docs(agent-memory): polish pass

- Trimmed frontmatter description so it fits the ~50-160 char target
  and reads as a standalone summary.
- Split the long hero paragraph into shorter sentences so each beat
  (value prop, harness list, no infra, async, each run) lands on its
  own. Fixed the 'memory ... memory' repetition by referring to
  creation and retrieval with 'they'.
- Reworded the 'Built on the layer your agents already live on'
  paragraph: opens with 'Warp is already the platform where your
  agents run', drops the dangling 'through the same platform' clause,
  and avoids the 'layer ... layer too' echo by saying 'Agent Memory
  turns that same platform into a memory layer'.
- Used 'Memory creation' (instead of 'Synthesis') in the 'Automatic
  memory from conversations' paragraph so the async terminology
  matches the 'Async by design' bullet.
- Switched the 'Sparse by design' / 'Learns over time' mini-headlines
  to the bold-term + em-dash + explanation pattern used by the rest
  of the page.
- Tightened the 'Per-agent access control and instructions' bullet.
- Replaced the awkward 'watch what they learn today make them
  sharper tomorrow' construction in the final CTA with 'so what they
  learn today makes them sharper tomorrow'.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: oz-agent

src/content/docs/agent-platform/agent-memory/index.mdx

@@ -1,17 +1,17 @@
 ---
 title: Agent Memory (Research Preview)
 description: >-
-  Agent Memory turns every agent you run on Warp — the built-in Warp Agent,
-  Claude Code, Codex, Gemini, and more — into one that learns over time,
-  with a shared memory layer that lives where your agents already do.
+  Agent Memory gives every agent you run on Warp — Warp Agent, Claude Code,
+  Codex, Gemini, and more — a shared, persistent memory that learns over
+  time.
 sidebar:
   label: "Agent Memory (Research Preview)"
 ---
 :::caution
 Agent Memory is in **research preview** and is enabled per team for design partners. [Join the waitlist](https://warp.dev/oz/agent-memory#waitlist) to request access for your team.
 :::
 
-Your agents should learn across every conversation, every harness, every run. Agent Memory makes that real: every agent you run on Warp — the built-in Warp Agent, Claude Code, Codex, Gemini, and any other harness — shares one persistent memory layer that lives on the same platform you already use to run them. No separate memory service to stand up. And because memory creation and retrieval happen in the background, memory doesn't slow down or burn tokens on the task in front of your agent — each run just begins further along than the last.
+Your agents should learn across every conversation, every harness, every run. Agent Memory makes that real. Every agent you run on Warp — the built-in Warp Agent, Claude Code, Codex, Gemini, and any other harness — shares one persistent memory layer on the platform you already use to run them. No separate memory service to stand up. And because memory creation and retrieval happen in the background, they never slow your agents down or burn tokens during a run. Each run just begins further along than the last.
 
 [**Join the Agent Memory waitlist →**](https://warp.dev/oz/agent-memory#waitlist)
 
@@ -21,12 +21,12 @@ Your agents should learn across every conversation, every harness, every run. Ag
 * **Async by design** — Memory creation and retrieval run in the background, so agents stay focused on the task and never burn tokens on memory work during a run.
 * **Automatic memory from conversations** — Warp extracts facts, learnings, and outcomes from finished conversations and combines them into memories your agents can build on over time.
 * **Personal and team memory stores** — Keep memories private to you, or share them across your team so every teammate and agent draws from the same well of knowledge.
-* **Per-agent access control and instructions** — Attach memory stores to an agent identity with read-only or read-write access, and write per-store instructions that tell the agent how and when to use each store.
+* **Per-agent access control and instructions** — Attach stores to specific agents with read-only or read-write access, plus per-store instructions that tell each agent how and when to use them.
 * **Safe by default** — Memory stores in active use can't be accidentally deleted, so shared team knowledge can't disappear out from under live agents.
 
 ## Built on the layer your agents already live on
 
-Warp is already where your agents run — the built-in Warp Agent locally, Oz cloud agents in the background, and third-party harnesses like Claude Code, Codex, and Gemini through the same platform. Agent Memory turns that layer into a memory layer too. Because storage and synthesis live where your agents already work, the same memory follows them across harnesses, machines, and teammates, with no new infrastructure to stand up or maintain.
+Warp is already the platform where your agents run — the built-in Warp Agent locally, Oz cloud agents in the background, and third-party harnesses like Claude Code, Codex, and Gemini. Agent Memory turns that same platform into a memory layer. Because the memory lives where your agents already work, it follows them across harnesses, machines, and teammates — with no new infrastructure to stand up or maintain.
 
 ## Memory stores
 
@@ -39,10 +39,10 @@ Use multiple stores to keep contexts clean, and share stores across agents when
 
 ## Automatic memory from conversations
 
-You don't have to remember to save things. When a conversation finishes, Warp extracts durable facts, learnings, and outcomes from what happened and writes them as memories — so every agent run leaves your team a little smarter than the last. Synthesis runs in the background after the conversation ends, so it never costs your agent tokens or attention during the task.
+You don't have to remember to save things. When a conversation finishes, Warp extracts durable facts, learnings, and outcomes from what happened and writes them as memories — so every agent run leaves your team a little smarter than the last. Memory creation runs in the background after the conversation ends, so it never costs your agent tokens or attention during a run.
 
-* **Sparse by design.** Routine work produces nothing. Only meaningful, reusable knowledge becomes a memory.
-* **Learns over time.** New knowledge merges into existing memories or supersedes outdated ones, so your team's memory keeps improving as your work evolves.
+* **Sparse by design** — Routine work produces nothing. Only meaningful, reusable knowledge becomes a memory.
+* **Learns over time** — New knowledge merges into existing memories or supersedes outdated ones, so your team's memory keeps improving as your work evolves.
 
 You can also explicitly tell Warp to remember something during a conversation, and it lands in the right store with the right context.
 
@@ -56,7 +56,7 @@ You decide which agents can read from which stores, and at what access level. Pe
 
 ## Ready to give your agents memory?
 
-Your agents already live on Warp. Give them a memory that lives there too — and watch what they learn today make them sharper tomorrow.
+Your agents already live on Warp. Give them a memory that lives there too, so what they learn today makes them sharper tomorrow.
 
 [**Join the Agent Memory waitlist →**](https://warp.dev/oz/agent-memory#waitlist)