Warp just opened a research preview for Agent Memory, a persistent memory layer that sits underneath multiple coding agents and lets them share what they've learned. The pitch is straightforward: stop making your agents relearn the same lessons every session, every repo, and every time a teammate kicks off a new task.

Agent Memory is a fully portable, cross-harness memory system that helps Claude Code, Codex, and the Warp agent remember what works across every session. It runs on Oz, Warp's cloud agent orchestration platform, and it's the first piece of memory infrastructure that explicitly spans more than one agent harness.

One brain, many agents

The core idea is decoupling memory from the agent runtime. Memory stays bound to its owner (a user or a team), independent of which harness reads or writes. So if Claude Code figures out the right way to run your migration scripts on Monday, Codex can pick up that same knowledge on Tuesday without anyone re-typing it into a prompt.

Memory is organized into named stores. By default, each agent has its own store that it writes to as it runs. Stores can also be shared across multiple agents when they need the same knowledge, and across teammates when knowledge should travel with the team. Personal stores hold individual preferences and working notes, while team stores carry shared artifacts like deployment runbooks, code review conventions, and on-call procedures.