Fast follow: orchestration launch docs updates#104
Conversation
Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds screenshot placement and sizing guidance to the docs style guide. The additions are scoped to documentation authoring standards and align with the stated intent; the security pass found no concerns.
Concerns
- No blocking concerns found.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
left a comment
hongyi-chen
left a comment
There was a problem hiding this comment.
a couple of small nits, but approving to unblock
| @@ -1,79 +1,79 @@ | |||
| --- | |||
| title: Agent Memory (Research Preview) | |||
There was a problem hiding this comment.
Can we keep this as Research Preview just for consistency with marketing comms?
| ## Sending a follow-up | ||
|
|
||
| You don't take a separate "hand off" action — you send a follow-up from the Warp app, and the run continues. The handoff happens automatically when the original session has ended. | ||
| To continue an ended cloud run, open the run in Warp and send the next message in the conversation. When the original session has ended, Warp automatically starts a fresh cloud session and restores the prior workspace state. |
There was a problem hiding this comment.
would be nice to include a screenshot here; we can tackle in a follow up PR
| --- | ||
|
|
||
| Handoff lets you move a unit of agent work between a local Warp session and the cloud, or continue a finished cloud run, without re-explaining the task. The receiving agent picks up the conversation history, your workspace state, and any conversation attachments from the prior session. | ||
| Handoff in Warp moves agent work between local Warp sessions and cloud agent runs without making you restart the task. Depending on the direction, Warp carries over conversation history, workspace changes, and attachments so the receiving agent can continue from the prior session instead of starting from scratch. |
There was a problem hiding this comment.
Generally, I don't think you need to describe things as "in Warp"
| After you submit, the cloud agent applies your workspace snapshot and responds to your follow-up. The local conversation is not modified, so you can keep working in it locally or close it. | ||
|
|
||
| To check on the new run, open it from the [Runs page](https://oz.warp.dev/runs) in the Oz web app or the conversation panel. | ||
| To check on the new run, open it from the [Runs page](https://oz.warp.dev/runs) in the Oz web app or the Conversation Panel in the Warp app. |
There was a problem hiding this comment.
Should we be capitalizing Conversational Panel? I think we can keep it lowercase? would like to keep this consistent throughout
There was a problem hiding this comment.
Reverted to lowercase for now but we may want to address on a broader scale later on as other parts of the docs treat it as a named UI surface w/ title case. Noting as an observation, not a high priority right now!
| 1. Go to the [Anthropic Console](https://platform.claude.com/login?returnTo=/?) and sign in (or create an account). | ||
| 2. Navigate to **API keys** and create a new key. | ||
| 3. Make sure your account has API credits — Claude Code runs are billed against your Anthropic API balance. | ||
| 2. In the top-right corner, click **Get API key**. |
There was a problem hiding this comment.
Instead of giving absolute directions, we should just tell them to navigate to specific sections (i.e. if Anthropic changes the layout of this page)
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
2 participants
Summary
This PR collects fast-follow improvements from a human review of the orchestration launch docs. The updates make the new Agent Memory, cloud handoff, and third-party harness docs clearer, more scannable, more visually actionable, and better aligned with the docs style guide.
Changes
Screenshot and style guidance
AGENTS.mdbased on patterns from legacy GitBook docs.Agent Memory docs
agent-memory/index.mdxfor clearer product framing, memory-store terminology, punctuation, and style-guide-aligned dash usage.Agent Memory (Research Preview)in the page title/sidebar for launch consistency while using lowercaseresearch previewin body copy.capabilities/skills.mdx.CLI agent related pages
Cloud handoff docs
conversation panelin these handoff docs.mainwhile resolving the branch conflict incloud-to-cloud.mdx.Third-party harness authentication docs
new runflow directly from the Claude Code and Codex credential setup steps.Review feedback and merge maintenance
in Warpphrasing, conversation panel capitalization, and provider API-key instructions.maininto this branch and resolved the resulting conflict.Additional context
Testing
git diff --checkgit diff --cached --checknpm --prefix /Users/rachaelrenk/Documents/Warp/docs run build— passed with existing non-fatal Astro prerender warnings.Co-Authored-By: Oz oz-agent@warp.dev