Elevate Oz cloud agents & orchestration to a top-level section + fix top-nav overflow#262
Conversation
Move agent-platform/cloud-agents/* to a new top-level platform/ directory and add an 'Oz' top-level nav tab between Agents and Reference. Repoint all crosslinks and vercel.json redirects to /platform/*, add an Oz Platform llms customSet, and fix the header topic-nav to wrap to a second row instead of clipping on narrow viewports (bumping --sl-nav-height in the crowded range so content isn't overlapped). 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 |
There was a problem hiding this comment.
Overview
This PR moves the Oz cloud agents docs into a top-level platform/ section, updates sidebar/navigation, redirects, and route references, and adjusts header wrapping behavior. The route move and navigation tree look mechanically consistent, but several updated authoring/audit references now point to platform.md, which does not exist after the landing page moved to platform/index.mdx.
Concerns
- Stale
platform.mdreferences in drafting guidance and the missing-docs surface map will point contributors or automation at nonexistent files; the audit resolver handles.md/.mdxvariants but not directory index pages.
Verdict
Found: 0 critical, 3 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
The meta-file sweep collapsed the old cloud-agents/overview file path to a nonexistent 'platform.md'; point these AGENTS.md, draft_conceptual, and feature_surface_map references at the real landing file 'platform/index.mdx'. Co-Authored-By: Oz <oz-agent@warp.dev>
|
/oz-review |
|
I'm re-reviewing this pull request in response to a review 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 |
There was a problem hiding this comment.
Overview
This PR moves the Oz cloud agents and orchestration documentation into a new top-level platform section, updates sidebar and llms.txt grouping, refreshes internal links and redirects, and adjusts the header topic nav to wrap at crowded widths. I reviewed the attached annotated diff, including the docs migration, navigation/config changes, redirect updates, security-relevant content, and the empty spec context.
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
|
|
||
| * [Agent API & SDK](https://docs.warp.dev/reference/api-and-sdk/agent) — API reference | ||
| * [Cloud Agents Overview](https://docs.warp.dev/agent-platform/cloud-agents/overview) — How cloud agents work | ||
| * [Cloud Agents Overview](https://docs.warp.dev/platform) — How cloud agents work |
There was a problem hiding this comment.
i assume we don't need to link to the "overview" pages right?
| * [Skills](/agent-platform/capabilities/skills/) - Reusable, scoped instructions that teach agents how to perform specific tasks. | ||
| * [Agent profiles and permissions](/agent-platform/capabilities/agent-profiles-permissions/) - Control what permissions and autonomy agents have. | ||
| * [Cloud agents overview](/agent-platform/cloud-agents/overview/) - Run background agents with team-wide observability. | ||
| * [Cloud agents overview](/platform/) - Run background agents with team-wide observability. |
There was a problem hiding this comment.
similarly, just want to double check if we also need to link an overview page? i assume this is the same as above
| }, | ||
| { | ||
| "source": "/agent-platform/agent-mode/ambient-agents-session-sharing", | ||
| "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", |
There was a problem hiding this comment.
we shouldn't just change the redirects from the old links, we should also add brand new redirects from these old destination links
e.g. /agent-platform/cloud-agents/viewing-cloud-agent-runs/ should go to /agent-platform/cloud-agents/viewing-cloud-agent-runs/
There was a problem hiding this comment.
ah i see these are added at the end, but i think we should also test them quite thoroughly. i see that it supports path matching via /agent-platform/cloud-agents/:path*, but would also like us to manually test a bit too!
…m-section # Conflicts: # src/content/docs/platform/environments.mdx
…icit redirects - Regroup the Oz topic into collapsible groups (Getting started, Managing agents, Orchestration kept as a separate sibling, Extending agents, Deployment & hosting, Access & support) instead of a flat first-level list. - Remove tangential 'Cloud agents overview' links from the error-page template and the Agent Memory see-also list. - Add explicit /agent-platform/cloud-agents/<page>/ -> /platform/<page>/ redirects (trailing and non-trailing variants) for all 47 moved pages. Live testing showed the :path* wildcard did not match trailing-slash URLs (the canonical form); explicit rules fix this. Kept both wildcards as fallback. Co-Authored-By: Oz <oz-agent@warp.dev>
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
…h wildcard The 94 explicit per-page redirects pushed vercel.json to 2056 entries and exceeded Vercel's redirect limit, failing the deployment. Revert to the wildcard approach and add a trailing-slash variant (/agent-platform/cloud-agents/:path*/ -> /platform/:path*/) to cover the trailing-slash URLs the non-trailing :path* wildcard was missing. Count back to 1962. Co-Authored-By: Oz <oz-agent@warp.dev>
|
Thanks @hongyi-chen! Pushed updates addressing all your feedback. Sidebar grouping — the Oz section is no longer a flat first-level list. Items are now collapsible groups under the Cloud agents overview landing: Getting started · Triggers · Integrations · Managing agents · Orchestration · Handoff · Harnesses · Extending agents · Deployment & hosting · Access & support. I kept "Orchestration" as its own group rather than nesting it under "Managing agents", since it's a headline concept (happy to nest it if you'd prefer). "Overview" links — removed the tangential Cloud agents overview links from both the error-page template and the Agent Memory "Related pages" list. Redirects from old destinations — The Verified live on the preview deploy. Old cloud-agents URLs now all 308 to their
Build + typecheck pass and the Vercel deploy is green. Ready for another look! |
Anchor the active-tab accent underline to the link's own bottom edge (bottom: 0) and let tabs hug their content instead of stretching to full header height. Previously the underline was dropped to the header's bottom hairline, which collided with the second row once the nav wrapped. Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
left a comment
There was a problem hiding this comment.
nice, looks good, ty!
let's proceed with the follow-up now, i.e.agents-platform -> agents
Resolve quickstart.mdx conflict from the cloud-agents -> platform restructure (warpdotdev#262): keep the link-out Next steps (de-duplicated, with the schedule example and Build/Max/Business note) and adopt the new /platform/ link paths. Co-Authored-By: Oz <oz-agent@warp.dev>
Resolve conflicts from main's cloud-agents -> /platform/ restructure (#262) and reconcile independently-added settings docs: - slash-commands.mdx: keep new /environment, /harness, /host, /rename-conversation rows; retarget moved cloud-agents links to /platform/. - all-settings.mdx: keep the corrected [agents.warp_agent.active_ai] home for git_operations_autogen_enabled (verified toml_path in source) and drop main's re-added, incorrect [agents.oz.active_ai] section; retarget handoff/ orchestration links to /platform/. - feature_surface_map.md: take main's /platform/ targets for cloud-agents entries, keep RemoteCodebaseIndexing, and migrate remaining cloud-agents mappings (AgentHarness, OzHandoff, Handoff*, RunAgentsTool, NamedAgents) to /platform/. Audit: map_hygiene 0, unaccounted none, no audits skipped. Build: 340 pages OK. Co-Authored-By: Oz <oz-agent@warp.dev>

Summary
Elevates the Oz Cloud Agents & Orchestration subsection from the Agents tab's sidebar into its own top-level Oz section in the horizontal header nav, positioned between Agents and Reference. Also reorganizes the section's sidebar into collapsible groups, fixes the header topic-nav to wrap on narrow viewports, and adds redirects (verified live) so every old URL keeps working.
Content move
src/content/docs/agent-platform/cloud-agents/*→src/content/docs/platform/*(49 files, viagit mv).overview.mdx→platform/index.mdx(landing at/platform/).platform.mdx("Oz Platform overview") →platform/overview.mdx(/platform/overview/).platform/pre-emptively for the upcoming product rename; the nav label is Oz for now.Navigation
src/sidebar.ts(link: '/platform/') between Agents and Reference. Memory stays under Agents.Cloud agents overviewlanding instead of a flat first-level list: Getting started, Triggers, Integrations, Managing agents, Orchestration, Handoff, Harnesses, Extending agents, Deployment & hosting, Access & support.WarpTopicNav.astro(cloud-downloadmobile-drawer fallback).Top-nav overflow fix
overflow: hidden, addedflex-wrap: wrap);--sl-nav-heightgrows in the crowded width range so the wrapped row doesn't overlap content.Crosslinks & config
/agent-platform/cloud-agents/...→/platform/...) across content + thedocs.warp.dev/...absolutes; also updatedAGENTS.md,astro.config.mjs, the SEO script, and.agents/skills/**.Cloud agents overviewlinks (error-page template + Agent Memory "Related pages"), per review.Oz PlatformllmscustomSetforplatform/**and trimmed the Agent Platform set.Redirects (every old URL preserved)
/platform/...and kept the 36 legacy GitBook sources./agent-platform/cloud-agents/overview/→/platform/and/agent-platform/cloud-agents/platform/→/platform/overview/./agent-platform/cloud-agents/:path*and/agent-platform/cloud-agents/:path*/→/platform/:path*/. The trailing-slash variant was added after live testing showed the non-trailing:path*alone didn't match trailing-slash URLs (our canonical form). An explicit per-page approach was tried first but pushedvercel.jsonover Vercel's redirect limit and failed the deploy, so the wildcard pair is the fix.Testing
Redirects — verified live on the preview deploy. Every old
/agent-platform/cloud-agents/*URL returns308to its/platform/*equivalent, across top-level, nested, and deep paths. Spot-checked examples:/agent-platform/cloud-agents/overview/→/platform//agent-platform/cloud-agents/platform/→/platform/overview//agent-platform/cloud-agents/viewing-cloud-agent-runs/→/platform/viewing-cloud-agent-runs//agent-platform/cloud-agents/integrations/slack/→/platform/integrations/slack//agent-platform/cloud-agents/self-hosting/quickstart/→/platform/self-hosting/quickstart/Other checks:
npm run build✓ (340 pages) ·npm run typecheck(astro check) ✓ (0 errors / 0 warnings)python3 scripts/check_redirects.py✓ (only wildcard sources flagged, as expected)0 residual
agent-platform/cloud-agentsreferences in contentVercel preview deploy is green
eyeball in the preview: the responsive top-nav wrap (resize ~50–90rem) and the active-tab underline placement when wrapped. @rachaelrenk
manually spot check redirects in the preview. @rachaelrenk
Notes
main; resolved a conflict inplatform/environments.mdx(kept the moved-file asset path + main's updated figcaption).cloud-agents-infra.pngasset reference; verifiedplatform-creditslinks were untouched.Plan: https://staging.warp.dev/drive/notebook/kH9pKwGM438cckB6SCAzyi
Conversation: https://staging.warp.dev/conversation/c5139d33-a19a-40d0-bc5e-56f25c1a051f
Co-Authored-By: Oz oz-agent@warp.dev