|
1 | 1 | --- |
2 | 2 | title: Agent Memory (Research Preview) |
3 | 3 | description: >- |
4 | | - Persistent, cross-harness memory layer that lets cloud agents on Oz carry |
5 | | - context from one run to the next. |
| 4 | + Persistent agent memory for Oz cloud agents. Carry context across runs and |
| 5 | + harnesses so each run starts further along than the last. |
6 | 6 | sidebar: |
7 | 7 | label: "Agent Memory" |
8 | 8 | --- |
9 | 9 | :::caution |
10 | | -Agent Memory is in **research preview**. Behavior, configuration, and any APIs may change before general availability. The feature is enabled per workspace for design partners — [join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your workspace. |
| 10 | +Agent Memory is in **research preview** and is enabled per workspace for design partners. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your workspace. |
11 | 11 | ::: |
12 | 12 |
|
13 | | -Every cloud agent run starts without context from prior runs. Agent Memory is a persistent, cross-harness memory layer for cloud agents on Oz: it captures durable knowledge from finished conversations and surfaces it at the start of future runs, so each run begins further along than the last. |
| 13 | +Every cloud agent run starts cold by default — it knows your codebase only as far as it can see in a single conversation. Agent Memory changes that. It captures durable knowledge from finished cloud runs and surfaces it at the start of future runs, so each run picks up where the last one left off. |
14 | 14 |
|
15 | | -## What's available today |
| 15 | +Agent Memory is a persistent, cross-harness memory layer that lives on Oz. The same knowledge is available whether your next run uses Warp Agent, Claude Code, Codex, or another supported harness. [Request early access](https://warp.dev/oz/agent-memory#waitlist) to try it with your team. |
16 | 16 |
|
17 | | -* **Cross-harness persistence** - Memories created in one harness are retrievable in another, because storage lives on Oz rather than inside a single harness. |
18 | | -* **Automatic consolidation** - Durable knowledge is extracted from finished conversations into a small, curated set of memories rather than the full conversation transcript. |
19 | | -* **Memory stores** - Named, scoped collections of memories that you attach to an agent identity for repeated runs or to a single run for one-off augmentation. |
20 | | -* **Session-start retrieval for personal memory** - At the start of each cloud run, Oz searches your personal memory store and injects relevant memories as context, regardless of harness. |
| 17 | +## Persistent memory across runs |
21 | 18 |
|
22 | | -## What's not yet available |
| 19 | +When an Oz cloud run finishes, Agent Memory consolidates durable knowledge from the conversation — preferences, conventions, environment details, repeated decisions — into a curated set of memories. The next run that needs them gets them as context, automatically. |
23 | 20 |
|
24 | | -* **Self-hosted memory backends** - Only the Warp-managed backend is available today. |
25 | | -* **Team-store retrieval at session start** - Consolidation can write to team-owned stores, but session-start retrieval only reads from the personal store. |
26 | | -* **CLI commands for memory store management** - Memory stores are managed through the Warp app today. |
27 | | -* **Suggested skills surfaced from memory patterns** - Promoting recurring memory patterns into reviewable skill drafts is still in design. |
28 | | -* **A stable, generally available public API** - The current surface is reachable for design partners, but paths and schemas may change before it lands in the public OpenAPI specification. |
| 21 | +## Cross-harness retrieval |
29 | 22 |
|
30 | | -## How to get involved |
| 23 | +Memories live on Oz, not inside a single harness. A memory created in a Warp Agent run is retrievable in a Claude Code run on the same identity, and vice versa. Your team isn't locked into one harness to benefit from the memory it has accumulated. |
31 | 24 |
|
32 | | -Agent Memory is enabled per workspace during the research preview. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your workspace, share use cases, or participate as a design partner on the pieces that aren't yet shipped. |
| 25 | +## Automatic consolidation |
| 26 | + |
| 27 | +Agent Memory extracts the signal from finished conversations — the durable facts that future runs actually need — and stores those instead of the raw transcript. Future runs get sharper context with less noise, and you don't pay the token cost of replaying everything. |
| 28 | + |
| 29 | +## Personal and team memory stores |
| 30 | + |
| 31 | +Memory stores are named, scoped collections of memories. Attach a store to an [agent identity](/agent-platform/cloud-agents/agents/) for repeated runs, so a deploy bot or a docs reviewer accumulates expertise over hundreds of runs. Attach one to a single run for one-off augmentation. Personal stores capture your own work; team stores let knowledge captured by one agent identity flow to the next. |
| 32 | + |
| 33 | +## Self-hosted memory backends |
| 34 | + |
| 35 | +For teams that need memory storage on their own infrastructure — for compliance, data residency, or preference — Agent Memory is designed to run against self-hosted backends alongside the Warp-managed default. |
| 36 | + |
| 37 | +## What Agent Memory unlocks |
| 38 | + |
| 39 | +* **Debugging that resumes where the last run left off** - A flaky-test investigation that ran out of time on Monday picks up Tuesday's run with the failure modes, hypotheses tested, and ruled-out causes already in context. |
| 40 | +* **Repeated maintenance agents that learn your codebase** - A dependency-bump agent or a link checker accumulates a memory of which crates are flaky, which directories to skip, and which past failures matter, so each run is faster and more accurate than the last. |
| 41 | +* **Team-shared knowledge across runs** - Deploy quirks, conventions, and runbook details captured by one teammate's agent are available the next time anyone on the team kicks off a run on the same identity. |
| 42 | + |
| 43 | +## Get early access |
| 44 | + |
| 45 | +Agent Memory is enabled per workspace during the research preview. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your workspace, share use cases, or partner with us on the parts still in design. |
33 | 46 |
|
34 | 47 | ## Related pages |
35 | 48 |
|
36 | | -* [**Skills**](/agent-platform/capabilities/skills/) - Durable instructions for agents; includes a forward-looking note on suggested skills from memory patterns. |
37 | | -* [**Agent identities**](https://docs.warp.dev/agent-platform/cloud-agents/agents/) - The team-scoped identities that memory stores attach to for repeated cloud runs. |
| 49 | +* [**Skills**](/agent-platform/capabilities/skills/) - Durable instructions for agents. |
| 50 | +* [**Agent identities**](/agent-platform/cloud-agents/agents/) - The team-scoped identities that memory stores attach to for repeated cloud runs. |
0 commit comments