Audit pass 3: Memory + Handoff polish, cross-references, glossary entries

.agents/references/terminology.md

@@ -93,6 +93,15 @@ For the summary of the most critical terms (core features, Oz terms, terms to av
 
 - **Slash Commands** — Built-in commands you run by typing `/` to trigger actions (or run saved prompts).
 
+- **Agent Memory** — Oz's persistent, cross-harness memory layer that lets agents read and write durable knowledge across conversations, harnesses, and devices. Currently in research preview.
+  *Usage note:* Capitalize as a feature name. Lowercase "memory" only when describing the generic concept (e.g., "the memory layer").
+
+- **memory store** — A named collection of memories owned by a user (personal) or team. Multiple agents can share a store, and per-agent attachments control read/write access.
+  *Usage note:* Lowercase common noun. Capitalize the first letter only at the start of a sentence or bullet.
+
+- **Handoff** — The feature for moving an agent's work between a local Warp session and the cloud, or continuing a finished cloud run. Supports local-to-cloud, cloud-to-cloud, and cloud-to-local directions.
+  *Usage note:* Capitalize as a feature name. Use lowercase "hand off" / "handed off" only as a verb.
+
 ## Coding terms (Warp features)
 
 - **Code** — Warp's coding experience for agent-assisted changes (editing, diffs, code review).

AGENTS.md

@@ -558,6 +558,8 @@ Product feature names retain their standard capitalization. Match the exact casi
 - **Codebase Context** - Warp indexes your Git-tracked codebase to help Agents understand your code.
 - **Admin Panel** - Team management surface for controlling members, roles, and billing.
 - **Agent Management Panel** - Interface for viewing and managing running agents (not "agent dashboard" or "agent manager").
+- **Agent Memory** - Persistent, cross-harness memory layer for Oz agents that captures durable facts, decisions, and outcomes across conversations (currently in research preview). Capitalize as a feature name; use lowercase "memory store" for individual stores.
+- **Handoff** - Feature for moving agent work between a local Warp session and the cloud, or continuing a finished cloud run; supports local-to-cloud, cloud-to-cloud, and cloud-to-local. Capitalize as a feature name; lowercase "hand off" only as a verb.
 
 ### Oz terminology
 

src/content/docs/agent-platform/capabilities/skills.mdx

@@ -411,7 +411,7 @@ Warp maintains a public collection of ready-to-use skills in the [warpdotdev/oz-
 
 These same skills also appear as suggested agents in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/), where you can run them directly in the cloud.
 
-## Suggested Skills from Agent Memory
+## Suggested skills from Agent Memory
 
 Promoting recurring patterns from [Agent Memory](/agent-platform/agent-memory/) into reviewable skill drafts is in design as part of the research preview. See the Agent Memory page for current status.
 

src/content/docs/agent-platform/cloud-agents/handoff/index.mdx

@@ -27,7 +27,7 @@ Handoff coverage depends on which agent is running the conversation:
 
 ## What carries over
 
-Handoff preserves enough state that the receiving agent can resume the work, not just read about it.
+Handoff preserves enough state that the receiving agent can resume the work, not only read about it.
 
 * **Conversation history** - The receiving agent sees the full transcript of the prior session. Local-to-cloud forks the conversation so the source isn't modified; cloud-to-cloud continues in the same conversation.
 * **Workspace state** - Local-to-cloud and cloud-to-cloud capture the prior session's repository changes (tracked and untracked) and apply them in the receiving run before the agent answers the next prompt. The cloud-to-local direction doesn't currently apply workspace patches to your local checkout; review the cloud agent's branch or pull request artifact to inspect those changes.

src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx

@@ -99,3 +99,10 @@ In both _Personal_ and _All_ views, you can open the filter menu and filter by:
 * Status
 
 This is the fastest way to isolate "everything that failed today," "runs from Slack," or "what a specific teammate triggered via integrations."
+
+## Related pages
+
+* [Cloud agents overview](/agent-platform/cloud-agents/overview/) — What cloud agents are and when to use them.
+* [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) — Open and inspect a remote cloud agent run.
+* [Handoff between local and cloud agents](/agent-platform/cloud-agents/handoff/) — Move agent work between local and cloud, or continue a finished cloud run.
+* [Oz web app](/agent-platform/cloud-agents/oz-web-app/) — Manage runs and schedules from any browser.

src/content/docs/agent-platform/cloud-agents/viewing-cloud-agent-runs.mdx

@@ -71,6 +71,8 @@ If you still want to continue the conversation or work on the code, you can clic
 
 #### 5. Fork the session to your local Warp
 
+Forking is the cloud-to-local direction of [Handoff between local and cloud agents](/agent-platform/cloud-agents/handoff/) — see that page for the other directions (local-to-cloud and cloud-to-cloud).
+
 Forking brings the cloud agent conversation into your local machine, so you can pick up where the agent left off.
 
 Once forked:

src/content/docs/agent-platform/local-agents/cloud-conversations.mdx

@@ -136,3 +136,4 @@ When you delete a conversation, it is removed permanently and immediately. Make
 * [Conversation Forking](/agent-platform/local-agents/interacting-with-agents/conversation-forking/) - Branch conversations to explore different directions.
 * [Session Sharing](/agent-platform/local-agents/session-sharing/) - Collaborate in real time on a live Agent session.
 * [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) - Run agents in the cloud from triggers, schedules, or integrations.
+* [Handoff between local and cloud agents](/agent-platform/cloud-agents/handoff/) - Promote a local conversation to a cloud agent run, or continue a finished cloud run.