Give your coding agent an (Elastic) memory

If you work with a coding agent every day, you know the routine. Each new session starts blank: the agent re-reads files it read yesterday, asks about decisions you settled last week, and redoes debugging you already finished. Its only memory is the context window, and that empties every time you close your laptop.

Claude Code ships a built-in fix: markdown notes the agent writes for itself and reads back at the next session start. It helps, but the notes live on one machine, there is no real search, and anything past the first page of the index gets dropped.

In this hands-on workshop, we’ll take that idea further with agent-memory, an open source project that keeps decisions, tasks, and session history in Elasticsearch, so they’re searchable and shared across machines. You’ll stand up the whole memory backend on Elastic Cloud with one Pulumi command, wire it into your coding agent, then kill the agent mid-task and see how much a fresh one remembers when its memory is a search engine instead of a text file.

You’ll leave with a repo you can review and share, so every teammate gets an identical memory backend instead of their own snowflake. No promises about becoming a 1000x AI engineer, but your agent will stop asking you the same question twice.