diff --git a/.agents/skills/afdocs-audit/references/known-exceptions.md b/.agents/skills/afdocs-audit/references/known-exceptions.md index fc9af65de..05eb819d1 100644 --- a/.agents/skills/afdocs-audit/references/known-exceptions.md +++ b/.agents/skills/afdocs-audit/references/known-exceptions.md @@ -25,8 +25,8 @@ This file lists checks from the afdocs-audit skill that may flag as warnings or **Expected status**: warn (several pages, ~2% average difference) **Reason**: False positive. The "missing" segments are numbered heading text like "2. Tabbed File Viewer" where Turndown correctly escapes the period (`### 2\. Tabbed File Viewer`) to prevent markdown parsers from interpreting it as a list item. The content IS present in the markdown — the AFDocs checker's text comparison doesn't account for markdown escaping. **Affected pages** (as of 2026-05-05): -- `/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/` — step headings -- `/agent-platform/cloud-agents/integrations/github-actions/` — numbered use case headings +- `/platform/triggers/scheduled-agents-quickstart/` — step headings +- `/platform/integrations/github-actions/` — numbered use case headings - `/support-and-community/troubleshooting-and-support/troubleshooting-login-issues/` — URLs with special chars - `/reference/cli/quickstart/` — optional step headings - `/guides/getting-started/welcome-to-warp/` — numbered section headings diff --git a/.agents/skills/answer_question/SKILL.md b/.agents/skills/answer_question/SKILL.md index e7a175772..f4c98bbf1 100644 --- a/.agents/skills/answer_question/SKILL.md +++ b/.agents/skills/answer_question/SKILL.md @@ -71,7 +71,7 @@ Key rules: - **`src/content/docs/` is the homepage space** — the `warp/` prefix is NOT included in URLs. Example: `src/content/docs/terminal/blocks/block-basics.mdx` → `https://docs.warp.dev/terminal/blocks/block-basics` - All other spaces include the space name in the URL. Example: `src/content/docs/agent-platform/capabilities/skills.mdx` → `https://docs.warp.dev/agent-platform/capabilities/skills` - Strip the `.mdx` extension. -- `index.mdx` resolves to the parent directory path. Example: `src/content/docs/agent-platform/cloud-agents/integrations/index.mdx` → `https://docs.warp.dev/agent-platform/cloud-agents/integrations` +- `index.mdx` resolves to the parent directory path. Example: `src/content/docs/platform/integrations/index.mdx` → `https://docs.warp.dev/platform/integrations` ### 5. Output format diff --git a/.agents/skills/docs-seo-audit/SKILL.md b/.agents/skills/docs-seo-audit/SKILL.md index 74506f79c..38dd00e7b 100644 --- a/.agents/skills/docs-seo-audit/SKILL.md +++ b/.agents/skills/docs-seo-audit/SKILL.md @@ -183,15 +183,15 @@ Astro Starlight uses `title` for the `` tag and `sidebar.label` for the s Example: - `agent-platform/capabilities/index.mdx`: `title: 'Capabilities overview'` + `sidebar.label: 'Overview'` -- `agent-platform/cloud-agents/integrations/index.mdx`: `title: 'Integrations overview'` + `sidebar.label: 'Overview'` +- `platform/integrations/index.mdx`: `title: 'Integrations overview'` + `sidebar.label: 'Overview'` When using this approach, also update the H1 in the markdown file to match the new `title`. #### Alternative: rename the sidebar config label If the short label is not intentional, rename the `label` in `src/sidebar.ts` to be unique and descriptive. Use sentence case and correct terminology per `AGENTS.md` (e.g., capitalize proper feature names like "Agent Mode", "Warp Drive", "Codebase Context" — but not generic terms like "overview", "quickstart", or "agents"). Example: -- Before: `{ slug: 'agent-platform/local-agents', label: 'Overview' }` + `{ slug: 'agent-platform/cloud-agents', label: 'Overview' }` -- After: `{ slug: 'agent-platform/local-agents', label: 'Local agents overview' }` + `{ slug: 'agent-platform/cloud-agents', label: 'Cloud agents overview' }` +- Before: `{ slug: 'agent-platform/local-agents', label: 'Overview' }` + `{ slug: 'platform', label: 'Overview' }` +- After: `{ slug: 'agent-platform/local-agents', label: 'Local agents overview' }` + `{ slug: 'platform', label: 'Cloud agents overview' }` When changing a sidebar config label, also update the H1 in the markdown file for consistency. diff --git a/.agents/skills/docs-seo-audit/scripts/seo_audit.py b/.agents/skills/docs-seo-audit/scripts/seo_audit.py index e1da7f44e..25dd8366d 100644 --- a/.agents/skills/docs-seo-audit/scripts/seo_audit.py +++ b/.agents/skills/docs-seo-audit/scripts/seo_audit.py @@ -36,7 +36,7 @@ # Astro Starlight content directory # --------------------------------------------------------------------------- # All content lives under src/content/docs/. URL paths map directly to this -# directory (e.g. /agent-platform/cloud-agents → src/content/docs/agent-platform/cloud-agents). +# directory (e.g. /platform → src/content/docs/platform). CONTENT_DIR = "src/content/docs" # --------------------------------------------------------------------------- diff --git a/.agents/skills/draft_conceptual/SKILL.md b/.agents/skills/draft_conceptual/SKILL.md index 0f24b54f8..3c51cfecd 100644 --- a/.agents/skills/draft_conceptual/SKILL.md +++ b/.agents/skills/draft_conceptual/SKILL.md @@ -34,5 +34,5 @@ All headings (H1–H4) must use **sentence case**: capitalize only the first wor ## Existing examples Read 2-3 of these strong examples to match the existing pattern: -- `src/content/docs/agent-platform/cloud-agents/deployment-patterns.md` -- `src/content/docs/agent-platform/cloud-agents/overview.md` +- `src/content/docs/platform/deployment-patterns.md` +- `src/content/docs/platform/index.mdx` diff --git a/.agents/skills/draft_feature_doc/SKILL.md b/.agents/skills/draft_feature_doc/SKILL.md index 0ef4f9596..87b94d73e 100644 --- a/.agents/skills/draft_feature_doc/SKILL.md +++ b/.agents/skills/draft_feature_doc/SKILL.md @@ -35,4 +35,4 @@ All headings (H1–H4) must use **sentence case**: capitalize only the first wor Read 2-3 of these strong examples to match the existing pattern: - `src/content/docs/agent-platform/capabilities/skills.md` -- `src/content/docs/agent-platform/cloud-agents/environments.md` +- `src/content/docs/platform/environments.md` diff --git a/.agents/skills/draft_procedural/SKILL.md b/.agents/skills/draft_procedural/SKILL.md index 3945e36b7..022f3a3c7 100644 --- a/.agents/skills/draft_procedural/SKILL.md +++ b/.agents/skills/draft_procedural/SKILL.md @@ -53,4 +53,4 @@ All headings (H1–H4) must use **sentence case**: capitalize only the first wor Read 2-3 of these strong examples to match the existing pattern: - `src/content/docs/reference/cli/api-keys.md` -- `src/content/docs/agent-platform/cloud-agents/integrations/slack.md` +- `src/content/docs/platform/integrations/slack.md` diff --git a/.agents/skills/draft_quickstart/SKILL.md b/.agents/skills/draft_quickstart/SKILL.md index 9a441b5da..531477926 100644 --- a/.agents/skills/draft_quickstart/SKILL.md +++ b/.agents/skills/draft_quickstart/SKILL.md @@ -36,5 +36,5 @@ All headings (H1–H4) must use **sentence case**: capitalize only the first wor ## Existing examples Read 2-3 of these strong examples to match the existing pattern: -- `src/content/docs/agent-platform/cloud-agents/quickstart.md` +- `src/content/docs/platform/quickstart.md` - `src/content/docs/getting-started/quickstart/installation-and-setup.md` diff --git a/.agents/skills/missing_docs/references/feature_surface_map.md b/.agents/skills/missing_docs/references/feature_surface_map.md index 8d149d767..20c2a05a1 100644 --- a/.agents/skills/missing_docs/references/feature_surface_map.md +++ b/.agents/skills/missing_docs/references/feature_surface_map.md @@ -13,8 +13,8 @@ Lines starting with `#` are comments. Blank lines are ignored. ## Feature flags -> doc pages AgentMode -> src/content/docs/agent-platform/local-agents/overview.mdx -AgentManagementView -> src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.md -AgentManagementDetailsView -> src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.md +AgentManagementView -> src/content/docs/platform/managing-cloud-agents.md +AgentManagementDetailsView -> src/content/docs/platform/managing-cloud-agents.md AgentModeComputerUse -> src/content/docs/agent-platform/capabilities/computer-use.mdx AgentModeWorkflows -> src/content/docs/knowledge-and-collaboration/warp-drive/workflows.md AgentOnboarding -> src/content/docs/agent-platform/getting-started/agents-in-warp.md @@ -36,11 +36,11 @@ CodebaseContext -> src/content/docs/agent-platform/capabilities/codebase-context CrossRepoContext -> src/content/docs/agent-platform/capabilities/codebase-context.mdx FullSourceCodeEmbedding -> src/content/docs/agent-platform/capabilities/codebase-context.mdx SearchCodebaseUI -> src/content/docs/agent-platform/capabilities/codebase-context.mdx -CloudEnvironments -> src/content/docs/agent-platform/cloud-agents/environments.md -CloudMode -> src/content/docs/agent-platform/cloud-agents/overview.md -AmbientAgentsCommandLine -> src/content/docs/agent-platform/cloud-agents/overview.md -ScheduledAmbientAgents -> src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.md -WarpManagedSecrets -> src/content/docs/agent-platform/cloud-agents/secrets.md +CloudEnvironments -> src/content/docs/platform/environments.md +CloudMode -> src/content/docs/platform/index.mdx +AmbientAgentsCommandLine -> src/content/docs/platform/index.mdx +ScheduledAmbientAgents -> src/content/docs/platform/triggers/scheduled-agents.md +WarpManagedSecrets -> src/content/docs/platform/secrets.md IntegrationCommand -> src/content/docs/reference/cli/integration-setup.md ConversationManagement -> src/content/docs/agent-platform/local-agents/cloud-conversations.mdx ForkConversationFromBlock -> src/content/docs/agent-platform/local-agents/interacting-with-agents/conversation-forking.mdx @@ -112,7 +112,7 @@ GitOperationsInCodeReview -> src/content/docs/code/code-review.md AgentView -> src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx AgentViewBlockContext -> src/content/docs/agent-platform/local-agents/agent-context/blocks-as-context.mdx CloudConversations -> src/content/docs/agent-platform/local-agents/cloud-conversations.mdx -CloudModeFromLocalSession -> src/content/docs/agent-platform/cloud-agents/overview.md +CloudModeFromLocalSession -> src/content/docs/platform/index.mdx TeamApiKeys -> src/content/docs/reference/cli/api-keys.md PRCommentsSlashCommand -> src/content/docs/agent-platform/capabilities/slash-commands.mdx PRCommentsV2 -> src/content/docs/agent-platform/local-agents/interacting-with-agents/index.mdx diff --git a/.agents/skills/sync-error-docs/references/error-page-template.md b/.agents/skills/sync-error-docs/references/error-page-template.md index 6d9067b01..532738830 100644 --- a/.agents/skills/sync-error-docs/references/error-page-template.md +++ b/.agents/skills/sync-error-docs/references/error-page-template.md @@ -61,7 +61,6 @@ This error is returned when: ## Related * [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 ``` ## Placeholder reference diff --git a/AGENTS.md b/AGENTS.md index ebd2eee4b..c6656f517 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -400,7 +400,7 @@ These rules apply regardless of content type: - Do NOT include step-by-step procedures — link to a procedural or quickstart page instead - Show real-world scenarios, not just abstract descriptions -**Existing examples**: `agent-platform/cloud-agents/deployment-patterns.mdx`, `agent-platform/cloud-agents/overview.mdx` +**Existing examples**: `platform/deployment-patterns.mdx`, `platform/index.mdx` **Template**: `.warp/templates/conceptual.md` @@ -428,7 +428,7 @@ These rules apply regardless of content type: - Test all instructions for accuracy. - Provide troubleshooting for common failure points. -**Existing examples**: `reference/cli/api-keys.mdx`, `agent-platform/cloud-agents/integrations/slack.mdx` +**Existing examples**: `reference/cli/api-keys.mdx`, `platform/integrations/slack.mdx` **Template**: `.warp/templates/procedural.md` @@ -453,7 +453,7 @@ These rules apply regardless of content type: - Keep steps focused on the critical path — defer edge cases and advanced options to other pages. - All procedural rules apply (focused steps, motivate steps, expected outcomes). -**Existing examples**: `agent-platform/cloud-agents/quickstart.mdx`, `getting-started/quickstart/installation-and-setup.mdx` +**Existing examples**: `platform/quickstart.mdx`, `getting-started/quickstart/installation-and-setup.mdx` **Template**: `.warp/templates/quickstart.md` @@ -569,7 +569,7 @@ This is the most common page type in Warp's docs (~75+ pages). A feature documen - Apply the **procedural** rules to the step-by-step sections (one action per step, motivate steps, expected outcomes). - Keep the conceptual and procedural sections clearly separated with distinct headers. -**Existing examples**: `agent-platform/capabilities/skills.mdx`, `agent-platform/cloud-agents/environments.mdx` +**Existing examples**: `agent-platform/capabilities/skills.mdx`, `platform/environments.mdx` **Template**: `.warp/templates/feature-doc.md` diff --git a/astro.config.mjs b/astro.config.mjs index 63c2d0f02..fb9ad8fd4 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -70,7 +70,7 @@ export default defineConfig({ wrap: true, }, // Map languages Shiki doesn't bundle to a safe fallback. PromQL - // blocks live in agent-platform/cloud-agents/self-hosting/monitoring.mdx; + // blocks live in platform/self-hosting/monitoring.mdx; // without this alias every build emits noisy "language could not be // found" warnings while still falling back to plaintext. shiki: { @@ -165,7 +165,8 @@ export default defineConfig({ 'Documentation for Warp, the agentic development environment, and Oz, Warp\'s programmable agent for running and coordinating agents at scale.', customSets: [ { label: 'Terminal', description: 'Warp Terminal features and configuration.', paths: ['terminal/**'] }, - { label: 'Agent Platform', description: 'Warp\'s Agent Platform: capabilities, local agents, CLI agents, cloud agents.', paths: ['agent-platform/**'] }, + { label: 'Agent Platform', description: 'Warp\'s Agent Platform: capabilities, local agents, and CLI agents.', paths: ['agent-platform/**'] }, + { label: 'Oz Platform', description: 'Warp\'s Oz platform: cloud agents, orchestration, triggers, integrations, environments, harnesses, and self-hosting.', paths: ['platform/**'] }, { label: 'Code', description: 'Code editor, code review, and Git worktrees.', paths: ['code/**'] }, { label: 'Enterprise', description: 'Enterprise features, SSO, team management, and security.', paths: ['enterprise/**'] }, { label: 'Getting Started', description: 'Installation, quickstart, and migration guides.', paths: ['index', 'quickstart', 'getting-started/**'] }, diff --git a/scripts/seo-audit.mjs b/scripts/seo-audit.mjs index 8facf6347..07d18b357 100644 --- a/scripts/seo-audit.mjs +++ b/scripts/seo-audit.mjs @@ -11,13 +11,13 @@ * node scripts/seo-audit.mjs --dist ./dist * * # Audit live URLs (handy for spot-checking the legacy GitBook output) - * node scripts/seo-audit.mjs --base https://docs.warp.dev /agent-platform/cloud-agents/oz-web-app /changelog + * node scripts/seo-audit.mjs --base https://docs.warp.dev /platform/oz-web-app /changelog * * # Diff between two sources, e.g. legacy vs. our preview deploy * node scripts/seo-audit.mjs \\ * --base https://docs.warp.dev \\ * --compare https://docs-preview.warp.dev \\ - * /agent-platform/cloud-agents/oz-web-app + * /platform/oz-web-app * * The script is intentionally dependency-free (uses regex over the raw HTML * head) so it runs in CI without installing extra packages. @@ -29,7 +29,7 @@ const DEFAULT_PATHS = [ '/', '/quickstart/', '/agent-platform/', - '/agent-platform/cloud-agents/oz-web-app/', + '/platform/oz-web-app/', '/agent-platform/capabilities/skills/', '/reference/cli/', '/reference/api-and-sdk/', diff --git a/src/components/WarpTopicNav.astro b/src/components/WarpTopicNav.astro index 4d91dbb20..d36cf094c 100644 --- a/src/components/WarpTopicNav.astro +++ b/src/components/WarpTopicNav.astro @@ -40,6 +40,7 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = { Agents: true, API: true, Enterprise: true, + Oz: true, }; --- @@ -95,6 +96,19 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = { <line x1="15" y1="14" x2="15" y2="14.01" /> <path d="M10 22v-4h4v4" /> </svg> + ) : topic.label === 'Oz' ? ( + /* Cloud icon — Feather-style cloud outline, stroke weight + matched to the other topic icons. */ + <svg + viewBox="0 0 24 24" + fill="none" + stroke="currentColor" + stroke-width="2" + stroke-linecap="round" + stroke-linejoin="round" + > + <path d="M18 10h-1.26A8 8 0 1 0 9 20h9a5 5 0 0 0 0-10z" /> + </svg> ) : ( /* Robot icon — stroke-based outline matching the visual weight of Starlight's other topic icons (laptop, book, @@ -135,12 +149,13 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = { <style> .warp-topic-nav { /* Sits between SiteTitle and the right control group inside `.header`. - The header itself is `display: flex; align-items: center;` — this - nav uses `align-self: stretch` so its links can pin a 2px accent - underline to the header's bottom edge. */ + `align-self: stretch` keeps the nav at full header height so its + row(s) of tabs center vertically; `align-items: center` centers the + tab list within that height — important once the list wraps to a + second row on crowded widths. */ align-self: stretch; display: flex; - align-items: stretch; + align-items: center; min-width: 0; } @@ -149,37 +164,37 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = { margin: 0; padding: 0; display: flex; - align-items: stretch; - gap: 1.25rem; + flex-wrap: wrap; + align-items: center; + /* Row gap applies only once the nav wraps to a second row on crowded + mid-width viewports; column gap keeps the single-row spacing. */ + gap: 0.25rem 1.25rem; min-width: 0; - overflow: hidden; } li { display: flex; - align-items: stretch; + align-items: center; } a { - /* Stretches to the full header height so the bottom-anchored `::after` - indicator sits flush with the header hairline (Scalar pattern) — - not under the link's text box. `align-self: stretch` inherits the - parent <li>'s height (which inherits from `<ul>` → nav → header). */ + /* The link hugs its own content (icon + label) plus a little vertical + padding, so the active-state `::after` underline sits just under the + tab in both single-row and wrapped (two-row) layouts. Vertical + centering of the row(s) is handled by the parent nav/ul rather than + by stretching each link to the full header height. */ position: relative; - align-self: stretch; display: flex; align-items: center; gap: 0.5rem; - padding: 0 0.25rem; + padding: 0.4rem 0.25rem; font-size: var(--sl-text-sm); font-weight: 500; /* `1.25` is just enough to clear Inter's natural ascent + descent (~1.21em) so descenders in `Changelog` (`g`) and `Reference` (`f`) aren't clipped, while keeping the line-box close to the - visible text. The link's outer height is set by `align-self: - stretch` on the parent, so this only affects internal text - layout (and the icon's optical centering, see - `.warp-topic-nav__icon` below). */ + visible text — which keeps the underline tight to the tab and the + icon optically centered (see `.warp-topic-nav__icon` below). */ line-height: 1.25; /* Idle color uses `gray-3` so the active link's full-emphasis white text reads as clearly distinct (and not just "white-on-slightly- @@ -213,23 +228,17 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = { font-weight: 600; } - /* 2px accent underline that REPLACES the header's 1px bottom hairline - under the active topic (Scalar pattern). The outer Starlight - `<header class="header">` owns the hairline - (`border-bottom: 1px solid var(--sl-color-hairline-shade)`) and has - `padding-block: var(--sl-nav-pad-y)` with `box-sizing: border-box`, so - the link's bottom edge sits `--sl-nav-pad-y` above the hairline rather - than directly on it. We anchor the indicator at the hairline by - dropping it through the bottom padding (`-var(--sl-nav-pad-y)`) and the - 1px border (`-1px`); `height: 2px` then paints across both, leaving the - blue accent as the only line at that position under the active tab. - The remainder of the header keeps its hairline. */ + /* 2px accent underline under the active tab, anchored to the link's own + bottom edge so it hugs the tab. It previously dropped down to the + header's bottom hairline (Scalar pattern), but once the nav can wrap to + a second row that pushed the line into the row below — `bottom: 0` keeps + it attached to the active tab in every layout. */ a[aria-current='page']::after { content: ''; position: absolute; left: 0; right: 0; - bottom: calc(-1 * var(--sl-nav-pad-y) - 1px); + bottom: 0; height: 2px; background: var(--sl-color-text-accent); } @@ -269,13 +278,13 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = { display: inline-block; } - /* Mid-width fallback. Below ~80rem (~1280px) the 8 topic items + logo + + /* Mid-width fallback. Below ~80rem (~1280px) the topic items + logo + right-group start to crowd. Drop the per-item icons first so the labels keep room. The mobile drawer (rendered separately) takes over below 50rem where this nav is hidden entirely. */ @media (max-width: 80rem) { ul { - gap: 1rem; + gap: 0.25rem 1rem; } .warp-topic-nav__icon { display: none; diff --git a/src/content/docs/agent-platform/agent-memory/index.mdx b/src/content/docs/agent-platform/agent-memory/index.mdx index 33b90bf8f..923c54af7 100644 --- a/src/content/docs/agent-platform/agent-memory/index.mdx +++ b/src/content/docs/agent-platform/agent-memory/index.mdx @@ -85,7 +85,7 @@ Attach stores to agents with read-only or read-write access. Each attachment inc These capabilities aren't part of the research preview yet, but they're on the way: * **Programmatic API access** - Read and manage memories and stores through the [Oz API](/reference/api-and-sdk/), in addition to managing them in the Oz web app. -* **Self-hosting support** - Run Agent Memory on a [self-hosted Oz](/agent-platform/cloud-agents/self-hosting/) instance to meet security, privacy, and compliance requirements. +* **Self-hosting support** - Run Agent Memory on a [self-hosted Oz](/platform/self-hosting/) instance to meet security, privacy, and compliance requirements. ## Join the waitlist @@ -97,4 +97,3 @@ Agent Memory is rolling out to design partner teams during research preview. [Jo * [Rules](/agent-platform/capabilities/rules/) - Define global and project-level guidelines that shape agent behavior. * [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. diff --git a/src/content/docs/agent-platform/capabilities/agent-notifications.mdx b/src/content/docs/agent-platform/capabilities/agent-notifications.mdx index 57f1e9c57..622fe589e 100644 --- a/src/content/docs/agent-platform/capabilities/agent-notifications.mdx +++ b/src/content/docs/agent-platform/capabilities/agent-notifications.mdx @@ -101,7 +101,7 @@ If auto-install doesn't work or you're running an agent over SSH, Warp displays ## Notifications in orchestrated runs -In a [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/), the parent agent and each child agent are separate conversations. Today, in-app notifications fire on the parent's conversation only: child agent conversations are excluded from the toast stream and the notification mailbox so the mailbox doesn't get cluttered with per-child status churn. +In a [multi-agent orchestration](/platform/orchestration/), the parent agent and each child agent are separate conversations. Today, in-app notifications fire on the parent's conversation only: child agent conversations are excluded from the toast stream and the notification mailbox so the mailbox doesn't get cluttered with per-child status churn. That means: @@ -112,8 +112,8 @@ That means: ## Related pages * [Desktop Notifications](/terminal/more-features/notifications/) - configure system-level notification permissions and troubleshoot delivery -* [Managing Agents](/agent-platform/cloud-agents/managing-cloud-agents/) - monitor all agent conversations, filter by status, and inspect sessions -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) - parent/child model, run state transitions, and the orchestration pill bar +* [Managing Agents](/platform/managing-cloud-agents/) - monitor all agent conversations, filter by status, and inspect sessions +* [Multi-agent orchestration](/platform/orchestration/) - parent/child model, run state transitions, and the orchestration pill bar * [Third-party CLI agents](/agent-platform/cli-agents/overview/) - overview of supported CLI agents and Warp features * [Claude Code](/agent-platform/cli-agents/claude-code/) - setup and notification plugin installation * [Codex](/agent-platform/cli-agents/codex/) - setup and notification configuration diff --git a/src/content/docs/agent-platform/capabilities/codebase-context.mdx b/src/content/docs/agent-platform/capabilities/codebase-context.mdx index 7033ff7f4..7f4d0b033 100644 --- a/src/content/docs/agent-platform/capabilities/codebase-context.mdx +++ b/src/content/docs/agent-platform/capabilities/codebase-context.mdx @@ -35,7 +35,7 @@ git clone https://github.com/vercel/next.js.git && cd next.js When you open a directory in Warp, we check if it is part of a Git repository. If it is, Warp begins indexing the source code to provide rich context for Agents. Warp also detects [Git worktree](/code/git-worktrees/) checkouts — each worktree is indexed as its own repository, so Agents always have accurate context for the branch you're working on. :::note -Code indexed with Codebase Context is never stored on our servers. Codebase Context works with both local agent sessions and [cloud agent runs](/agent-platform/cloud-agents/overview/). Without Codebase Context enabled, agents will still be able use terminal commands (i.e. `grep`, `sed`) to navigate your code. +Code indexed with Codebase Context is never stored on our servers. Codebase Context works with both local agent sessions and [cloud agent runs](/platform/). Without Codebase Context enabled, agents will still be able use terminal commands (i.e. `grep`, `sed`) to navigate your code. ::: :::note diff --git a/src/content/docs/agent-platform/capabilities/computer-use.mdx b/src/content/docs/agent-platform/capabilities/computer-use.mdx index 11c48b6c7..b65461b0e 100644 --- a/src/content/docs/agent-platform/capabilities/computer-use.mdx +++ b/src/content/docs/agent-platform/capabilities/computer-use.mdx @@ -31,7 +31,7 @@ Computer Use is **opt-in** and disabled by default. You can enable it through se ### Warp app settings -To enable Computer Use for [Cloud Agents](/agent-platform/cloud-agents/overview/), navigate to **Settings** > **Agents** > **Warp Agent** > **Experimental** > **Computer use in Cloud Agents** and toggle to enable. +To enable Computer Use for [Cloud Agents](/platform/), navigate to **Settings** > **Agents** > **Warp Agent** > **Experimental** > **Computer use in Cloud Agents** and toggle to enable. ### CLI @@ -72,7 +72,7 @@ In the Warp web app, you can enable or disable Computer Use for: Computer Use runs in a containerized sandbox, allowing headless cloud environments to render and interact with graphical applications. The sandbox is fully isolated—it does not have access to your local machine, credentials, or sensitive data outside the sandbox environment. -Your cloud environment must include any applications you want the agent to control. For example, to test a web app in a browser, install Chrome or Firefox in your [environment configuration](/agent-platform/cloud-agents/environments/). +Your cloud environment must include any applications you want the agent to control. For example, to test a web app in a browser, install Chrome or Firefox in your [environment configuration](/platform/environments/). ### Model selection diff --git a/src/content/docs/agent-platform/capabilities/mcp.mdx b/src/content/docs/agent-platform/capabilities/mcp.mdx index ad373d339..6a1e1bfd2 100644 --- a/src/content/docs/agent-platform/capabilities/mcp.mdx +++ b/src/content/docs/agent-platform/capabilities/mcp.mdx @@ -12,7 +12,7 @@ MCP servers extend Warp's [local agents](/agent-platform/local-agents/interactin MCP is an open source protocol. Check out the official [MCP documentation](https://modelcontextprotocol.io/introduction) for more detailed information on how this protocol is engineered. :::note -This page covers MCP servers for local agents in the Warp app. For help choosing between local, cloud, and shared MCP workflows, see [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/). If you're using cloud agents, see [MCP Servers for cloud agents](/agent-platform/cloud-agents/mcp/). +This page covers MCP servers for local agents in the Warp app. For help choosing between local, cloud, and shared MCP workflows, see [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/). If you're using cloud agents, see [MCP Servers for cloud agents](/platform/mcp/). ::: ### How to access MCP Server settings diff --git a/src/content/docs/agent-platform/capabilities/planning.mdx b/src/content/docs/agent-platform/capabilities/planning.mdx index bfe4738db..60ae8bea8 100644 --- a/src/content/docs/agent-platform/capabilities/planning.mdx +++ b/src/content/docs/agent-platform/capabilities/planning.mdx @@ -112,4 +112,4 @@ The **@plans** command helps you quickly search for and reopen previously saved As the agent executes your plan, you'll review code changes and may want to scale work to the cloud. * **[Interactive Code Review](/agent-platform/local-agents/interactive-code-review/)** - Leave inline comments on agent-generated diffs and have the agent revise in one pass. -* **[Cloud Agents quickstart](/agent-platform/cloud-agents/quickstart/)** - Run agents in the cloud for longer tasks, background automation, or parallel work across repos. +* **[Cloud Agents quickstart](/platform/quickstart/)** - Run agents in the cloud for longer tasks, background automation, or parallel work across repos. diff --git a/src/content/docs/agent-platform/capabilities/skills.mdx b/src/content/docs/agent-platform/capabilities/skills.mdx index 7b70a851e..dcffe7050 100644 --- a/src/content/docs/agent-platform/capabilities/skills.mdx +++ b/src/content/docs/agent-platform/capabilities/skills.mdx @@ -409,7 +409,7 @@ This opens an interactive menu where you can: Warp maintains a public collection of ready-to-use skills in the [warpdotdev/oz-skills](https://github.com/warpdotdev/oz-skills) repository. You can browse these skills for inspiration, copy them directly into your project's `.agents/skills/` directory, or adapt them to fit your team's workflows. -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. +These same skills also appear as suggested agents in the [Oz web app](/platform/oz-web-app/), where you can run them directly in the cloud. ## Suggested skills from Agent Memory @@ -428,15 +428,15 @@ This is useful when you want to reuse a skill's workflow but tailor the executio ## Running agents from skills -Skills can be used with both local and [cloud agents](/agent-platform/cloud-agents/overview/) to create reusable, automated workflows. When running an agent via the CLI, web app, or API, you can specify a skill to provide the base instructions for the agent. +Skills can be used with both local and [cloud agents](/platform/) to create reusable, automated workflows. When running an agent via the CLI, web app, or API, you can specify a skill to provide the base instructions for the agent. -For a complete guide to running skill-based agents—including CLI usage, the Oz web app, scheduling, skill discovery, and API integration—see [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/). +For a complete guide to running skill-based agents—including CLI usage, the Oz web app, scheduling, skill discovery, and API integration—see [Skills as Agents](/platform/skills-as-agents/). ## Related features * [**Rules**](/agent-platform/capabilities/rules/) - Set persistent guidelines and constraints for Agent behavior * [**MCP Servers**](/agent-platform/capabilities/mcp/) - Expose external data sources and tools to Agents -* [**Cloud Agents**](/agent-platform/cloud-agents/overview/) - Run Agents in the cloud on schedules or triggers +* [**Cloud Agents**](/platform/) - Run Agents in the cloud on schedules or triggers * [**Agent Profiles**](/agent-platform/capabilities/agent-profiles-permissions/) - Control Agent permissions and autonomy --- @@ -445,5 +445,5 @@ For a complete guide to running skill-based agents—including CLI usage, the Oz Skills become even more powerful when you automate and share them. -* **[Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/)** - Run a skill on a recurring cron schedule for tasks like weekly dependency checks or daily code cleanup. -* **[Integrations quickstart](/agent-platform/cloud-agents/integrations/quickstart/)** - Trigger skills from Slack or Linear so your team can invoke agent workflows from the tools they already use. +* **[Scheduled Agents quickstart](/platform/triggers/scheduled-agents-quickstart/)** - Run a skill on a recurring cron schedule for tasks like weekly dependency checks or daily code cleanup. +* **[Integrations quickstart](/platform/integrations/quickstart/)** - Trigger skills from Slack or Linear so your team can invoke agent workflows from the tools they already use. diff --git a/src/content/docs/agent-platform/capabilities/slash-commands.mdx b/src/content/docs/agent-platform/capabilities/slash-commands.mdx index 4f6190c43..ab1500ead 100644 --- a/src/content/docs/agent-platform/capabilities/slash-commands.mdx +++ b/src/content/docs/agent-platform/capabilities/slash-commands.mdx @@ -18,7 +18,7 @@ As you type, the menu filters results in real time, making it easy to find and r Warp currently supports the following built-in Slash Commands: -<table><thead><tr><th width="211.64453125">Slash Command</th><th>Description</th></tr></thead><tbody><tr><td><code>/add-mcp</code></td><td>Add a new <a href="/agent-platform/capabilities/mcp/">MCP server</a>.</td></tr><tr><td><code>/add-prompt</code></td><td>Add a new <a href="/knowledge-and-collaboration/warp-drive/prompts/">Agent Prompt</a> in Warp Drive.</td></tr><tr><td><code>/add-rule</code></td><td>Add a new <a href="/agent-platform/capabilities/rules/">Global Rule</a> for the Agent.</td></tr><tr><td><code>/agent</code></td><td>Start a new <a href="/agent-platform/local-agents/interacting-with-agents/">agent conversation</a>. Optionally include a prompt to send immediately.</td></tr><tr><td><code>/changelog</code></td><td>Open the latest Warp <a href="/changelog/">changelog</a>.</td></tr><tr><td><code>/cloud-agent</code></td><td>Start a new <a href="/agent-platform/cloud-agents/overview/">cloud agent conversation</a>. <code>{'*'}</code></td></tr><tr><td><code>/compact</code></td><td>Free up context by summarizing conversation history.</td></tr><tr><td><code>/compact-and</code></td><td>Compact the current conversation and then send a follow-up prompt.</td></tr><tr><td><code>/conversations</code></td><td>Open <a href="/agent-platform/local-agents/interacting-with-agents/">conversation history</a>.</td></tr><tr><td><code>/cost</code></td><td>Toggle credit usage details in the current conversation.</td></tr><tr><td><code>/create-environment</code></td><td>Create a <a href="/agent-platform/cloud-agents/environments/">Warp Environment</a> (Docker image + repos) via guided setup. <code>{'*'}</code></td></tr><tr><td><code>/create-new-project</code></td><td>Have the Agent walk you through creating a new coding project. <code>{'*'}</code></td></tr><tr><td><code>/export-to-clipboard</code></td><td>Export the current conversation to clipboard in markdown format.</td></tr><tr><td><code>/export-to-file</code></td><td>Export the current conversation to a markdown file.</td></tr><tr><td><code>/feedback</code></td><td>Open the static feedback experience. See <a href="/support-and-community/troubleshooting-and-support/sending-us-feedback/#using-feedback-in-warp">Using <code>/feedback</code> in Warp</a> for details.</td></tr><tr><td><code>/fork</code></td><td><a href="/agent-platform/local-agents/interacting-with-agents/conversation-forking/">Forks the current conversation</a> into a new thread with the full context and history of the original. <br /><br />You can optionally include a prompt that will be sent immediately in the forked conversation.</td></tr><tr><td><code>/fork-and-compact</code></td><td><a href="/agent-platform/local-agents/interacting-with-agents/conversation-forking/">Forks the current conversation</a> and automatically compacts the forked version.<br /><br />Useful when you want a fresh, summarized starting point that preserves relevant context while trimming the rest.</td></tr><tr><td><code>/fork-from</code></td><td>Open a searchable menu to <a href="/agent-platform/local-agents/interacting-with-agents/conversation-forking/">fork the conversation</a> from a specific query. Select a query to create a fork that includes everything up to that point.</td></tr><tr><td><code>/index</code></td><td>Index the current codebase using <a href="/agent-platform/capabilities/codebase-context/">Codebase Context</a>.</td></tr><tr><td><code>/init</code></td><td>Index the current codebase and generate an <a href="/agent-platform/capabilities/rules/">AGENTS.md file</a>. <code>{'*'}</code></td></tr><tr><td><code>/model</code></td><td>Switch the base agent model for the current conversation.</td></tr><tr><td><code>/new</code></td><td>Start a new <a href="/agent-platform/local-agents/interacting-with-agents/">agent conversation</a> (alias for <code>/agent</code>).</td></tr><tr><td><code>/open-code-review</code></td><td>Open the <a href="/code/code-review/">code review</a> pane.</td></tr><tr><td><code>/open-file</code></td><td>Open a file for editing in Warp's <a href="/code/code-editor/">code editor</a>.</td></tr><tr><td><code>/open-mcp-servers</code></td><td>View the status of your <a href="/agent-platform/capabilities/mcp/">MCP servers</a>.</td></tr><tr><td><code>/open-project-rules</code></td><td>Open the <a href="/agent-platform/capabilities/rules/#project-rules">Project Rules</a> file (<code>AGENTS</code>).</td></tr><tr><td><code>/open-repo</code></td><td>Switch to another indexed repository.</td></tr><tr><td><code>/open-rules</code></td><td>View all of your global and project <a href="/agent-platform/capabilities/rules/">rules</a>.</td></tr><tr><td><code>/open-settings-file</code></td><td>Open the Warp <a href="/terminal/settings/">settings file</a> (<code>settings.toml</code>) in Warp's code editor.</td></tr><tr><td><code>/open-skill</code></td><td>Open an interactive menu to browse and edit project or global <a href="/agent-platform/capabilities/skills/">skills</a>.</td></tr><tr><td><code>/orchestrate</code></td><td>Break a task into subtasks and run them in parallel with multiple agents. <code>{'*'}</code></td></tr><tr><td><code>/plan</code></td><td>Prompt the Agent to do some research and create a <a href="/agent-platform/capabilities/planning/">plan</a> for a task.</td></tr><tr><td><code>/pr-comments</code></td><td>Pull GitHub PR review comments into Warp. <code>{'*'}</code></td></tr><tr><td><code>/profile</code></td><td>Switch the active <a href="/agent-platform/capabilities/agent-profiles-permissions/">execution profile</a>.</td></tr><tr><td><code>/prompts</code></td><td>Search saved <a href="/knowledge-and-collaboration/warp-drive/prompts/">prompts</a>.</td></tr><tr><td><code>/queue</code></td><td>Queue a prompt to send after the agent finishes responding. See <a href="/agent-platform/local-agents/interacting-with-agents/prompt-queueing/">Prompt Queueing</a>.</td></tr><tr><td><code>/rename-tab</code></td><td>Rename the current tab. Include the new tab name as an argument (for example, <code>/rename-tab deploy</code>).</td></tr><tr><td><code>/rewind</code></td><td>Rewind to a previous point in the conversation.</td></tr><tr><td><code>/skills</code></td><td>Invoke a <a href="/agent-platform/capabilities/skills/">skill</a> from a searchable menu.</td></tr><tr><td><code>/usage</code></td><td>Open <a href="/support-and-community/plans-and-billing/">billing and usage</a> settings.</td></tr></tbody></table> +<table><thead><tr><th width="211.64453125">Slash Command</th><th>Description</th></tr></thead><tbody><tr><td><code>/add-mcp</code></td><td>Add a new <a href="/agent-platform/capabilities/mcp/">MCP server</a>.</td></tr><tr><td><code>/add-prompt</code></td><td>Add a new <a href="/knowledge-and-collaboration/warp-drive/prompts/">Agent Prompt</a> in Warp Drive.</td></tr><tr><td><code>/add-rule</code></td><td>Add a new <a href="/agent-platform/capabilities/rules/">Global Rule</a> for the Agent.</td></tr><tr><td><code>/agent</code></td><td>Start a new <a href="/agent-platform/local-agents/interacting-with-agents/">agent conversation</a>. Optionally include a prompt to send immediately.</td></tr><tr><td><code>/changelog</code></td><td>Open the latest Warp <a href="/changelog/">changelog</a>.</td></tr><tr><td><code>/cloud-agent</code></td><td>Start a new <a href="/platform/">cloud agent conversation</a>. <code>{'*'}</code></td></tr><tr><td><code>/compact</code></td><td>Free up context by summarizing conversation history.</td></tr><tr><td><code>/compact-and</code></td><td>Compact the current conversation and then send a follow-up prompt.</td></tr><tr><td><code>/conversations</code></td><td>Open <a href="/agent-platform/local-agents/interacting-with-agents/">conversation history</a>.</td></tr><tr><td><code>/cost</code></td><td>Toggle credit usage details in the current conversation.</td></tr><tr><td><code>/create-environment</code></td><td>Create a <a href="/platform/environments/">Warp Environment</a> (Docker image + repos) via guided setup. <code>{'*'}</code></td></tr><tr><td><code>/create-new-project</code></td><td>Have the Agent walk you through creating a new coding project. <code>{'*'}</code></td></tr><tr><td><code>/export-to-clipboard</code></td><td>Export the current conversation to clipboard in markdown format.</td></tr><tr><td><code>/export-to-file</code></td><td>Export the current conversation to a markdown file.</td></tr><tr><td><code>/feedback</code></td><td>Open the static feedback experience. See <a href="/support-and-community/troubleshooting-and-support/sending-us-feedback/#using-feedback-in-warp">Using <code>/feedback</code> in Warp</a> for details.</td></tr><tr><td><code>/fork</code></td><td><a href="/agent-platform/local-agents/interacting-with-agents/conversation-forking/">Forks the current conversation</a> into a new thread with the full context and history of the original. <br /><br />You can optionally include a prompt that will be sent immediately in the forked conversation.</td></tr><tr><td><code>/fork-and-compact</code></td><td><a href="/agent-platform/local-agents/interacting-with-agents/conversation-forking/">Forks the current conversation</a> and automatically compacts the forked version.<br /><br />Useful when you want a fresh, summarized starting point that preserves relevant context while trimming the rest.</td></tr><tr><td><code>/fork-from</code></td><td>Open a searchable menu to <a href="/agent-platform/local-agents/interacting-with-agents/conversation-forking/">fork the conversation</a> from a specific query. Select a query to create a fork that includes everything up to that point.</td></tr><tr><td><code>/index</code></td><td>Index the current codebase using <a href="/agent-platform/capabilities/codebase-context/">Codebase Context</a>.</td></tr><tr><td><code>/init</code></td><td>Index the current codebase and generate an <a href="/agent-platform/capabilities/rules/">AGENTS.md file</a>. <code>{'*'}</code></td></tr><tr><td><code>/model</code></td><td>Switch the base agent model for the current conversation.</td></tr><tr><td><code>/new</code></td><td>Start a new <a href="/agent-platform/local-agents/interacting-with-agents/">agent conversation</a> (alias for <code>/agent</code>).</td></tr><tr><td><code>/open-code-review</code></td><td>Open the <a href="/code/code-review/">code review</a> pane.</td></tr><tr><td><code>/open-file</code></td><td>Open a file for editing in Warp's <a href="/code/code-editor/">code editor</a>.</td></tr><tr><td><code>/open-mcp-servers</code></td><td>View the status of your <a href="/agent-platform/capabilities/mcp/">MCP servers</a>.</td></tr><tr><td><code>/open-project-rules</code></td><td>Open the <a href="/agent-platform/capabilities/rules/#project-rules">Project Rules</a> file (<code>AGENTS</code>).</td></tr><tr><td><code>/open-repo</code></td><td>Switch to another indexed repository.</td></tr><tr><td><code>/open-rules</code></td><td>View all of your global and project <a href="/agent-platform/capabilities/rules/">rules</a>.</td></tr><tr><td><code>/open-settings-file</code></td><td>Open the Warp <a href="/terminal/settings/">settings file</a> (<code>settings.toml</code>) in Warp's code editor.</td></tr><tr><td><code>/open-skill</code></td><td>Open an interactive menu to browse and edit project or global <a href="/agent-platform/capabilities/skills/">skills</a>.</td></tr><tr><td><code>/orchestrate</code></td><td>Break a task into subtasks and run them in parallel with multiple agents. <code>{'*'}</code></td></tr><tr><td><code>/plan</code></td><td>Prompt the Agent to do some research and create a <a href="/agent-platform/capabilities/planning/">plan</a> for a task.</td></tr><tr><td><code>/pr-comments</code></td><td>Pull GitHub PR review comments into Warp. <code>{'*'}</code></td></tr><tr><td><code>/profile</code></td><td>Switch the active <a href="/agent-platform/capabilities/agent-profiles-permissions/">execution profile</a>.</td></tr><tr><td><code>/prompts</code></td><td>Search saved <a href="/knowledge-and-collaboration/warp-drive/prompts/">prompts</a>.</td></tr><tr><td><code>/queue</code></td><td>Queue a prompt to send after the agent finishes responding. See <a href="/agent-platform/local-agents/interacting-with-agents/prompt-queueing/">Prompt Queueing</a>.</td></tr><tr><td><code>/rename-tab</code></td><td>Rename the current tab. Include the new tab name as an argument (for example, <code>/rename-tab deploy</code>).</td></tr><tr><td><code>/rewind</code></td><td>Rewind to a previous point in the conversation.</td></tr><tr><td><code>/skills</code></td><td>Invoke a <a href="/agent-platform/capabilities/skills/">skill</a> from a searchable menu.</td></tr><tr><td><code>/usage</code></td><td>Open <a href="/support-and-community/plans-and-billing/">billing and usage</a> settings.</td></tr></tbody></table> :::caution Slash commands marked with a `*` consume credits to complete the task. diff --git a/src/content/docs/agent-platform/cli-agents/claude-code.mdx b/src/content/docs/agent-platform/cli-agents/claude-code.mdx index 4094ff798..9e2936fe4 100644 --- a/src/content/docs/agent-platform/cli-agents/claude-code.mdx +++ b/src/content/docs/agent-platform/cli-agents/claude-code.mdx @@ -14,7 +14,7 @@ Warp auto-detects Claude Code when you run it, giving you access to rich input c For installation, authentication, project configuration, and productivity tips, see the [How to set up Claude Code](/guides/external-tools/how-to-set-up-claude-code/) guide. :::note -Claude Code is also available as a harness in Oz for cloud orchestration. See [Claude Code with Oz](/agent-platform/cloud-agents/harnesses/claude-code/). +Claude Code is also available as a harness in Oz for cloud orchestration. See [Claude Code with Oz](/platform/harnesses/claude-code/). ::: ## Setting up notifications @@ -74,6 +74,6 @@ Claude Code supports the full set of Warp's agent integration features: * [How to set up Claude Code](/guides/external-tools/how-to-set-up-claude-code/) — step-by-step setup guide * [Claude Code in Warp](https://www.warp.dev/agents/claude-code) — product overview * [Third-party CLI agents overview](/agent-platform/cli-agents/overview/) — supported CLI agent integrations -* [Claude Code with Oz](/agent-platform/cloud-agents/harnesses/claude-code/) — Claude Code as a cloud harness +* [Claude Code with Oz](/platform/harnesses/claude-code/) — Claude Code as a cloud harness * [OpenCode](/agent-platform/cli-agents/opencode/) — OpenCode in Warp * [Codex](/agent-platform/cli-agents/codex/) — Codex in Warp diff --git a/src/content/docs/agent-platform/cli-agents/codex.mdx b/src/content/docs/agent-platform/cli-agents/codex.mdx index 068e254bc..401fdc42a 100644 --- a/src/content/docs/agent-platform/cli-agents/codex.mdx +++ b/src/content/docs/agent-platform/cli-agents/codex.mdx @@ -14,7 +14,7 @@ Warp auto-detects Codex when you run it, giving you access to rich input control For installation, authentication, project configuration, and productivity tips, see the [How to set up Codex CLI](/guides/external-tools/how-to-set-up-codex-cli/) guide. :::note -Codex is also available as a harness in Oz for cloud orchestration. See [Codex with Oz](/agent-platform/cloud-agents/harnesses/codex/). +Codex is also available as a harness in Oz for cloud orchestration. See [Codex with Oz](/platform/harnesses/codex/). ::: ## Setting up notifications @@ -49,6 +49,6 @@ Codex supports the full set of Warp's agent integration features: * [How to set up Codex CLI](/guides/external-tools/how-to-set-up-codex-cli/) — step-by-step setup guide * [Codex in Warp](https://www.warp.dev/agents/codex) — product overview * [Third-party CLI agents overview](/agent-platform/cli-agents/overview/) — supported CLI agent integrations -* [Codex with Oz](/agent-platform/cloud-agents/harnesses/codex/) — Codex as a cloud harness +* [Codex with Oz](/platform/harnesses/codex/) — Codex as a cloud harness * [Claude Code](/agent-platform/cli-agents/claude-code/) — Claude Code in Warp * [OpenCode](/agent-platform/cli-agents/opencode/) — OpenCode in Warp diff --git a/src/content/docs/agent-platform/cli-agents/overview.mdx b/src/content/docs/agent-platform/cli-agents/overview.mdx index c3fe72137..4e1cd1b67 100644 --- a/src/content/docs/agent-platform/cli-agents/overview.mdx +++ b/src/content/docs/agent-platform/cli-agents/overview.mdx @@ -12,7 +12,7 @@ Warp auto-detects supported CLI agents and enhances them with IDE-level features This feature set is also known as **universal agent support**. :::note -Claude Code and Codex are also supported as harnesses in Oz for cloud orchestration. See [Harnesses in Oz](/agent-platform/cloud-agents/harnesses/). +Claude Code and Codex are also supported as harnesses in Oz for cloud orchestration. See [Harnesses in Oz](/platform/harnesses/). ::: ## Supported agents diff --git a/src/content/docs/agent-platform/cli-agents/remote-control.mdx b/src/content/docs/agent-platform/cli-agents/remote-control.mdx index f1cdc0090..09aa2925d 100644 --- a/src/content/docs/agent-platform/cli-agents/remote-control.mdx +++ b/src/content/docs/agent-platform/cli-agents/remote-control.mdx @@ -68,4 +68,4 @@ Only you (the publisher) can revoke access or stop publishing the session. * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) * [Third-party CLI agents](/agent-platform/cli-agents/overview/) -* [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) +* [Viewing Cloud Agent Runs](/platform/viewing-cloud-agent-runs/) diff --git a/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx b/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx index 5fd93b94f..0677b46b4 100644 --- a/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx +++ b/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx @@ -68,7 +68,7 @@ For more details, see [Agent Profiles & Permissions](/agent-platform/capabilitie ## Managing agents -You can run multiple agents simultaneously in Warp. All active agents—both local conversations and cloud agent runs—are tracked in the [management view](/agent-platform/cloud-agents/managing-cloud-agents/). +You can run multiple agents simultaneously in Warp. All active agents—both local conversations and cloud agent runs—are tracked in the [management view](/platform/managing-cloud-agents/). Agents notify you when they need input, such as permission to run a command or approval to apply a code diff. This lets you focus on other work, knowing you'll be alerted when your attention is required. @@ -107,7 +107,7 @@ The same agent capabilities that power interactive conversations in Warp also ru Cloud agents are ideal for work that doesn't need your immediate attention—PR reviews, issue triage, routine maintenance, and integration-driven workflows. -→ [Learn about Cloud Agents](/agent-platform/cloud-agents/overview/) +→ [Learn about Cloud Agents](/platform/) --- diff --git a/src/content/docs/agent-platform/index.mdx b/src/content/docs/agent-platform/index.mdx index dc2735e8f..5041c2197 100644 --- a/src/content/docs/agent-platform/index.mdx +++ b/src/content/docs/agent-platform/index.mdx @@ -24,9 +24,9 @@ Oz is fully programmable—launch agents manually or build custom logic around t * [**Local Agents**](/agent-platform/local-agents/overview/) - Interactive agents embedded in Warp. Use natural language to write code, debug issues, run commands, and automate development tasks with full terminal access. * [**Third-party CLI agents**](/agent-platform/cli-agents/overview/) - Use Claude Code, Codex, OpenCode, and other CLI coding agents in Warp with rich input, notifications, code review, and remote session control. -* [**Cloud Agents**](/agent-platform/cloud-agents/overview/) - Autonomous agents that run in the background in response to system events, schedules, or integrations. -* [**Integrations**](/agent-platform/cloud-agents/integrations/) - Connect external system events to autonomous agent execution. Use [Slack](/agent-platform/cloud-agents/integrations/slack/), [Linear](/agent-platform/cloud-agents/integrations/linear/), [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/), and other integrations to trigger agents in the cloud. -* [**Oz Platform**](/agent-platform/cloud-agents/platform/) - The underlying infrastructure that powers Oz, including the CLI, API/SDK, orchestration layer, environments, secrets, and management/observability. +* [**Cloud Agents**](/platform/) - Autonomous agents that run in the background in response to system events, schedules, or integrations. +* [**Integrations**](/platform/integrations/) - Connect external system events to autonomous agent execution. Use [Slack](/platform/integrations/slack/), [Linear](/platform/integrations/linear/), [GitHub Actions](/platform/integrations/github-actions/), and other integrations to trigger agents in the cloud. +* [**Oz Platform**](/platform/overview/) - The underlying infrastructure that powers Oz, including the CLI, API/SDK, orchestration layer, environments, secrets, and management/observability. --- @@ -43,10 +43,10 @@ Oz is fully programmable—launch agents manually or build custom logic around t * [Warp Agents overview](/agent-platform/local-agents/overview/) - Interactive agents in Warp * [Third-party CLI agents](/agent-platform/cli-agents/overview/) - Claude Code, Codex, OpenCode, and more -* [Cloud Agents overview](/agent-platform/cloud-agents/overview/) - Background agents for automation at scale +* [Cloud Agents overview](/platform/) - Background agents for automation at scale * [Agent Capabilities](/agent-platform/capabilities/) - Skills, planning, MCP, rules, and more -* [Oz Platform](/agent-platform/cloud-agents/platform/) - CLI, API/SDK, orchestration, environments, and hosts -* [Environments](/agent-platform/cloud-agents/environments/) - Configure execution context for cloud agents -* [Integrations](/agent-platform/cloud-agents/integrations/) - Slack, Linear, GitHub Actions, and custom integrations -* [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) - Run agents from reusable skill definitions -* [Managing Cloud Agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Monitor and manage agent activity +* [Oz Platform](/platform/overview/) - CLI, API/SDK, orchestration, environments, and hosts +* [Environments](/platform/environments/) - Configure execution context for cloud agents +* [Integrations](/platform/integrations/) - Slack, Linear, GitHub Actions, and custom integrations +* [Skills as Agents](/platform/skills-as-agents/) - Run agents from reusable skill definitions +* [Managing Cloud Agents](/platform/managing-cloud-agents/) - Monitor and manage agent activity diff --git a/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx b/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx index 0a8d68c30..f559736ea 100644 --- a/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx +++ b/src/content/docs/agent-platform/inference/bring-your-own-api-key.mdx @@ -47,7 +47,7 @@ Your API key passes through Warp's servers each time you send a request, but War ::: :::caution -BYOK does not apply to [Cloud Agents](/agent-platform/cloud-agents/overview/). Because your API keys are stored locally on your device, they are not available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). +BYOK does not apply to [Cloud Agents](/platform/). Because your API keys are stored locally on your device, they are not available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). ::: When a model is selected using your own key: @@ -101,7 +101,7 @@ Some AI-powered features are not affected by BYOK and are included as part of Wa | ----------------------------------------------------------------------------- | ------------------- | -------------------------------------------------------------------- | | [Active AI Recommendations](/agent-platform/local-agents/active-ai/) | No | Always included with Build and higher plans. | | [Codebase Context](/agent-platform/capabilities/codebase-context/) | Yes | Uses Warp's AI infrastructure and consumes credits. | -| [Cloud Agents](/agent-platform/cloud-agents/overview/) | Yes | BYOK keys are stored locally and not available to cloud-hosted runs. | +| [Cloud Agents](/platform/) | Yes | BYOK keys are stored locally and not available to cloud-hosted runs. | These features will continue to function normally regardless of whether you’ve configured BYOK. diff --git a/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx b/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx index 74e8bde8c..15030a45f 100644 --- a/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx +++ b/src/content/docs/agent-platform/inference/custom-inference-endpoint.mdx @@ -46,7 +46,7 @@ Your API key passes through Warp's servers each time you send a request, but War ::: :::caution -Custom inference endpoints don't apply to [Cloud Agents](/agent-platform/cloud-agents/overview/). Because the configuration is stored locally, it isn't available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). +Custom inference endpoints don't apply to [Cloud Agents](/platform/). Because the configuration is stored locally, it isn't available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). ::: When a model routed through your endpoint is selected: diff --git a/src/content/docs/agent-platform/inference/grok-subscription.mdx b/src/content/docs/agent-platform/inference/grok-subscription.mdx index 727806455..88b08b67d 100644 --- a/src/content/docs/agent-platform/inference/grok-subscription.mdx +++ b/src/content/docs/agent-platform/inference/grok-subscription.mdx @@ -47,7 +47,7 @@ When a Grok model with the key icon is selected: Warp's **Auto** models always use Warp's own inference and **always consume Warp credits**, even with a SuperGrok subscription connected. Auto never routes requests through your subscription. To use your subscription, select a specific Grok model from the model picker. :::caution -A connected SuperGrok subscription does not apply to [Cloud Agents](/agent-platform/cloud-agents/overview/). Because tokens are stored locally on your device, they are not available to cloud-hosted agent runs, which always consume [Warp credits](/support-and-community/plans-and-billing/credits/). +A connected SuperGrok subscription does not apply to [Cloud Agents](/platform/). Because tokens are stored locally on your device, they are not available to cloud-hosted agent runs, which always consume [Warp credits](/support-and-community/plans-and-billing/credits/). ::: ### Zero data retention (ZDR) diff --git a/src/content/docs/agent-platform/inference/model-choice.mdx b/src/content/docs/agent-platform/inference/model-choice.mdx index 79482199a..5289fc76c 100644 --- a/src/content/docs/agent-platform/inference/model-choice.mdx +++ b/src/content/docs/agent-platform/inference/model-choice.mdx @@ -15,7 +15,7 @@ Warp lets you choose from a curated set of large language models (LLMs) to power **Warp supports the following models.** -The `model_id` values shown below can be used when configuring models via the [Oz Platform](/agent-platform/cloud-agents/platform/) or [CLI](/reference/cli/). +The `model_id` values shown below can be used when configuring models via the [Oz Platform](/platform/overview/) or [CLI](/reference/cli/). ### Auto models diff --git a/src/content/docs/agent-platform/local-agents/agent-context/images-as-context.mdx b/src/content/docs/agent-platform/local-agents/agent-context/images-as-context.mdx index beeabf932..053115d52 100644 --- a/src/content/docs/agent-platform/local-agents/agent-context/images-as-context.mdx +++ b/src/content/docs/agent-platform/local-agents/agent-context/images-as-context.mdx @@ -35,7 +35,7 @@ Warp accepts the following image formats: `.jpg`, `.jpeg`, `.png`, `.gif`, and ` You can attach up to **5 images per request**, and up to **20 images across a single conversation**. Each image is sent to the model provider and immediately discarded — nothing is stored on Warp's servers. :::caution -**Cloud agent conversations do not currently support image attachments.** Image attachment is only available in local agent conversations. If you need to provide visual context to a cloud agent, describe the image contents in your prompt or reference the image file path within the cloud agent's [environment](/agent-platform/cloud-agents/environments/). +**Cloud agent conversations do not currently support image attachments.** Image attachment is only available in local agent conversations. If you need to provide visual context to a cloud agent, describe the image contents in your prompt or reference the image file path within the cloud agent's [environment](/platform/environments/). ::: ### Model behavior and image handling diff --git a/src/content/docs/agent-platform/local-agents/cloud-conversations.mdx b/src/content/docs/agent-platform/local-agents/cloud-conversations.mdx index 56127abc2..552a0c36a 100644 --- a/src/content/docs/agent-platform/local-agents/cloud-conversations.mdx +++ b/src/content/docs/agent-platform/local-agents/cloud-conversations.mdx @@ -6,7 +6,7 @@ description: >- --- import VideoEmbed from '@components/VideoEmbed.astro'; -Warp can sync your [agent conversations](/agent-platform/local-agents/interacting-with-agents/) to the cloud, making them accessible across devices, shareable with teammates, and persistent even after logging out. This enables you to pick up where you left off on any machine, share context with collaborators, and access past [cloud agent](/agent-platform/cloud-agents/overview/) conversations. +Warp can sync your [agent conversations](/agent-platform/local-agents/interacting-with-agents/) to the cloud, making them accessible across devices, shareable with teammates, and persistent even after logging out. This enables you to pick up where you left off on any machine, share context with collaborators, and access past [cloud agent](/platform/) conversations. ## Key capabilities @@ -93,7 +93,7 @@ Cloud-synced conversations store snapshots of conversation data. For real-time c ## Cloud agent conversations -[Cloud agents](/agent-platform/cloud-agents/overview/) run in the cloud, and their conversations are automatically stored regardless of your local cloud conversations setting. +[Cloud agents](/platform/) run in the cloud, and their conversations are automatically stored regardless of your local cloud conversations setting. ### Accessing cloud agent conversations @@ -135,5 +135,5 @@ When you delete a conversation, it is removed permanently and immediately. Make * [Interacting with Agents](/agent-platform/local-agents/interacting-with-agents/) - Learn about conversation mechanics, follow-ups, and context windows. * [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. +* [Cloud Agents overview](/platform/) - Run agents in the cloud from triggers, schedules, or integrations. +* [Handoff between local and cloud agents](/platform/handoff/) - Promote a local conversation to a cloud agent run, or continue a finished cloud run. diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/prompt-queueing.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/prompt-queueing.mdx index d2c253a6a..429444c3e 100644 --- a/src/content/docs/agent-platform/local-agents/interacting-with-agents/prompt-queueing.mdx +++ b/src/content/docs/agent-platform/local-agents/interacting-with-agents/prompt-queueing.mdx @@ -109,7 +109,7 @@ Any remaining prompts stay in the panel so you can review, edit, reorder, or del ## Prompt queueing with cloud agents -Prompt queueing also works for [cloud agents](/agent-platform/cloud-agents/overview/), including while a cloud environment is still setting up. You can queue follow-up work before the agent is live, and Warp sends those prompts once the agent is ready and the current response finishes. +Prompt queueing also works for [cloud agents](/platform/), including while a cloud environment is still setting up. You can queue follow-up work before the agent is live, and Warp sends those prompts once the agent is ready and the current response finishes. For cloud agents, the prompt that started the run appears as a locked first row in the queue because it has already been accepted by the agent. You can't edit, reorder, or delete that first prompt, but any follow-up prompts queued behind it remain editable. @@ -126,4 +126,4 @@ Because cloud conversations keep running after you leave the agent view, their q * [Slash Commands](/agent-platform/capabilities/slash-commands/) - The full list of built-in commands, including `/queue`. * [Terminal and Agent modes](/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes/) - How input is routed between the terminal and the agent. -* [Cloud agents overview](/agent-platform/cloud-agents/overview/) - Run agents in the cloud from any trigger. +* [Cloud agents overview](/platform/) - Run agents in the cloud from any trigger. diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx index ab883360b..dc46ff2f9 100644 --- a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx +++ b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx @@ -122,7 +122,7 @@ To start a cloud agent conversation, press `⌥⌘↩` (Option+Command+Enter on Cloud agent conversations have a few differences from local conversations: -* **Environment selector** - Choose which [Warp Environment](/agent-platform/cloud-agents/environments/) to run in +* **Environment selector** - Choose which [Warp Environment](/platform/environments/) to run in * **Credits indicator** - Shows your remaining cloud agent credits * **Different zero state** - The conversation header indicates "New cloud agent conversation" @@ -131,10 +131,10 @@ Cloud agent conversations are always stored in the cloud. For more details on ac **Accessing running or past cloud conversations:** * **From the conversation list panel** - Cloud conversations appear alongside local conversations. Click to open. -* **From the management view** - Use the [Agent Management view](/agent-platform/cloud-agents/managing-cloud-agents/) to see all cloud agent runs, filter by status, and click any row to open the conversation. +* **From the management view** - Use the [Agent Management view](/platform/managing-cloud-agents/) to see all cloud agent runs, filter by status, and click any row to open the conversation. * **From the Oz web app** - Access your cloud agents from the [Oz web app](https://oz.warp.dev) to manage runs from any browser. -For more on cloud agents, see [Cloud Agents overview](/agent-platform/cloud-agents/overview/). +For more on cloud agents, see [Cloud Agents overview](/platform/). --- diff --git a/src/content/docs/agent-platform/local-agents/interactive-code-review.mdx b/src/content/docs/agent-platform/local-agents/interactive-code-review.mdx index a32197cc5..3bec24655 100644 --- a/src/content/docs/agent-platform/local-agents/interactive-code-review.mdx +++ b/src/content/docs/agent-platform/local-agents/interactive-code-review.mdx @@ -78,6 +78,6 @@ This workflow can be repeated until the code matches your expectations. Once you're comfortable reviewing agent code locally, try running agents in the cloud for longer or parallel tasks. -* **[Cloud Agents quickstart](/agent-platform/cloud-agents/quickstart/)** - Run agents on Warp's infrastructure for background tasks like PR review, issue triage, and dependency updates. +* **[Cloud Agents quickstart](/platform/quickstart/)** - Run agents on Warp's infrastructure for background tasks like PR review, issue triage, and dependency updates. * **[Attach agent session context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/)** - Share the agent's prompt, plan, commands, logs, validation, and reviewer asks with the PR. * **[Skills](/agent-platform/capabilities/skills/)** - Turn successful agent workflows into reusable, shareable instructions. diff --git a/src/content/docs/agent-platform/local-agents/session-sharing.mdx b/src/content/docs/agent-platform/local-agents/session-sharing.mdx index cca72ba2d..5e2b95c99 100644 --- a/src/content/docs/agent-platform/local-agents/session-sharing.mdx +++ b/src/content/docs/agent-platform/local-agents/session-sharing.mdx @@ -101,6 +101,6 @@ Multiple participants can join the same session from different machines, browser * [Remote Control](/agent-platform/cli-agents/remote-control/) * [Third-party CLI agents](/agent-platform/cli-agents/overview/) -* [Cloud Agent Session Sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) +* [Cloud Agent Session Sharing](/platform/viewing-cloud-agent-runs/) * [Attach agent session context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/) * [Session Sharing (terminal)](/knowledge-and-collaboration/session-sharing/) diff --git a/src/content/docs/changelog/2025.mdx b/src/content/docs/changelog/2025.mdx index e72bd6457..b76dfe370 100644 --- a/src/content/docs/changelog/2025.mdx +++ b/src/content/docs/changelog/2025.mdx @@ -68,7 +68,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * [Full Terminal Use](/agent-platform/capabilities/full-terminal-use/): Let the agent use the terminal as you would: interact with REPLs, debuggers, and full-screen apps like `top`. Warp is the only product on the market with Full Terminal Use capabilities. * [`/plan`](/agent-platform/capabilities/planning/): do spec-driven development in Warp. Work with an agent to align on an implementation plan that can be saved, versioned, and even attached to a PR for teammates. * [Interactive Code Review](/agent-platform/local-agents/interactive-code-review/): Review an agent's code like you would a teammate's, directly in Warp, and ask the agent to address the comments. -* [Slack and Linear integrations](https://docs.warp.dev/agent-platform/cloud-agents/integrations):\*\* Ask the agent to get to work from the tools you already use, track their progress, and take the wheel via live session sharing. +* [Slack and Linear integrations](https://docs.warp.dev/platform/integrations):\*\* Ask the agent to get to work from the tools you already use, track their progress, and take the wheel via live session sharing. * Warp's Agents can now [search the web](/agent-platform/capabilities/web-search/) to retrieve information, when relevant. This capability is configurable via Agent Profiles. ### 2025.11.12 (v0.2025.11.12.08.12) diff --git a/src/content/docs/changelog/2026.mdx b/src/content/docs/changelog/2026.mdx index 525ed6b32..92ce8e494 100644 --- a/src/content/docs/changelog/2026.mdx +++ b/src/content/docs/changelog/2026.mdx @@ -1058,10 +1058,10 @@ Oz is Warp's orchestration platform for cloud agents: launch parallel agents, au #### Cloud Agents -* **Run Cloud Agents from anywhere with built-in tracking** — start agents from Warp or via the CLI, triggers, or schedules. Every run is auditable and steerable. [Cloud Agents docs →](https://docs.warp.dev/agent-platform/cloud-agents/overview) -* **Cloud environments for consistent execution** — configure Docker-based environments (unlimited repos + setup commands) and run agents in isolated cloud sandboxes. [Environments docs →](https://docs.warp.dev/agent-platform/cloud-agents/environments) +* **Run Cloud Agents from anywhere with built-in tracking** — start agents from Warp or via the CLI, triggers, or schedules. Every run is auditable and steerable. [Cloud Agents docs →](https://docs.warp.dev/platform/) +* **Cloud environments for consistent execution** — configure Docker-based environments (unlimited repos + setup commands) and run agents in isolated cloud sandboxes. [Environments docs →](https://docs.warp.dev/platform/environments) * **Track agents from the web** — manage runs, create schedules, configure environments, and set up integrations from any browser in the [Oz web app](https://oz.warp.dev). -* **Schedule agents based on Skills** — run agents automatically on a cron schedule for code cleanup, dependency updates, and issue triage. See [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). +* **Schedule agents based on Skills** — run agents automatically on a cron schedule for code cleanup, dependency updates, and issue triage. See [Scheduled Agents](/platform/triggers/scheduled-agents/). * **Programmable by default** — orchestrate agents via the CLI and integrate Oz into tools and services via the [API and CLI reference](/reference/). #### Warp Upgrades diff --git a/src/content/docs/code/ssh-feature-support.mdx b/src/content/docs/code/ssh-feature-support.mdx index 4d83197cd..666244fad 100644 --- a/src/content/docs/code/ssh-feature-support.mdx +++ b/src/content/docs/code/ssh-feature-support.mdx @@ -38,7 +38,7 @@ The following features require the **SSH extension**: The following features are not yet available in Warpified remote (SSH) sessions: * **Language Server Protocol (LSP)** — [LSP features](/code/code-editor/language-server-protocol/) such as hover info, go-to-definition, and inline diagnostics are not available for remote files. SSH support is tracked in [GitHub #6831](https://github.com/warpdotdev/Warp/issues/6831). -* **Agent orchestration** — [Multi-agent runs](/agent-platform/cloud-agents/orchestration/) cannot be launched from a remote session; the Agent works as a single agent on the remote host. +* **Agent orchestration** — [Multi-agent runs](/platform/orchestration/) cannot be launched from a remote session; the Agent works as a single agent on the remote host. * **Computer use** — The Agent cannot take screenshots or interact with the remote machine's desktop. :::note diff --git a/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx b/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx index 19f9ae640..c8805b257 100644 --- a/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx +++ b/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx @@ -151,7 +151,7 @@ Consider the following when selecting a deployment model: ## Related resources -* [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) - Detailed patterns for CLI-only, Oz-hosted, and self-hosted setups +* [Deployment Patterns](/platform/deployment-patterns/) - Detailed patterns for CLI-only, Oz-hosted, and self-hosted setups * [Security overview](/enterprise/security-and-compliance/security-overview/) - Data handling, encryption, and compliance details * [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) - Route inference through your own cloud infrastructure * [Admin Panel](/enterprise/team-management/admin-panel/) - Configure agent policies and security settings diff --git a/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx b/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx index 94f1d1211..609cf53a1 100644 --- a/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx +++ b/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx @@ -169,7 +169,7 @@ The role setup has two parts: #### Trust policy requirements -This trust policy authorizes any cloud-hosted run from your team. The `sub` claim Warp signs has the shape `scoped_principal:<team-uid>/<actor-type>:<principal-uid>`, where `<actor-type>` is `user` for user-triggered runs or `service_account` for [cloud agent](/agent-platform/cloud-agents/agents/) runs. The `<team-uid>/*` pattern below covers both. +This trust policy authorizes any cloud-hosted run from your team. The `sub` claim Warp signs has the shape `scoped_principal:<team-uid>/<actor-type>:<principal-uid>`, where `<actor-type>` is `user` for user-triggered runs or `service_account` for [cloud agent](/platform/agents/) runs. The `<team-uid>/*` pattern below covers both. **Example trust policy** @@ -253,7 +253,7 @@ To safely test BYOLLM, configure it on a single named agent first. Misconfigurat In the Oz web app: -1. [Create a new agent](/agent-platform/cloud-agents/oz-web-app/#creating-a-new-agent) or edit an existing one. +1. [Create a new agent](/platform/oz-web-app/#creating-a-new-agent) or edit an existing one. 2. In the agent form, expand the **AWS Bedrock** section. 3. Choose **Custom** and paste the IAM role ARN from Step 2. 4. Ensure the agent's default model is one that's enabled for Bedrock under the Admin Panel **Models** page. diff --git a/src/content/docs/enterprise/getting-started/getting-started-developers.mdx b/src/content/docs/enterprise/getting-started/getting-started-developers.mdx index 155bb91b9..87a65d2c9 100644 --- a/src/content/docs/enterprise/getting-started/getting-started-developers.mdx +++ b/src/content/docs/enterprise/getting-started/getting-started-developers.mdx @@ -250,7 +250,7 @@ For common login, SSO, and access issues, see the [Enterprise FAQ](/enterprise/g Now that you're set up: -* **Explore agent capabilities** - Learn about [agents in Warp](/agent-platform/local-agents/overview/) and [cloud agents](/agent-platform/cloud-agents/overview/) +* **Explore agent capabilities** - Learn about [agents in Warp](/agent-platform/local-agents/overview/) and [cloud agents](/platform/) * **Contribute to team knowledge** - Add useful Workflows, Prompts, and Rules to your team's Warp Drive to compound productivity gains across your team * **Stay updated** - Check the [Warp changelog](/changelog/) for new features diff --git a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx index a7ccf73f6..e28d85b02 100644 --- a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx +++ b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx @@ -163,7 +163,7 @@ Once your team is set up: * **Agent Profiles** - Configure default [Agent Profiles](/agent-platform/capabilities/agent-profiles-permissions/) for different types of work to give teams appropriate autonomy and control * **BYOLLM** - Set up [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) to route inference through your cloud infrastructure for data locality and cost control * **Monitor usage** - Review usage analytics in the Admin Panel to track adoption and measure engineering productivity gains -* **Self-hosting** - Run agents on your own infrastructure to control where agents run and keep repository clones on your own machines. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions +* **Self-hosting** - Run agents on your own infrastructure to control where agents run and keep repository clones on your own machines. See [Self-hosting](/platform/self-hosting/) for setup instructions ## Troubleshooting diff --git a/src/content/docs/enterprise/getting-started/quickstart.mdx b/src/content/docs/enterprise/getting-started/quickstart.mdx index 18eee4377..073248e76 100644 --- a/src/content/docs/enterprise/getting-started/quickstart.mdx +++ b/src/content/docs/enterprise/getting-started/quickstart.mdx @@ -93,5 +93,5 @@ Monitor and steer cloud agents from the Oz dashboard or directly in Warp. ## Next steps * **Set up key features** - Follow the full [Getting started for developers](/enterprise/getting-started/getting-started-developers/) guide to configure Codebase Context, Warp Drive, MCP integrations, and Agent Profiles. -* **Explore cloud agents** - Learn about [cloud agents](/agent-platform/cloud-agents/overview/) for background automation and parallel workflows. +* **Explore cloud agents** - Learn about [cloud agents](/platform/) for background automation and parallel workflows. * **Explore guides** - Visit [Warp Guides](/guides/) for video tutorials and end-to-end workflows. diff --git a/src/content/docs/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index 9ab7145a9..057059da3 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -39,7 +39,7 @@ On Enterprise plans, local and cloud agent usage both draw from the same team cr For agent API key runs (e.g., CI/CD pipelines, scheduled tasks), credits also draw from the team's shared pool since these runs are not tied to any individual user. -For more details, see [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/). +For more details, see [Access, Billing, and Identity](/platform/team-access-billing-and-identity/). ## BYOLLM billing diff --git a/src/content/docs/enterprise/team-management/admin-panel.mdx b/src/content/docs/enterprise/team-management/admin-panel.mdx index 2af958a08..68c925970 100644 --- a/src/content/docs/enterprise/team-management/admin-panel.mdx +++ b/src/content/docs/enterprise/team-management/admin-panel.mdx @@ -278,7 +278,7 @@ To configure: The organizations and repository access shown here reflect the Oz by Warp GitHub App installation scope, which is configured in [GitHub settings](https://github.com/settings/installations). To change which repositories the app can access, edit the installation directly in GitHub. :::note -This setting controls GitHub access for agent API key runs only. Runs triggered by individual users (via personal API key, Slack, or Linear) continue to use that user's personal GitHub token. For more details, see [Team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization). +This setting controls GitHub access for agent API key runs only. Runs triggered by individual users (via personal API key, Slack, or Linear) continue to use that user's personal GitHub token. For more details, see [Team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization). ::: ## Multi-admin functionality diff --git a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx index 835a2f366..2db68162f 100644 --- a/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx +++ b/src/content/docs/getting-started/migrate-to-warp/migrate-to-warp-from-claude-code.mdx @@ -75,7 +75,7 @@ Warp's Agent also pulls context from several other explicit sources: * **Tight terminal integration.** Agent Mode runs inside Warp and sees the full state of your terminal session — open files, command history, environment variables — without needing you to paste context. * **Parallel agents.** Warp runs multiple agent conversations across tabs simultaneously, each with its own state, which you can track in the Agent Management Panel. * **Code Review built in.** Agent-generated diffs open in Warp's [Code Review](/code/code-review/) panel, not the terminal. -* **Cloud orchestration.** Long-running or scheduled agent work can be offloaded to [Oz](/agent-platform/cloud-agents/overview/). +* **Cloud orchestration.** Long-running or scheduled agent work can be offloaded to [Oz](/platform/). ## Warp-native equivalents diff --git a/src/content/docs/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs.mdx b/src/content/docs/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs.mdx index 702153471..cfde6116a 100644 --- a/src/content/docs/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs.mdx @@ -18,7 +18,7 @@ Add a Warp session or cloud agent run link to the PR description or a PR comment Use these Warp docs and surfaces to collect the right context: * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) for local Warp agents or third-party CLI agents running in Warp. -* [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for cloud agent runs started from Slack, Linear, GitHub Actions, schedules, the Oz CLI, or the API. +* [Cloud agent session sharing](/platform/viewing-cloud-agent-runs/) for cloud agent runs started from Slack, Linear, GitHub Actions, schedules, the Oz CLI, or the API. * The [Code Review panel](/code/code-review/) and [Interactive Code Review](/agent-platform/local-agents/interactive-code-review/) to inspect and refine the actual code diff before or after you share the PR. ## What to include in the PR @@ -71,12 +71,12 @@ See [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) for t If the agent ran in the cloud, use the cloud run session link: -1. Open the run from the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs). +1. Open the run from the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/platform/oz-web-app/#runs). 2. Confirm the session shows the run context reviewers need. 3. Copy the cloud agent session link. 4. Paste the link into the PR description or a PR comment. -See [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for details. +See [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) for details. ## 2. Review the diff before handing it off @@ -130,6 +130,6 @@ Avoid vague asks like "review the agent output." Point reviewers to the decision ## Next steps * Use [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) to share local or third-party agent sessions. -* Use [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) to inspect cloud agent runs. +* Use [Cloud agent session sharing](/platform/viewing-cloud-agent-runs/) to inspect cloud agent runs. * Use [Code Review panel](/code/code-review/) to review Git diffs in Warp. * Use [Interactive Code Review](/agent-platform/local-agents/interactive-code-review/) to leave inline comments and send feedback back to an agent. diff --git a/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx b/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx index 11c1f3ccc..825d5500d 100644 --- a/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-run-3-agents-in-parallel-summarize-logs-analyze-pr-modify-ui.mdx @@ -67,7 +67,7 @@ In the demo, we run three parallel workflows: 2. #### Monitor all agents The **task pane** in Warp shows all running agents.\ - You can view plans, progress, and results live without interrupting other tasks. To track these runs across your account and team in real time, including cloud agent runs, open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app. + You can view plans, progress, and results live without interrupting other tasks. To track these runs across your account and team in real time, including cloud agent runs, open the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app. 3. #### Review results @@ -92,4 +92,4 @@ In the demo, we run three parallel workflows: ### Next steps * [How to run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/) - Decompose tasks, assign Git worktrees, validate output, and hand off branches or PRs for review. -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) - Fan parallel work out to cloud child agents when a task is too large or slow to run locally. +* [Multi-agent orchestration](/platform/orchestration/) - Fan parallel work out to cloud child agents when a task is too large or slow to run locally. diff --git a/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx b/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx index da177d24b..77cad2abc 100644 --- a/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-run-multiple-ai-coding-agents.mdx @@ -19,7 +19,7 @@ Use multiple coding agents, including Warp Agent, Claude Code, Codex, and other The best multi-agent workflows have one thing in common: each agent owns a clear slice of work, reports back with validation results, and hands off a branch, diff, PR, or concise finding you can review. -Plan on about 15 minutes for the local setup. Cloud orchestration takes longer only if you need to create or select an [environment](/agent-platform/cloud-agents/environments/) first. +Plan on about 15 minutes for the local setup. Cloud orchestration takes longer only if you need to create or select an [environment](/platform/environments/) first. ## Prerequisites @@ -33,8 +33,8 @@ Plan on about 15 minutes for the local setup. Cloud orchestration takes longer o | Same task, different agents | You want to compare approaches or pick the best implementation. | Run each agent in a separate tab and worktree, then compare diffs in the [Code Review panel](/code/code-review/). | | Split by file or subsystem | A feature spans independent modules that can be changed in parallel. | Assign each agent a worktree, branch, file boundary, and validation command. | | Builder plus reviewer | One agent implements while another reviews, writes tests, or checks edge cases. | Put the reviewer in a read-only or review-focused tab, or use a separate branch for test-only changes. | -| Cloud fan-out | The work is large, slow, or can run away from your laptop. | Use [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) or [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/) to spawn cloud children. | -| Repeatable fleet workflow | You want the same agent pattern on every PR, issue, schedule, or release. | Use a cloud agent with a trigger, skill, or API workflow, then inspect parent and child runs in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/). | +| Cloud fan-out | The work is large, slow, or can run away from your laptop. | Use [Multi-agent orchestration](/platform/orchestration/) or [Running orchestrated agents](/platform/orchestration/multi-agent-runs/) to spawn cloud children. | +| Repeatable fleet workflow | You want the same agent pattern on every PR, issue, schedule, or release. | Use a cloud agent with a trigger, skill, or API workflow, then inspect parent and child runs in the [Oz web app](/platform/oz-web-app/). | ## Plan the split before launching agents @@ -213,8 +213,8 @@ Use cloud agents when the work is long-running, resource-intensive, easy to shar ``` 2. Use `/plan` for larger changes where you want to review the plan, orchestration config, child ownership, and merge strategy before agents launch. -3. For repeatable or unattended workflows, start the parent from the Oz CLI, the Oz web app, or the Oz API. See [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/) for launch options. -4. Inspect parent and child runs from the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) or the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app. +3. For repeatable or unattended workflows, start the parent from the Oz CLI, the Oz web app, or the Oz API. See [Running orchestrated agents](/platform/orchestration/multi-agent-runs/) for launch options. +4. Inspect parent and child runs from the [Oz web app](/platform/oz-web-app/) or the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app. Cloud orchestration is the best fit when you need: @@ -250,8 +250,8 @@ Explore related guides and features: * [How to review AI-generated code](/guides/agent-workflows/how-to-review-ai-generated-code/) — review and refine the code your agents produced * [Attach agent session context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/) — give reviewers the agent context behind a PR -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) — coordinate parent and child agents across local and cloud runs -* [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/) — start orchestrated runs from Warp, the Oz CLI, the Oz web app, or the Oz API +* [Multi-agent orchestration](/platform/orchestration/) — coordinate parent and child agents across local and cloud runs +* [Running orchestrated agents](/platform/orchestration/multi-agent-runs/) — start orchestrated runs from Warp, the Oz CLI, the Oz web app, or the Oz API * [Set up Claude Code](/guides/external-tools/how-to-set-up-claude-code/) or [Set up Codex CLI](/guides/external-tools/how-to-set-up-codex-cli/) — install both agents if you haven't already * [Claude Code in Warp](https://www.warp.dev/agents/claude-code) — overview of Claude Code support in Warp * [Codex in Warp](https://www.warp.dev/agents/codex) — overview of Codex support in Warp diff --git a/src/content/docs/guides/agent-workflows/how-to-run-unattended-agents.mdx b/src/content/docs/guides/agent-workflows/how-to-run-unattended-agents.mdx index 6b9bc1880..00152c119 100644 --- a/src/content/docs/guides/agent-workflows/how-to-run-unattended-agents.mdx +++ b/src/content/docs/guides/agent-workflows/how-to-run-unattended-agents.mdx @@ -14,7 +14,7 @@ tags: Warp cloud agents can run unattended from schedules, team tools, CI, the Oz CLI, or the API. Use them when you want an agent to keep working after you leave your terminal, react to external events, or run recurring maintenance without a human starting each run. -Every unattended workflow creates a cloud agent run that your team can inspect later. Open runs from the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs), the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app, or the session link posted back to the tool that triggered the agent. +Every unattended workflow creates a cloud agent run that your team can inspect later. Open runs from the [Runs page in the Oz web app](/platform/oz-web-app/#runs), the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app, or the session link posted back to the tool that triggered the agent. ## Choose a trigger @@ -22,10 +22,10 @@ Use this table to decide where an unattended agent should start. | Trigger | Use it when | Where to configure | Where to inspect | | ------- | ----------- | ------------------ | ---------------- | -| Scheduled agents | Work should run on a predictable cadence, like weekly triage, nightly dependency checks, or monthly cleanup. | [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) or the [Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/) | Oz web app Runs page, Agent Management Panel in the Warp app, schedule history, and cloud agent session links | -| Slack | A teammate should delegate work from a Slack message or thread. | [Slack integration](/agent-platform/cloud-agents/integrations/slack/) | Slack thread updates, Oz web app Runs page, Agent Management Panel in the Warp app, and the shared run session | -| Linear | An issue, comment, or assignment should start the agent. | [Linear integration](/agent-platform/cloud-agents/integrations/linear/) | Linear issue updates, Oz web app Runs page, Agent Management Panel in the Warp app, and the shared run session | -| GitHub Actions | A repository event, PR workflow, issue workflow, or CI failure should start the agent. | [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) | GitHub Actions logs, PR or issue comments, Oz web app, and cloud agent runs | +| Scheduled agents | Work should run on a predictable cadence, like weekly triage, nightly dependency checks, or monthly cleanup. | [Scheduled Agents](/platform/triggers/scheduled-agents/) or the [Scheduled Agents quickstart](/platform/triggers/scheduled-agents-quickstart/) | Oz web app Runs page, Agent Management Panel in the Warp app, schedule history, and cloud agent session links | +| Slack | A teammate should delegate work from a Slack message or thread. | [Slack integration](/platform/integrations/slack/) | Slack thread updates, Oz web app Runs page, Agent Management Panel in the Warp app, and the shared run session | +| Linear | An issue, comment, or assignment should start the agent. | [Linear integration](/platform/integrations/linear/) | Linear issue updates, Oz web app Runs page, Agent Management Panel in the Warp app, and the shared run session | +| GitHub Actions | A repository event, PR workflow, issue workflow, or CI failure should start the agent. | [GitHub Actions](/platform/integrations/github-actions/) | GitHub Actions logs, PR or issue comments, Oz web app, and cloud agent runs | | Oz CLI | You want to start a named cloud run from a terminal, script, or local automation. | [Oz CLI](/reference/cli/#running-agents-remotely-oz-agent-run-cloud) | CLI output, Oz web app Runs page, Agent Management Panel in the Warp app, and cloud agent session links | | Oz API or SDK | Your internal system should create, query, or monitor runs programmatically. | [Oz API and SDK](/reference/api-and-sdk/) | Your system, API results, Oz web app, and run sessions | @@ -33,7 +33,7 @@ Use this table to decide where an unattended agent should start. ### Run recurring maintenance -Use [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) for tasks that should happen on a fixed cadence. Good fits include: +Use [Scheduled Agents](/platform/triggers/scheduled-agents/) for tasks that should happen on a fixed cadence. Good fits include: * dependency update checks * stale issue or PR triage @@ -45,7 +45,7 @@ Each scheduled run starts a fresh cloud agent session and records its own task h ### Delegate work from Slack or Linear -Use [Slack](/agent-platform/cloud-agents/integrations/slack/) or [Linear](/agent-platform/cloud-agents/integrations/linear/) when the task starts from team conversation or issue context. These integrations are best for: +Use [Slack](/platform/integrations/slack/) or [Linear](/platform/integrations/linear/) when the task starts from team conversation or issue context. These integrations are best for: * turning a Slack thread into an implementation task * asking an agent to investigate a Linear issue @@ -56,7 +56,7 @@ The agent posts progress updates back to the source thread or issue and provides ### React to GitHub events -Use [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) when the trigger should be tied to a repository event. +Use [GitHub Actions](/platform/integrations/github-actions/) when the trigger should be tied to a repository event. For example: @@ -97,9 +97,9 @@ If the agent can change code or infrastructure, keep the instructions narrow and Unattended does not mean invisible. Use these surfaces to review what happened: -* [Oz web app](/agent-platform/cloud-agents/oz-web-app/) - View runs, schedules, run metadata, and session transcripts from a browser or mobile device. -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Filter runs by source, status, day, creator, or trigger. -* [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) - Inspect the prompt, plan, commands, logs, output, and follow-up messages where available. +* [Oz web app](/platform/oz-web-app/) - View runs, schedules, run metadata, and session transcripts from a browser or mobile device. +* [Managing cloud agents](/platform/managing-cloud-agents/) - Filter runs by source, status, day, creator, or trigger. +* [Cloud agent session sharing](/platform/viewing-cloud-agent-runs/) - Inspect the prompt, plan, commands, logs, output, and follow-up messages where available. * [Oz API and SDK](/reference/api-and-sdk/) - Query runs and build internal monitoring around status, runtime, or outcomes. When a run creates a PR, include the cloud run link in the PR description or a comment. See [Attach agent session context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/) for a template. @@ -118,7 +118,7 @@ Start with one narrow workflow before deploying many unattended agents: ## Next steps -* [Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/) - Create your first recurring agent in the Oz web app. -* [Integrations quickstart](/agent-platform/cloud-agents/integrations/quickstart/) - Trigger agents from Slack or Linear. -* [GitHub Actions quickstart](/agent-platform/cloud-agents/integrations/quickstart-github-actions/) - Add an agent to a PR review workflow. -* [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) - Inspect and share unattended run sessions. +* [Scheduled Agents quickstart](/platform/triggers/scheduled-agents-quickstart/) - Create your first recurring agent in the Oz web app. +* [Integrations quickstart](/platform/integrations/quickstart/) - Trigger agents from Slack or Linear. +* [GitHub Actions quickstart](/platform/integrations/quickstart-github-actions/) - Add an agent to a PR review workflow. +* [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) - Inspect and share unattended run sessions. diff --git a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx index f5f8ca932..c5dd513c6 100644 --- a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx +++ b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx @@ -94,6 +94,6 @@ Open the Agent Mode Dashboard to see: * Completed tasks * Logs and outputs -You can refine or cancel tasks mid-run if needed, or switch back to manual commands. To track these runs across your account and team, including cloud agent runs, open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app. +You can refine or cancel tasks mid-run if needed, or switch back to manual commands. To track these runs across your account and team, including cloud agent runs, open the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app. For a workflow-oriented setup guide that covers task decomposition, worktrees, cloud orchestration, validation, and review handoff, see [How to run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/). diff --git a/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx b/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx index 81c3a265c..54926b41e 100644 --- a/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx +++ b/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx @@ -179,7 +179,7 @@ The `analysis-artifacts` Skill is largely stack-agnostic. It structures outputs, You installed two community Skills, customized the model index for your warehouse, and ran both a simple lookup and a full deep-dive analysis. -**Extend to Slack.** Wire the same two Skills into a cloud agent configured with your dbt repo, and your teammates can ask data questions by @-mentioning Oz in a Slack channel, without opening a terminal. The agent clones the repo, picks up the Skills from `.agents/skills/`, and replies in-thread. See the [Slack integration docs](https://docs.warp.dev/agent-platform/cloud-agents/integrations/slack/) and [Skills as Agents](https://docs.warp.dev/agent-platform/cloud-agents/skills-as-agents/) for setup. +**Extend to Slack.** Wire the same two Skills into a cloud agent configured with your dbt repo, and your teammates can ask data questions by @-mentioning Oz in a Slack channel, without opening a terminal. The agent clones the repo, picks up the Skills from `.agents/skills/`, and replies in-thread. See the [Slack integration docs](https://docs.warp.dev/platform/integrations/slack/) and [Skills as Agents](https://docs.warp.dev/platform/skills-as-agents/) for setup. Explore related guides and features: diff --git a/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx b/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx index b872fc2f6..e8c665a7a 100644 --- a/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx +++ b/src/content/docs/guides/external-tools/using-mcp-servers-with-warp.mdx @@ -28,8 +28,8 @@ Use this guide to choose the right setup path, then jump to the source docs for | -------- | ----------- | ------------------ | ----------- | | Local Warp agent | You are working interactively in Warp and want the agent to use tools from your machine or desktop-authenticated services. | Warp MCP settings, Warp Drive MCP servers, `.warp/.mcp.json`, or provider config files. | [Model Context Protocol (MCP)](/agent-platform/capabilities/mcp/) | | Third-party CLI agent in Warp | You run Claude Code, Codex, OpenCode, or another CLI agent in Warp and want shared MCP config across tools. | File-based MCP config that Warp can detect and approve. | [File-based MCP servers](/agent-platform/capabilities/mcp/#file-based-mcp-servers) | -| Cloud agent run | The agent runs in a cloud environment from Slack, Linear, schedules, GitHub Actions, the CLI, or the API. | `--mcp`, an agent config file, or a Warp-shared MCP UUID. | [MCP Servers for cloud agents](/agent-platform/cloud-agents/mcp/) | -| Repeatable automation | You need the same MCP tools every time a scheduled agent, integration, or CI workflow runs. | Agent config files plus [Agent Secrets](/agent-platform/cloud-agents/secrets/) for credentials. | [MCP servers (CLI reference)](/reference/cli/mcp-servers/) | +| Cloud agent run | The agent runs in a cloud environment from Slack, Linear, schedules, GitHub Actions, the CLI, or the API. | `--mcp`, an agent config file, or a Warp-shared MCP UUID. | [MCP Servers for cloud agents](/platform/mcp/) | +| Repeatable automation | You need the same MCP tools every time a scheduled agent, integration, or CI workflow runs. | Agent config files plus [Agent Secrets](/platform/secrets/) for credentials. | [MCP servers (CLI reference)](/reference/cli/mcp-servers/) | ## Common MCP workflows @@ -54,12 +54,12 @@ Use cloud MCP when an unattended or remote agent needs tool access while it runs Example workflow: 1. Create or identify the MCP server the cloud agent should use. -2. Store required credentials as [Agent Secrets](/agent-platform/cloud-agents/secrets/) instead of hardcoding tokens in config files. +2. Store required credentials as [Agent Secrets](/platform/secrets/) instead of hardcoding tokens in config files. 3. Attach the MCP server with `--mcp`, a config file, or a Warp-shared MCP UUID. 4. Run the cloud agent from the Oz CLI, Slack, Linear, GitHub Actions, a schedule, or the API. -5. Inspect the run in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) or [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). +5. Inspect the run in the [Oz web app](/platform/oz-web-app/) or [Cloud agent session sharing](/platform/viewing-cloud-agent-runs/). -For schema and cloud-specific limitations, see [MCP Servers for cloud agents](/agent-platform/cloud-agents/mcp/). +For schema and cloud-specific limitations, see [MCP Servers for cloud agents](/platform/mcp/). ### Share an MCP server with a team @@ -101,7 +101,7 @@ For cloud agents, choose one of these paths: * **JSON file** - Best for reusable scripts. * **Agent config file** - Best for production workflows where model, environment, prompt, and MCP servers should live together. -Cloud agents run away from your desktop. Any secrets required by MCP tools should be available in the cloud run through [Agent Secrets](/agent-platform/cloud-agents/secrets/) or the execution environment, not only in your local shell. +Cloud agents run away from your desktop. Any secrets required by MCP tools should be available in the cloud run through [Agent Secrets](/platform/secrets/) or the execution environment, not only in your local shell. :::caution OAuth-based MCP servers are not currently supported directly for cloud agents. If a server requires browser-based OAuth, use it with a local agent, choose a token-based/server-side configuration if the provider supports it, or pass the relevant artifact as context another way. @@ -126,7 +126,7 @@ Before giving an agent tool access through MCP: * Use the narrowest credentials and scopes that let the workflow run. * Prefer service accounts for team or scheduled workflows. -* Store cloud-run credentials in [Agent Secrets](/agent-platform/cloud-agents/secrets/). +* Store cloud-run credentials in [Agent Secrets](/platform/secrets/). * Review file-based MCP config before approving it, especially commands, args, environment variables, and URLs. * Treat MCP logs as sensitive if they contain API responses, tokens, request headers, or private data. * For cloud agents, confirm whether the MCP server can be reached from the cloud environment or self-hosted worker. @@ -134,6 +134,6 @@ Before giving an agent tool access through MCP: ## Next steps * [Model Context Protocol (MCP)](/agent-platform/capabilities/mcp/) - Configure MCP servers for local agents in the Warp app. -* [MCP Servers for cloud agents](/agent-platform/cloud-agents/mcp/) - Configure MCP servers for cloud runs and automation. +* [MCP Servers for cloud agents](/platform/mcp/) - Configure MCP servers for cloud runs and automation. * [MCP servers (CLI reference)](/reference/cli/mcp-servers/) - Use `--mcp` with UUIDs, inline JSON, or files. -* [Agent Secrets](/agent-platform/cloud-agents/secrets/) - Store credentials for cloud agent runs. \ No newline at end of file +* [Agent Secrets](/platform/secrets/) - Store credentials for cloud agent runs. \ No newline at end of file diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx index 4a29963f1..d505a68a6 100644 --- a/src/content/docs/index.mdx +++ b/src/content/docs/index.mdx @@ -62,7 +62,7 @@ Cloud agents run in the background on Warp's infrastructure (or your own) for au Cloud agents are ideal for work that doesn't need your immediate attention, like PR reviews, issue triage, routine maintenance, and integration-driven workflows. -→ [Learn about cloud agents](/agent-platform/cloud-agents/overview/) +→ [Learn about cloud agents](/platform/) --- @@ -105,5 +105,5 @@ Warp's AI features can be globally disabled in **Settings** > **Agents** > **War * [**Quickstart**](/quickstart/): Get Warp installed and start coding * [**Warp Agents overview**](/agent-platform/local-agents/overview/): Explore all AI features available in Warp -* [**Cloud Agents overview**](/agent-platform/cloud-agents/overview/): Set up background automation -* [**Oz Platform**](/agent-platform/cloud-agents/platform/): Learn about the CLI, API, SDK, and infrastructure +* [**Cloud Agents overview**](/platform/): Set up background automation +* [**Oz Platform**](/platform/overview/): Learn about the CLI, API, SDK, and infrastructure diff --git a/src/content/docs/knowledge-and-collaboration/session-sharing/index.mdx b/src/content/docs/knowledge-and-collaboration/session-sharing/index.mdx index d45cfb249..3a0b1d0e2 100644 --- a/src/content/docs/knowledge-and-collaboration/session-sharing/index.mdx +++ b/src/content/docs/knowledge-and-collaboration/session-sharing/index.mdx @@ -8,4 +8,4 @@ description: >- Session sharing documentation has moved to the Agent Platform section. See the articles below for details on sharing sessions: * **[Agent Session Sharing](/agent-platform/local-agents/session-sharing/)** - Share agent sessions with your team for review and collaboration. -* **[Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/)** - Share session context from cloud agent runs. +* **[Viewing Cloud Agent Runs](/platform/viewing-cloud-agent-runs/)** - Share session context from cloud agent runs. diff --git a/src/content/docs/agent-platform/cloud-agents/agents.mdx b/src/content/docs/platform/agents.mdx similarity index 81% rename from src/content/docs/agent-platform/cloud-agents/agents.mdx rename to src/content/docs/platform/agents.mdx index 9c2e99dd7..b438cdee8 100644 --- a/src/content/docs/agent-platform/cloud-agents/agents.mdx +++ b/src/content/docs/platform/agents.mdx @@ -15,8 +15,8 @@ Every team starts with a default cloud agent, which is what runs when an automat A run executes as a cloud agent when it's authenticated with an [agent API key](/reference/cli/api-keys/) or when an agent is explicitly selected; otherwise it runs as the calling user. The triggers that can run as a cloud agent are: -* **Schedules** — Cron-style recurring runs. See [Scheduled agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). -* **Integrations** — Slack mentions, Linear issue updates, GitHub Actions workflow steps. See [Integrations](/agent-platform/cloud-agents/integrations/). +* **Schedules** — Cron-style recurring runs. See [Scheduled agents](/platform/triggers/scheduled-agents/). +* **Integrations** — Slack mentions, Linear issue updates, GitHub Actions workflow steps. See [Integrations](/platform/integrations/). * **API and SDK** — Programmatic runs from your own backend, scripts, or webhooks via the [Oz API](/reference/api-and-sdk/). * **CLI** — `oz agent run-cloud` from a developer machine, CI pipeline, or self-hosted worker. See the [Oz CLI](/reference/cli/). @@ -32,7 +32,7 @@ In the CLI and REST API, a cloud agent is represented as a **service account**. ## Managing cloud agents -Use the [Oz web app's Agents page](/agent-platform/cloud-agents/oz-web-app/#agents) for day-to-day management. Use the public API when you need to create or update agents from scripts, CI/CD, or internal tooling. Full request and response formats, including error codes, live on the [API Reference](/api) page under the **agent** tag. +Use the [Oz web app's Agents page](/platform/oz-web-app/#agents) for day-to-day management. Use the public API when you need to create or update agents from scripts, CI/CD, or internal tooling. Full request and response formats, including error codes, live on the [API Reference](/api) page under the **agent** tag. | Action | Endpoint | What it does | | --- | --- | --- | @@ -56,17 +56,17 @@ When a team is over its plan limit (for example, after downgrading), the extra a ## Where cloud agents appear in the product -* **Agents page** - The Agents page in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) is where teams view, create, edit, and delete cloud agents. +* **Agents page** - The Agents page in the [Oz web app](/platform/oz-web-app/) is where teams view, create, edit, and delete cloud agents. * **Agent picker** - Forms that start a new run or schedule include an **Agent** dropdown. **Quick run** is the default (runs execute as the calling user); picking a cloud agent runs as the cloud agent instead. * **Run filters and detail** - The Runs view lets you filter by cloud agent, and individual run detail pages show which agent executed the run. * **Admin Panel** - Billing usage in the [Admin Panel](/knowledge-and-collaboration/admin-panel/) attributes credits consumed by cloud agent runs to the team rather than to a person. ## Related pages -* [Triggers](/agent-platform/cloud-agents/triggers/) - How schedules, integrations, and API calls invoke cloud agents. -* [Environments](/agent-platform/cloud-agents/environments/) - The runtime context (Docker image, repos, setup commands) a cloud agent uses. +* [Triggers](/platform/triggers/) - How schedules, integrations, and API calls invoke cloud agents. +* [Environments](/platform/environments/) - The runtime context (Docker image, repos, setup commands) a cloud agent uses. * [API keys](/reference/cli/api-keys/) - Create personal and agent API keys. * [Oz API & SDK](/reference/api-and-sdk/) - Programmatic access to the cloud agent endpoints. * [Federated identity tokens](/reference/cli/federate/) - Issue OIDC tokens from inside a run. -* [Oz web app](/agent-platform/cloud-agents/oz-web-app/) - Manage cloud agents and inspect their runs in the web UI. +* [Oz web app](/platform/oz-web-app/) - Manage cloud agents and inspect their runs in the web UI. * [Admin Panel](/knowledge-and-collaboration/admin-panel/) - Team-level billing and access controls. diff --git a/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx b/src/content/docs/platform/deployment-patterns.mdx similarity index 82% rename from src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx rename to src/content/docs/platform/deployment-patterns.mdx index ef57a0b94..097fb2acb 100644 --- a/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx +++ b/src/content/docs/platform/deployment-patterns.mdx @@ -53,7 +53,7 @@ Use this when you already have a system that schedules work (CI, dev boxes, inte #### Minimal setup checklist * A Warp team -* A [cloud agent](/agent-platform/cloud-agents/agents/) (recommended for automation) +* A [cloud agent](/platform/agents/) (recommended for automation) * The Oz CLI installed on the runner / box * Any needed credentials (often via secrets + environment variables) @@ -63,7 +63,7 @@ Use this when you already have a system that schedules work (CI, dev boxes, inte Use this when you want Oz to run agent workloads on Warp-managed infrastructure, typically inside reproducible Docker environments, with built-in lifecycle management. -![Warp enterprise SaaS architecture showing customer infrastructure, isolated tenant sandboxes, Warp backend, and LLM providers](../../../../assets/agent-platform/cloud-agents-infra.png) +![Warp enterprise SaaS architecture showing customer infrastructure, isolated tenant sandboxes, Warp backend, and LLM providers](../../../assets/agent-platform/cloud-agents-infra.png) #### What it looks like @@ -101,7 +101,7 @@ Use this when you want Oz to run agent workloads on Warp-managed infrastructure, #### Example recipe: fan-out parallel work (sharding) -When a task is naturally divisible, use [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) to spawn one child agent per shard from a single parent run. The parent owns coordination and result aggregation; the children execute in parallel, each with their own repo subset, prompt, and (optionally) model. See [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/) for slash command, CLI, web app, and API examples. +When a task is naturally divisible, use [multi-agent orchestration](/platform/orchestration/) to spawn one child agent per shard from a single parent run. The parent owns coordination and result aggregation; the children execute in parallel, each with their own repo subset, prompt, and (optionally) model. See [Running orchestrated agents](/platform/orchestration/multi-agent-runs/) for slash command, CLI, web app, and API examples. #### Example recipe: same task across multiple models @@ -122,13 +122,13 @@ Think of self-hosted execution as **customer-hosted execution with Warp-hosted o Self-hosting has two architectures that differ on **who orchestrates agent runs** (both keep code and execution on your infrastructure): -* **[Managed](/agent-platform/cloud-agents/self-hosting/#managed-architecture)** — Oz orchestrates. You run the `oz-agent-worker` daemon; Oz routes runs to it from Slack, Linear, schedules, the API, or `oz agent run-cloud`. Tasks execute in Docker containers, Kubernetes Jobs, or directly on the host. -* **[Unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/)** — You orchestrate. Invoke `oz agent run` directly from your CI, Kubernetes, or dev environment. Warp provides session tracking and observability; it does not start or stop agents. +* **[Managed](/platform/self-hosting/#managed-architecture)** — Oz orchestrates. You run the `oz-agent-worker` daemon; Oz routes runs to it from Slack, Linear, schedules, the API, or `oz agent run-cloud`. Tasks execute in Docker containers, Kubernetes Jobs, or directly on the host. +* **[Unmanaged](/platform/self-hosting/unmanaged/)** — You orchestrate. Invoke `oz agent run` directly from your CI, Kubernetes, or dev environment. Warp provides session tracking and observability; it does not start or stop agents. Why teams choose self-hosted execution: * Code and execution must stay within your network boundary for compliance or security requirements. -* Agents need to access services behind a VPN or self-hosted SCMs like GitLab or Bitbucket. Warp-hosted agents can also access GitLab and Bitbucket over the public internet — see the [GitLab](/agent-platform/cloud-agents/integrations/gitlab/) and [Bitbucket](/agent-platform/cloud-agents/integrations/bitbucket/) setup guides. +* Agents need to access services behind a VPN or self-hosted SCMs like GitLab or Bitbucket. Warp-hosted agents can also access GitLab and Bitbucket over the public internet — see the [GitLab](/platform/integrations/gitlab/) and [Bitbucket](/platform/integrations/bitbucket/) setup guides. * Your environments (multi-service stacks, heavy resource requirements) don't fit in a single Docker container. -For setup, decision guides, and a quickstart, start with [Self-hosting](/agent-platform/cloud-agents/self-hosting/). +For setup, decision guides, and a quickstart, start with [Self-hosting](/platform/self-hosting/). diff --git a/src/content/docs/agent-platform/cloud-agents/environments.mdx b/src/content/docs/platform/environments.mdx similarity index 90% rename from src/content/docs/agent-platform/cloud-agents/environments.mdx rename to src/content/docs/platform/environments.mdx index aace31661..4a1a84c74 100644 --- a/src/content/docs/agent-platform/cloud-agents/environments.mdx +++ b/src/content/docs/platform/environments.mdx @@ -7,7 +7,7 @@ description: >- all triggers. Learn when to use environments and how to configure them. --- -Environments ensure your [cloud agents](/agent-platform/cloud-agents/overview/) run with the same toolchain and setup every time, regardless of where they're triggered from. +Environments ensure your [cloud agents](/platform/) run with the same toolchain and setup every time, regardless of where they're triggered from. An environment defines the execution context for automated agent runs: the **Docker image**, **repositories to clone**, **setup commands**, and **runtime configuration** Warp uses to prepare the workspace before the agent starts. @@ -29,11 +29,11 @@ Don't want to bring your own image? Warp provides [prebuilt dev images](https:// ## About environments -Environments define _how_ an agent runs, not _what_ it does. They're required for [Oz Platform](/agent-platform/cloud-agents/platform/) automation (cloud agents, integrations, API runs) but are not required for interactive local usage. +Environments define _how_ an agent runs, not _what_ it does. They're required for [Oz Platform](/platform/overview/) automation (cloud agents, integrations, API runs) but are not required for interactive local usage. An environment typically includes: -* **Docker image (required)** – The task/workspace image with the toolchain and dependencies your code needs. For self-hosted Kubernetes workers, a [`default_image`](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) on the worker lets you skip creating an environment entirely. +* **Docker image (required)** – The task/workspace image with the toolchain and dependencies your code needs. For self-hosted Kubernetes workers, a [`default_image`](/platform/self-hosting/managed-kubernetes/) on the worker lets you skip creating an environment entirely. * **Repository/workspace** – One or more repos the agent can clone and operate on. * **Setup commands** – Commands to prepare the workspace (e.g., dependency install, builds, bootstrapping). @@ -43,7 +43,7 @@ Use the Docker image for language runtimes, package managers, system libraries, Configuring runtime settings: * **Environment variables**: Configure these in your Dockerfile using Docker’s `ENV` directives or pass them when running the container. -* **Secrets**: For credentials and sensitive data, use [Agent Secrets](/agent-platform/cloud-agents/secrets/). These are configured separately from environments and injected securely at runtime. +* **Secrets**: For credentials and sensitive data, use [Agent Secrets](/platform/secrets/). These are configured separately from environments and injected securely at runtime. ::: What an environment is not: @@ -51,7 +51,7 @@ What an environment is not: * Host – Hosts determine where execution happens (Warp-hosted vs. self-hosted infrastructure). * [Agent Profile](/agent-platform/capabilities/agent-profiles-permissions/) – Profiles control agent behavior like permissions, model choice, and defaults, not the runtime environment. * [Rules](/agent-platform/capabilities/rules/) – Rules determine agent responses and decisions but don't define the container or toolchain. -* [MCP Servers](/agent-platform/cloud-agents/mcp/) – connect agents to external tools and data via MCP. +* [MCP Servers](/platform/mcp/) – connect agents to external tools and data via MCP. * Per-run context – Trigger-specific data like Slack threads, PR metadata, or CI logs attach to individual tasks, not the environment configuration. ## How environments fit into the Oz Platform @@ -78,10 +78,10 @@ While environments define _how_ an agent runs, hosts determine _where_ the envir Host options: * **Warp-hosted (default)** – Warp provides the infrastructure. Best for most users who want hands-off execution. -* **[Self-hosted](/agent-platform/cloud-agents/self-hosting/)** – You provide the infrastructure (runners in your cloud or network). Best for compliance requirements, on-premise execution, or custom hardware needs. +* **[Self-hosted](/platform/self-hosting/)** – You provide the infrastructure (runners in your cloud or network). Best for compliance requirements, on-premise execution, or custom hardware needs. * Local (coming soon) – Run environments on your local machine for sandbox development and testing. -The same environment can run on different hosts with identical behavior. For more details on hosting options, see [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) and [execution hosts](/agent-platform/cloud-agents/platform/#execution-hosts). +The same environment can run on different hosts with identical behavior. For more details on hosting options, see [Deployment Patterns](/platform/deployment-patterns/) and [execution hosts](/platform/overview/#execution-hosts). ### What happens at runtime @@ -135,7 +135,7 @@ You can create environments in three ways: from the Oz web app, using the guided Make sure you have: * One or more GitHub repositories that the agent should clone and work in. -* **GitHub authorization configured** so the agent can access your repos. For user-triggered runs, each user authorizes GitHub individually. For automated workflows using an agent API key, configure [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) in the Admin Panel. +* **GitHub authorization configured** so the agent can access your repos. For user-triggered runs, each user authorizes GitHub individually. For automated workflows using an agent API key, configure [team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization) in the Admin Panel. * A publicly-accessible Docker image that can build and run your code. Official images like [node](https://hub.docker.com/_/node), [python](https://hub.docker.com/_/python), or [rust](https://hub.docker.com/_/rust) work for many projects. You can also use one of [Warp's prebuilt dev images](https://github.com/warpdotdev/oz-dev-environments). :::caution @@ -149,7 +149,7 @@ Create one environment per codebase, then reuse it across triggers like Slack, L ### Create an environment from the Oz web app <figure> -![Creating a new environment in the Oz Web App.](../../../../assets/agent-platform/oz-web-app-new-environment.png) +![Creating a new environment in the Oz Web App.](../../../assets/agent-platform/oz-web-app-new-environment.png) <figcaption>The Create environment panel in the Oz web app.</figcaption> </figure> @@ -296,7 +296,7 @@ npm install ``` :::note -If your setup commands depend on secrets or credentials, configure them through Warp's [secrets mechanism](/agent-platform/cloud-agents/secrets/) rather than hardcoding tokens. +If your setup commands depend on secrets or credentials, configure them through Warp's [secrets mechanism](/platform/secrets/) rather than hardcoding tokens. ::: ### Common issues @@ -304,7 +304,7 @@ If your setup commands depend on secrets or credentials, configure them through * **Setup assumes previous state** – Steps that rely on leftover caches, existing directories, or already-cloned repos can make runs unreliable. Setup failures can surface as [`environment_setup_failed`](/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed/). * Solution: Write idempotent setup commands that work on a fresh container. * **Missing credentials or secrets** – Builds fail when private repos, package registries, or external services require authorization. - * Solution: Configure credentials with [Agent Secrets](/agent-platform/cloud-agents/secrets/). + * Solution: Configure credentials with [Agent Secrets](/platform/secrets/). * **Repo access and GitHub authorization issues** – Runs fail when GitHub doesn't have repo access or the triggering user lacks permissions. Missing external authorization can surface as [`external_authentication_required`](/reference/api-and-sdk/troubleshooting/errors/external-authentication-required/). * Solution: See [Integration setup](/reference/cli/integration-setup/#how-github-authorization-works) for GitHub authorization setup. * **Docker image incompatibility** – You see the error: "VM failed before the agent could run. This is likely an issue with your Docker image." diff --git a/src/content/docs/agent-platform/cloud-agents/faqs.mdx b/src/content/docs/platform/faqs.mdx similarity index 84% rename from src/content/docs/agent-platform/cloud-agents/faqs.mdx rename to src/content/docs/platform/faqs.mdx index b05aa1025..9369fbeb7 100644 --- a/src/content/docs/agent-platform/cloud-agents/faqs.mdx +++ b/src/content/docs/platform/faqs.mdx @@ -13,7 +13,7 @@ This page answers common questions about cloud agents, including where they run, ### Where do cloud agents run? What's the architecture? -Agents run either **locally** (inside your Warp session) or **in the cloud** as a **cloud agent run**, inside an **environment** (see [Environments](/agent-platform/cloud-agents/environments/)). +Agents run either **locally** (inside your Warp session) or **in the cloud** as a **cloud agent run**, inside an **environment** (see [Environments](/platform/environments/)). The cloud agents platform is built around modular, observable execution: @@ -57,7 +57,7 @@ Yes. Cloud agent runs execute in a full Linux environment and behave like a loca The cloud agents platform supports self-hosting the **agent sandbox** (the execution environment) on your own infrastructure. The **control plane**—which handles orchestration, tracking, and auditability—remains Warp-managed and is not self-hosted. -Self-hosted execution is available on **Enterprise** plans. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) and [Deployment patterns](/agent-platform/cloud-agents/deployment-patterns/) for details. +Self-hosted execution is available on **Enterprise** plans. See [Self-hosting](/platform/self-hosting/) and [Deployment patterns](/platform/deployment-patterns/) for details. :::note [Bring Your Own API Key (BYOK)](/agent-platform/inference/bring-your-own-api-key/) does not apply to cloud agents. BYOK keys are stored locally on your device and cannot be passed to cloud-hosted or self-hosted agent runs. All cloud agent runs consume [Warp credits](/support-and-community/plans-and-billing/credits/). @@ -108,7 +108,7 @@ Cloud agents are included in the Build plan. Usage is metered via credits, with Secrets are managed via the cloud agents CLI. Secrets are encrypted at rest, scoped to your Warp account, and injected into the agent environment at runtime. They are never hard-coded into agent instructions or logs. -To learn more about how secrets work in practice, see [Cloud Agent Secrets](/agent-platform/cloud-agents/secrets/). +To learn more about how secrets work in practice, see [Cloud Agent Secrets](/platform/secrets/). ## Workflows @@ -203,11 +203,11 @@ With self-hosting, repositories are cloned and stored only on your infrastructur * **Execution plane (your infrastructure)** — Repository clones, build artifacts, runtime secrets, and container filesystem state stay on the machines you control. * **Control plane (Warp-hosted)** — Session transcripts (which include code context from agent interactions), orchestration metadata, and LLM inference route through Warp's backend under [Zero Data Retention (ZDR)](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr) agreements. Warp does not persistently store your source code or use it for model training. -See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for deployment options and [Security Overview](/enterprise/security-and-compliance/security-overview/) for full details. +See [Self-hosting](/platform/self-hosting/) for deployment options and [Security Overview](/enterprise/security-and-compliance/security-overview/) for full details. ### Can I use `oz agent run` in CI or existing runners? -Yes. The [unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/) is designed exactly for this. Run `oz agent run` in any environment where you can execute a CLI command — GitHub Actions, Jenkins, Buildkite, Kubernetes pods, or custom orchestrators. This is how the [`warpdotdev/oz-agent-action`](https://github.com/warpdotdev/oz-agent-action) GitHub Action works. The agent runs locally on the runner and its session is tracked on Warp's backend for observability. +Yes. The [unmanaged architecture](/platform/self-hosting/unmanaged/) is designed exactly for this. Run `oz agent run` in any environment where you can execute a CLI command — GitHub Actions, Jenkins, Buildkite, Kubernetes pods, or custom orchestrators. This is how the [`warpdotdev/oz-agent-action`](https://github.com/warpdotdev/oz-agent-action) GitHub Action works. The agent runs locally on the runner and its session is tracked on Warp's backend for observability. ### Can self-hosted agents access services behind a VPN? @@ -215,7 +215,7 @@ Yes. Since self-hosted agents run on your infrastructure, they inherit your netw ### Does self-hosting work with GitLab or other non-GitHub SCMs? -Self-hosted agents can use any SCM accessible from your infrastructure. With the [unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/), agents run directly on your host and use whatever Git configuration and SCM access is already available. With the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture), automatic environment setup currently focuses on GitHub, but you can configure access to other SCMs via volume mounts, environment variables, setup commands, or Kubernetes Secrets (when using the [Kubernetes backend](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/)). See the [GitLab](/agent-platform/cloud-agents/integrations/gitlab/) and [Bitbucket](/agent-platform/cloud-agents/integrations/bitbucket/) setup guides for step-by-step instructions. +Self-hosted agents can use any SCM accessible from your infrastructure. With the [unmanaged architecture](/platform/self-hosting/unmanaged/), agents run directly on your host and use whatever Git configuration and SCM access is already available. With the [managed architecture](/platform/self-hosting/#managed-architecture), automatic environment setup currently focuses on GitHub, but you can configure access to other SCMs via volume mounts, environment variables, setup commands, or Kubernetes Secrets (when using the [Kubernetes backend](/platform/self-hosting/managed-kubernetes/)). See the [GitLab](/platform/integrations/gitlab/) and [Bitbucket](/platform/integrations/bitbucket/) setup guides for step-by-step instructions. ### Do LLM requests still go through Warp with self-hosting? @@ -223,10 +223,10 @@ Yes. LLM inference routes through Warp's backend, which has [Zero Data Retention ### What about large monorepos with long environment setup times? -The [unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/) is well-suited for large monorepos because agents run directly in your pre-provisioned environment — there is no Docker image build or repo cloning step. For the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture), the Docker backend supports volume mounts (`-v` flag) to mount a pre-existing repo checkout from the host into task containers. With the Kubernetes backend, use `pod_template` to configure persistent volume claims or pre-populated storage for the same purpose. +The [unmanaged architecture](/platform/self-hosting/unmanaged/) is well-suited for large monorepos because agents run directly in your pre-provisioned environment — there is no Docker image build or repo cloning step. For the [managed architecture](/platform/self-hosting/#managed-architecture), the Docker backend supports volume mounts (`-v` flag) to mount a pre-existing repo checkout from the host into task containers. With the Kubernetes backend, use `pod_template` to configure persistent volume claims or pre-populated storage for the same purpose. :::note -The managed architecture supports three execution backends: **Docker** (default), **Kubernetes**, and **Direct** (no container runtime). The Kubernetes backend runs each task as a Kubernetes Job and includes a Helm chart for deployment. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/#choosing-a-managed-backend) for details on choosing a backend. +The managed architecture supports three execution backends: **Docker** (default), **Kubernetes**, and **Direct** (no container runtime). The Kubernetes backend runs each task as a Kubernetes Job and includes a Helm chart for deployment. See [Self-hosting](/platform/self-hosting/#choosing-a-managed-backend) for details on choosing a backend. ::: ### Do Kubernetes pods provide enough sandboxing for self-hosted agents? @@ -239,5 +239,5 @@ This depends on your cluster configuration and risk profile. Evaluate your pod s Cloud agent conversations do not currently support image attachments. Image attachment (via the toolbar button, clipboard paste, or drag-and-drop) is only available in [local agent conversations](/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes/). -If you need to provide visual context to a cloud agent, you can describe the image contents in your prompt or reference image file paths within the agent's [environment](/agent-platform/cloud-agents/environments/). +If you need to provide visual context to a cloud agent, you can describe the image contents in your prompt or reference image file paths within the agent's [environment](/platform/environments/). diff --git a/src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx b/src/content/docs/platform/handoff/cloud-to-cloud.mdx similarity index 80% rename from src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx rename to src/content/docs/platform/handoff/cloud-to-cloud.mdx index ed6b82368..cad8ff257 100644 --- a/src/content/docs/agent-platform/cloud-agents/handoff/cloud-to-cloud.mdx +++ b/src/content/docs/platform/handoff/cloud-to-cloud.mdx @@ -17,14 +17,14 @@ Watch this walkthrough to see how cloud-to-cloud handoff continues a cloud agent Use this handoff direction when: * You want to send a follow-up to a cloud agent after its session has ended. -* You want to continue a background cloud agent run, such as a scheduled or integration-triggered run, while preserving it as a single unit of work in the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs). +* You want to continue a background cloud agent run, such as a scheduled or integration-triggered run, while preserving it as a single unit of work in the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/platform/oz-web-app/#runs). ## What carries over When you send a follow-up to a run whose session has ended, the run continues with: * **The same conversation** - The follow-up is appended to the same conversation. From your perspective, the run is one continuous conversation across sessions. -* **The prior workspace state** - The prior session's repository changes (tracked and untracked) are restored before the agent answers your follow-up. For Git-managed sessions, the new session continues on the same Git branch. You can [customize which repositories and files get snapshotted](/agent-platform/cloud-agents/handoff/snapshots/) when running outside the bundled cloud agent image. +* **The prior workspace state** - The prior session's repository changes (tracked and untracked) are restored before the agent answers your follow-up. For Git-managed sessions, the new session continues on the same Git branch. You can [customize which repositories and files get snapshotted](/platform/handoff/snapshots/) when running outside the bundled cloud agent image. * **Stable run identity** - The run's ID, task, creator, environment, schedule trigger, and integration source are preserved. Compute usage is recorded per session but rolls up to the same run. If any changes fail to apply, the agent reports which changes failed and continues with the changes that applied cleanly. @@ -58,9 +58,9 @@ Cloud-to-cloud handoff also works for supported third-party agent runtimes, but ## Inspecting a run that's been handed off -The [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs) show one row per run, even when the run spans multiple sessions. +The [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/platform/oz-web-app/#runs) show one row per run, even when the run spans multiple sessions. -1. Open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs). +1. Open the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/platform/oz-web-app/#runs). 2. Select the handed-off run. 3. Review the transcript. Each session appears in order, so you can see where one session ended and the next began. @@ -76,6 +76,6 @@ Very old runs predate the agent conversation model and can't be continued via ha ## Related pages -* [Handoff overview](/agent-platform/cloud-agents/handoff/) - What handoff is, the directions it supports, and what carries over. -* [Handoff from local to cloud](/agent-platform/cloud-agents/handoff/local-to-cloud/) - Promote a local conversation to a cloud run. -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Find runs to send follow-ups to. +* [Handoff overview](/platform/handoff/) - What handoff is, the directions it supports, and what carries over. +* [Handoff from local to cloud](/platform/handoff/local-to-cloud/) - Promote a local conversation to a cloud run. +* [Managing cloud agents](/platform/managing-cloud-agents/) - Find runs to send follow-ups to. diff --git a/src/content/docs/agent-platform/cloud-agents/handoff/index.mdx b/src/content/docs/platform/handoff/index.mdx similarity index 74% rename from src/content/docs/agent-platform/cloud-agents/handoff/index.mdx rename to src/content/docs/platform/handoff/index.mdx index 5345cc7ad..af1e45fd9 100644 --- a/src/content/docs/agent-platform/cloud-agents/handoff/index.mdx +++ b/src/content/docs/platform/handoff/index.mdx @@ -10,7 +10,7 @@ sidebar: Handoff 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. <figure style={{ maxWidth: "350px" }}> -![A Handoff control in a local Warp Agent conversation.](../../../../../assets/agent-platform/local-to-cloud-handoff-chip.png) +![A Handoff control in a local Warp Agent conversation.](../../../../assets/agent-platform/local-to-cloud-handoff-chip.png) <figcaption>The Handoff control in a local conversation.</figcaption> </figure> @@ -18,15 +18,15 @@ Handoff moves agent work between local Warp sessions and cloud agent runs withou Handoff supports three directions: -* **Local to cloud** - Promote a local Warp Agent conversation to a cloud agent run when you need more compute, longer-running work, or parallel variants of the same task. The cloud agent starts from your conversation history and a snapshot of your uncommitted workspace changes. See [Handoff from local to cloud](/agent-platform/cloud-agents/handoff/local-to-cloud/). -* **Cloud to cloud** - Send a follow-up to a cloud run after its session has ended. The run continues in the same conversation, with the prior session's workspace state restored. See [Handoff from cloud to cloud](/agent-platform/cloud-agents/handoff/cloud-to-cloud/). -* **Cloud to local** - Fork a cloud conversation into a local Warp session with **Continue locally** or `/continue-locally`. See [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/#5-fork-the-session-to-your-local-warp). +* **Local to cloud** - Promote a local Warp Agent conversation to a cloud agent run when you need more compute, longer-running work, or parallel variants of the same task. The cloud agent starts from your conversation history and a snapshot of your uncommitted workspace changes. See [Handoff from local to cloud](/platform/handoff/local-to-cloud/). +* **Cloud to cloud** - Send a follow-up to a cloud run after its session has ended. The run continues in the same conversation, with the prior session's workspace state restored. See [Handoff from cloud to cloud](/platform/handoff/cloud-to-cloud/). +* **Cloud to local** - Fork a cloud conversation into a local Warp session with **Continue locally** or `/continue-locally`. See [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/#5-fork-the-session-to-your-local-warp). ### Third-party agent runtime coverage Handoff coverage depends on which agent is running the conversation: -* **Cloud to cloud** works for the Warp Agent and the [third-party cloud harnesses currently supported in Oz](/agent-platform/cloud-agents/harnesses/): Claude Code and Codex. For Claude Code and Codex runs, click **Continue**, then enter your follow-up prompt. Warp Agent runs use the streamlined follow-up input. +* **Cloud to cloud** works for the Warp Agent and the [third-party cloud harnesses currently supported in Oz](/platform/harnesses/): Claude Code and Codex. For Claude Code and Codex runs, click **Continue**, then enter your follow-up prompt. Warp Agent runs use the streamlined follow-up input. * **Local to cloud** works for the Warp Agent. It isn't available for third-party CLI agent sessions. ## What carries over @@ -49,8 +49,8 @@ Each direction has a clear motivating workflow. ## Related pages -* [Cloud agents overview](/agent-platform/cloud-agents/overview/) - What cloud agents are, when to use them, and how they fit into the Oz Platform. -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Inspect handoff runs from the Agent Management Panel in the Warp app or the Runs page in the Oz web app alongside local conversations. -* [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) - Open and continue a cloud run locally with **Continue locally** or `/continue-locally`. +* [Cloud agents overview](/platform/) - What cloud agents are, when to use them, and how they fit into the Oz Platform. +* [Managing cloud agents](/platform/managing-cloud-agents/) - Inspect handoff runs from the Agent Management Panel in the Warp app or the Runs page in the Oz web app alongside local conversations. +* [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) - Open and continue a cloud run locally with **Continue locally** or `/continue-locally`. * [Cloud-synced conversations](/agent-platform/local-agents/cloud-conversations/) - How conversations sync between local and cloud so handoff can find them. -* [Environments](/agent-platform/cloud-agents/environments/) - The runtime context a cloud agent runs in after a handoff. +* [Environments](/platform/environments/) - The runtime context a cloud agent runs in after a handoff. diff --git a/src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx b/src/content/docs/platform/handoff/local-to-cloud.mdx similarity index 82% rename from src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx rename to src/content/docs/platform/handoff/local-to-cloud.mdx index 5ef5ee511..bfcfd4302 100644 --- a/src/content/docs/agent-platform/cloud-agents/handoff/local-to-cloud.mdx +++ b/src/content/docs/platform/handoff/local-to-cloud.mdx @@ -34,9 +34,9 @@ If any changes fail to apply in the cloud run, the cloud agent reports which cha ## Prerequisites * **An active local conversation** - Have a [Warp Agent](/agent-platform/local-agents/overview/) conversation open in Warp with the work you want to hand off. -* **A configured environment** - The cloud agent needs an [environment](/agent-platform/cloud-agents/environments/) that includes the same repositories you're working in locally. The environment's repos must match your local checkout so the workspace snapshot applies cleanly. +* **A configured environment** - The cloud agent needs an [environment](/platform/environments/) that includes the same repositories you're working in locally. The environment's repos must match your local checkout so the workspace snapshot applies cleanly. * **Cloud conversation storage enabled** - In the Warp app, go to **Settings** > **Privacy** and turn on **Store AI conversations in the cloud** so the conversation can be forked. See [Cloud-synced conversations](/agent-platform/local-agents/cloud-conversations/). -* **Sufficient credits** - Cloud agent runs consume credits. See [Credits](/support-and-community/plans-and-billing/credits/) for how credit usage works, and [Access, billing, and identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for team-specific credit requirements. +* **Sufficient credits** - Cloud agent runs consume credits. See [Credits](/support-and-community/plans-and-billing/credits/) for how credit usage works, and [Access, billing, and identity](/platform/team-access-billing-and-identity/) for team-specific credit requirements. ## Handing off a conversation to the cloud @@ -47,24 +47,24 @@ If any changes fail to apply in the cloud run, the cloud agent reports which cha The `&` entry point and `/handoff` slash command both open the same handoff flow. <figure style={{ maxWidth: "375px" }}> -![The ampersand entry point for handoff in a local Warp Agent conversation.](../../../../../assets/agent-platform/local-to-cloud-handoff-input-entrypoint.png) +![The ampersand entry point for handoff in a local Warp Agent conversation.](../../../../assets/agent-platform/local-to-cloud-handoff-input-entrypoint.png) <figcaption>The ampersand handoff entry point.</figcaption> </figure> <figure style={{ maxWidth: "375px" }}> -![The slash command menu showing the handoff command in Warp.](../../../../../assets/agent-platform/local-to-cloud-handoff-slash-command.png) +![The slash command menu showing the handoff command in Warp.](../../../../assets/agent-platform/local-to-cloud-handoff-slash-command.png) <figcaption>The `/handoff` slash command.</figcaption> </figure> After the flow opens, choose the cloud environment and add the follow-up prompt the cloud agent should act on. <figure style={{ maxWidth: "375px" }}> -![The handoff flow showing an environment selector for the cloud run.](../../../../../assets/agent-platform/local-to-cloud-handoff-environment-selector.png) +![The handoff flow showing an environment selector for the cloud run.](../../../../assets/agent-platform/local-to-cloud-handoff-environment-selector.png) <figcaption>The environment selector in the handoff flow.</figcaption> </figure> <figure style={{ maxWidth: "563px" }}> -![The handoff flow with a follow-up prompt entered before submitting.](../../../../../assets/agent-platform/local-to-cloud-handoff-follow-up-prompt.png) +![The handoff flow with a follow-up prompt entered before submitting.](../../../../assets/agent-platform/local-to-cloud-handoff-follow-up-prompt.png) <figcaption>A follow-up prompt before handoff.</figcaption> </figure> @@ -89,7 +89,7 @@ The source conversation may not have finished syncing to the cloud when you trig ## Related pages -* [Handoff overview](/agent-platform/cloud-agents/handoff/) - What handoff is, the directions it supports, and what carries over. -* [Handoff from cloud to cloud](/agent-platform/cloud-agents/handoff/cloud-to-cloud/) - Continue a finished cloud run with workspace state restored. -* [Environments](/agent-platform/cloud-agents/environments/) - Configure the repos, image, and setup commands the cloud agent starts in. -* [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) - Run your first cloud agent from scratch. +* [Handoff overview](/platform/handoff/) - What handoff is, the directions it supports, and what carries over. +* [Handoff from cloud to cloud](/platform/handoff/cloud-to-cloud/) - Continue a finished cloud run with workspace state restored. +* [Environments](/platform/environments/) - Configure the repos, image, and setup commands the cloud agent starts in. +* [Cloud agents quickstart](/platform/quickstart/) - Run your first cloud agent from scratch. diff --git a/src/content/docs/agent-platform/cloud-agents/handoff/snapshots.mdx b/src/content/docs/platform/handoff/snapshots.mdx similarity index 89% rename from src/content/docs/agent-platform/cloud-agents/handoff/snapshots.mdx rename to src/content/docs/platform/handoff/snapshots.mdx index 8fec8ef05..4f3542c04 100644 --- a/src/content/docs/agent-platform/cloud-agents/handoff/snapshots.mdx +++ b/src/content/docs/platform/handoff/snapshots.mdx @@ -8,9 +8,9 @@ sidebar: label: "Snapshots" --- -Workspace snapshots are how [handoff](/agent-platform/cloud-agents/handoff/) carries repository changes and other workspace state across cloud agent runs. At the end of every cloud agent run, Warp asks a small declarations script which repositories and files to snapshot, then uploads the resulting git diffs and file contents so the next cloud agent run can apply them. +Workspace snapshots are how [handoff](/platform/handoff/) carries repository changes and other workspace state across cloud agent runs. At the end of every cloud agent run, Warp asks a small declarations script which repositories and files to snapshot, then uploads the resulting git diffs and file contents so the next cloud agent run can apply them. -Warp's bundled cloud agent image ships with a declarations script that snapshots every Git repository under the agent's workspace, so most cloud agent runs need no configuration. This page is for the cases where you need to customize what gets snapshotted — for example, when running cloud agents in a custom Docker image, on a self-hosted [Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/), or as an [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) `oz agent run` in CI. +Warp's bundled cloud agent image ships with a declarations script that snapshots every Git repository under the agent's workspace, so most cloud agent runs need no configuration. This page is for the cases where you need to customize what gets snapshotted — for example, when running cloud agents in a custom Docker image, on a self-hosted [Direct backend](/platform/self-hosting/managed-direct/), or as an [unmanaged](/platform/self-hosting/unmanaged/) `oz agent run` in CI. ## When to customize snapshots @@ -112,7 +112,7 @@ Then point Warp at it by exporting `OZ_SNAPSHOT_DECLARATIONS_SCRIPT` in the envi export OZ_SNAPSHOT_DECLARATIONS_SCRIPT=/path/to/snapshot-declarations.sh ``` -For a managed [Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/) worker, set it via the worker's `environment` config so it's present when the agent process starts. +For a managed [Direct backend](/platform/self-hosting/managed-direct/) worker, set it via the worker's `environment` config so it's present when the agent process starts. ### The full bundled script @@ -226,8 +226,8 @@ Snapshotting is also skipped automatically when cloud conversations are disabled ## Related pages -* [Handoff from local to cloud](/agent-platform/cloud-agents/handoff/local-to-cloud/) - Promote a local conversation to a cloud run; the workspace snapshot is what carries your uncommitted changes across. -* [Handoff from cloud to cloud](/agent-platform/cloud-agents/handoff/cloud-to-cloud/) - Continue a finished cloud run; the prior session's workspace snapshot is what gets restored. -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) - Architecture decision guide for self-hosted workers, where customizing snapshots is most often needed. -* [Unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/) - Run `oz agent run` in CI, Kubernetes, or your dev environment outside the bundled image. +* [Handoff from local to cloud](/platform/handoff/local-to-cloud/) - Promote a local conversation to a cloud run; the workspace snapshot is what carries your uncommitted changes across. +* [Handoff from cloud to cloud](/platform/handoff/cloud-to-cloud/) - Continue a finished cloud run; the prior session's workspace snapshot is what gets restored. +* [Self-hosting overview](/platform/self-hosting/) - Architecture decision guide for self-hosted workers, where customizing snapshots is most often needed. +* [Unmanaged architecture](/platform/self-hosting/unmanaged/) - Run `oz agent run` in CI, Kubernetes, or your dev environment outside the bundled image. * [Oz CLI](/reference/cli/) - Full reference for `oz agent run` and `oz agent run-cloud`. diff --git a/src/content/docs/agent-platform/cloud-agents/harnesses/authentication.mdx b/src/content/docs/platform/harnesses/authentication.mdx similarity index 93% rename from src/content/docs/agent-platform/cloud-agents/harnesses/authentication.mdx rename to src/content/docs/platform/harnesses/authentication.mdx index f1a7c167d..f024fe89c 100644 --- a/src/content/docs/agent-platform/cloud-agents/harnesses/authentication.mdx +++ b/src/content/docs/platform/harnesses/authentication.mdx @@ -39,7 +39,7 @@ Start a new cloud agent run and choose **Claude Code** from the **Agent harness* Start a [new run](https://oz.warp.dev/runs/new), choose **Claude Code** as the harness, and add a new key in the Claude Code auth secret dialog. <figure style={{ maxWidth: "563px" }}> -![The Oz web app dialog for adding a new Claude Code auth secret.](../../../../../assets/agent-platform/claude-code-auth-secret-setup.png) +![The Oz web app dialog for adding a new Claude Code auth secret.](../../../../assets/agent-platform/claude-code-auth-secret-setup.png) <figcaption>The Claude Code auth secret dialog.</figcaption> </figure> @@ -91,7 +91,7 @@ Add `--description "..."` to record rotation notes or owner info. Replace `--tea ## Managing harness auth secrets -Auth secrets follow the same management commands as any other Warp-managed secret. See [Cloud agent secrets](/agent-platform/cloud-agents/secrets/) for the full reference. Common tasks: +Auth secrets follow the same management commands as any other Warp-managed secret. See [Cloud agent secrets](/platform/secrets/) for the full reference. Common tasks: ```bash # List secrets you can see @@ -124,7 +124,7 @@ Your team admin has disabled the harness for your workspace. Contact your admin ## Related pages -* [Harnesses in Oz](/agent-platform/cloud-agents/harnesses/) — overview of third-party harnesses in Oz. +* [Harnesses in Oz](/platform/harnesses/) — overview of third-party harnesses in Oz. * [Claude Code in Warp](/agent-platform/cli-agents/claude-code/) — run Claude Code locally in the Warp terminal. * [Codex CLI in Warp](/agent-platform/cli-agents/codex/) — run Codex locally in the Warp terminal. -* [Cloud agent secrets](/agent-platform/cloud-agents/secrets/) — the full Warp-managed secrets reference. +* [Cloud agent secrets](/platform/secrets/) — the full Warp-managed secrets reference. diff --git a/src/content/docs/agent-platform/cloud-agents/harnesses/claude-code.mdx b/src/content/docs/platform/harnesses/claude-code.mdx similarity index 81% rename from src/content/docs/agent-platform/cloud-agents/harnesses/claude-code.mdx rename to src/content/docs/platform/harnesses/claude-code.mdx index 2640003a1..11b58e0e6 100644 --- a/src/content/docs/agent-platform/cloud-agents/harnesses/claude-code.mdx +++ b/src/content/docs/platform/harnesses/claude-code.mdx @@ -30,7 +30,7 @@ For the full list — including 1M-context variants for very large codebases and ## Credentials and billing -Claude Code calls Anthropic directly using credentials your team provides. Oz supports three Anthropic credential types, stored as [Warp-managed secrets](/agent-platform/cloud-agents/secrets/): +Claude Code calls Anthropic directly using credentials your team provides. Oz supports three Anthropic credential types, stored as [Warp-managed secrets](/platform/secrets/): * **Anthropic API key** - For direct Anthropic API access. * **Anthropic Bedrock API key** - For Bedrock-routed inference using an API key. @@ -38,7 +38,7 @@ Claude Code calls Anthropic directly using credentials your team provides. Oz su Anthropic bills your account directly for inference. Warp still meters [compute credits](/support-and-community/plans-and-billing/credits/#compute-credits) for the run's sandbox and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the orchestration layer. -For setup steps, see [Connecting Claude Code credentials](/agent-platform/cloud-agents/harnesses/authentication/#connecting-claude-code-credentials). +For setup steps, see [Connecting Claude Code credentials](/platform/harnesses/authentication/#connecting-claude-code-credentials). ## Starting a Claude Code run @@ -48,8 +48,8 @@ For setup steps, see [Connecting Claude Code credentials](/agent-platform/cloud- ## Related pages -* [Harnesses in Oz](/agent-platform/cloud-agents/harnesses/) — choose between Warp Agent, Claude Code, and Codex. -* [Authentication](/agent-platform/cloud-agents/harnesses/authentication/) — store Anthropic credentials as Warp-managed secrets. -* [Warp Agent with Oz](/agent-platform/cloud-agents/harnesses/warp-agent/) — Oz's default harness, the only one that can orchestrate Claude Code subagents. -* [Codex with Oz](/agent-platform/cloud-agents/harnesses/codex/) — Codex as a cloud harness. +* [Harnesses in Oz](/platform/harnesses/) — choose between Warp Agent, Claude Code, and Codex. +* [Authentication](/platform/harnesses/authentication/) — store Anthropic credentials as Warp-managed secrets. +* [Warp Agent with Oz](/platform/harnesses/warp-agent/) — Oz's default harness, the only one that can orchestrate Claude Code subagents. +* [Codex with Oz](/platform/harnesses/codex/) — Codex as a cloud harness. * [Claude Code in Warp](/agent-platform/cli-agents/claude-code/) — Claude Code in your local Warp terminal. diff --git a/src/content/docs/agent-platform/cloud-agents/harnesses/codex.mdx b/src/content/docs/platform/harnesses/codex.mdx similarity index 81% rename from src/content/docs/agent-platform/cloud-agents/harnesses/codex.mdx rename to src/content/docs/platform/harnesses/codex.mdx index bdff1417b..00baa881c 100644 --- a/src/content/docs/agent-platform/cloud-agents/harnesses/codex.mdx +++ b/src/content/docs/platform/harnesses/codex.mdx @@ -31,13 +31,13 @@ For the full list, including Codex-tuned and general models, open the model pick ## Credentials and billing -Codex calls OpenAI directly using credentials your team provides. Oz supports one credential type today, stored as a [Warp-managed secret](/agent-platform/cloud-agents/secrets/): +Codex calls OpenAI directly using credentials your team provides. Oz supports one credential type today, stored as a [Warp-managed secret](/platform/secrets/): * **OpenAI API key** - The Codex harness authenticates to OpenAI using this key for every run. OpenAI bills your account directly for inference. Warp still meters [compute credits](/support-and-community/plans-and-billing/credits/#compute-credits) for the run's sandbox and [platform credits](/support-and-community/plans-and-billing/platform-credits/) for the orchestration layer. -For setup steps, see [Connecting Codex credentials](/agent-platform/cloud-agents/harnesses/authentication/#connecting-codex-credentials). +For setup steps, see [Connecting Codex credentials](/platform/harnesses/authentication/#connecting-codex-credentials). ## Starting a Codex run @@ -47,8 +47,8 @@ For setup steps, see [Connecting Codex credentials](/agent-platform/cloud-agents ## Related pages -* [Harnesses in Oz](/agent-platform/cloud-agents/harnesses/) — choose between Warp Agent, Claude Code, and Codex. -* [Authentication](/agent-platform/cloud-agents/harnesses/authentication/) — store OpenAI credentials as Warp-managed secrets. -* [Warp Agent with Oz](/agent-platform/cloud-agents/harnesses/warp-agent/) — Oz's default harness, the only one that can orchestrate Codex subagents. -* [Claude Code with Oz](/agent-platform/cloud-agents/harnesses/claude-code/) — Claude Code as a cloud harness. +* [Harnesses in Oz](/platform/harnesses/) — choose between Warp Agent, Claude Code, and Codex. +* [Authentication](/platform/harnesses/authentication/) — store OpenAI credentials as Warp-managed secrets. +* [Warp Agent with Oz](/platform/harnesses/warp-agent/) — Oz's default harness, the only one that can orchestrate Codex subagents. +* [Claude Code with Oz](/platform/harnesses/claude-code/) — Claude Code as a cloud harness. * [Codex CLI in Warp](/agent-platform/cli-agents/codex/) — Codex in your local Warp terminal. diff --git a/src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx b/src/content/docs/platform/harnesses/index.mdx similarity index 67% rename from src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx rename to src/content/docs/platform/harnesses/index.mdx index deebccd16..1e0939b19 100644 --- a/src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx +++ b/src/content/docs/platform/harnesses/index.mdx @@ -9,7 +9,7 @@ sidebar: --- import VideoEmbed from '@components/VideoEmbed.astro'; -Oz can run third-party agent harnesses as cloud agents alongside Warp Agent, including [Claude Code](/agent-platform/cloud-agents/harnesses/claude-code/) and [Codex](/agent-platform/cloud-agents/harnesses/codex/). You choose the harness (agent runtime) that fits the task; the platform around the run stays the same. +Oz can run third-party agent harnesses as cloud agents alongside Warp Agent, including [Claude Code](/platform/harnesses/claude-code/) and [Codex](/platform/harnesses/codex/). You choose the harness (agent runtime) that fits the task; the platform around the run stays the same. Watch this walkthrough to see how to run Warp Agent, Claude Code, or Codex as a cloud agent. @@ -19,10 +19,10 @@ Watch this walkthrough to see how to run Warp Agent, Claude Code, or Codex as a Third-party harnesses inherit the same Oz platform features as Warp Agent: -* **Triggers** — Slack, Linear, schedules, CI, and API [triggers](/agent-platform/cloud-agents/triggers/) launch any harness. -* **Environments and secrets** — Reuse the same [environments](/agent-platform/cloud-agents/environments/) and [agent secrets](/agent-platform/cloud-agents/secrets/). +* **Triggers** — Slack, Linear, schedules, CI, and API [triggers](/platform/triggers/) launch any harness. +* **Environments and secrets** — Reuse the same [environments](/platform/environments/) and [agent secrets](/platform/secrets/). * **Skills and Rules** — Saved [Skills](/agent-platform/capabilities/skills/) and [Rules](/agent-platform/capabilities/rules/) apply across harnesses. -* **Observability** — Every run produces a transcript and shareable session in the [Oz dashboard](/agent-platform/cloud-agents/managing-cloud-agents/). +* **Observability** — Every run produces a transcript and shareable session in the [Oz dashboard](/platform/managing-cloud-agents/). ## Billing @@ -35,7 +35,7 @@ Claude Code and Codex each call their provider directly using credentials you su In Cloud Mode, choose a harness from the **Agent harness** dropdown above the input. <figure style={{ maxWidth: "375px" }}> -![The Warp app Agent harness dropdown showing third-party harness options for a cloud agent.](../../../../../assets/agent-platform/cloud-agent-harness-selector-warp-app.png) +![The Warp app Agent harness dropdown showing third-party harness options for a cloud agent.](../../../../assets/agent-platform/cloud-agent-harness-selector-warp-app.png) <figcaption>The Agent harness selector.</figcaption> </figure> @@ -53,8 +53,8 @@ Set the `harness` field on the agent config. See the [API reference](/reference/ ## Related pages -* [Warp Agent with Oz](/agent-platform/cloud-agents/harnesses/warp-agent/) — Oz's default first-party harness. -* [Claude Code with Oz](/agent-platform/cloud-agents/harnesses/claude-code/) — Claude Code as a cloud harness. -* [Codex with Oz](/agent-platform/cloud-agents/harnesses/codex/) — Codex as a cloud harness. -* [Authentication](/agent-platform/cloud-agents/harnesses/authentication/) — connect credentials and launch Claude Code or Codex. +* [Warp Agent with Oz](/platform/harnesses/warp-agent/) — Oz's default first-party harness. +* [Claude Code with Oz](/platform/harnesses/claude-code/) — Claude Code as a cloud harness. +* [Codex with Oz](/platform/harnesses/codex/) — Codex as a cloud harness. +* [Authentication](/platform/harnesses/authentication/) — connect credentials and launch Claude Code or Codex. * [Third-party CLI agents in the Warp terminal](/agent-platform/cli-agents/overview/) — run Claude Code, Codex, and other CLI agents locally. diff --git a/src/content/docs/agent-platform/cloud-agents/harnesses/warp-agent.mdx b/src/content/docs/platform/harnesses/warp-agent.mdx similarity index 79% rename from src/content/docs/agent-platform/cloud-agents/harnesses/warp-agent.mdx rename to src/content/docs/platform/harnesses/warp-agent.mdx index 56ab1c5b8..c3092f4a2 100644 --- a/src/content/docs/agent-platform/cloud-agents/harnesses/warp-agent.mdx +++ b/src/content/docs/platform/harnesses/warp-agent.mdx @@ -16,13 +16,13 @@ Warp Agent is the same agent runtime that powers Agent Mode in the Warp terminal * **Multi-model auto-routing** - Routes between Anthropic, OpenAI, Google, and Fireworks-hosted models. Choose a specific model, or let Warp pick via `auto`, `auto-efficient`, `auto-genius`, or `auto-open`. See [Model choice](/agent-platform/inference/model-choice/) for the full catalog. * **Full terminal and tool access** - Runs commands, edits files, reads logs, executes tests, navigates repos, and calls MCP servers, giving cloud runs the same toolbelt Warp Agent uses locally. * **Platform-native context** - Reads [Codebase Context](/agent-platform/capabilities/codebase-context/), applies [Rules](/agent-platform/capabilities/rules/), reuses saved [Skills](/agent-platform/capabilities/skills/), and respects Memory and Warp Drive context with no extra setup. -* **Multi-repo execution** - Clones every repo configured on the [environment](/agent-platform/cloud-agents/environments/) and works across them in a single run. -* **Cross-harness orchestration parent** - A Warp Agent parent run can spawn Claude Code or Codex [subagents](/agent-platform/cloud-agents/overview/) and coordinate their outputs. Other harnesses cannot act as parents in a multi-harness orchestration. +* **Multi-repo execution** - Clones every repo configured on the [environment](/platform/environments/) and works across them in a single run. +* **Cross-harness orchestration parent** - A Warp Agent parent run can spawn Claude Code or Codex [subagents](/platform/) and coordinate their outputs. Other harnesses cannot act as parents in a multi-harness orchestration. * **No extra credentials** - Warp Agent uses your existing Warp account and credits. There's no separate API key to configure. ## How it works -Warp Agent is the same agent runtime as Agent Mode in the Warp terminal: it plans, calls tools, edits code, runs tests, and reports progress. The cloud platform adds the [environment](/agent-platform/cloud-agents/environments/), triggers, observability, and team governance around the run, and the transcript is inspectable in real time and replayable afterward from the [Oz dashboard](/agent-platform/cloud-agents/managing-cloud-agents/). +Warp Agent is the same agent runtime as Agent Mode in the Warp terminal: it plans, calls tools, edits code, runs tests, and reports progress. The cloud platform adds the [environment](/platform/environments/), triggers, observability, and team governance around the run, and the transcript is inspectable in real time and replayable afterward from the [Oz dashboard](/platform/managing-cloud-agents/). Team admins can disable any harness for their workspace. Users on that team can only start runs with the harnesses that remain enabled. @@ -57,13 +57,13 @@ Warp Agent is the default, so there's nothing extra to configure. * **Oz CLI** - Run `oz agent run-cloud --prompt "..."` with no `--harness` flag, or pass `--harness oz` explicitly. * **API and SDK** - Omit the `harness` field on the agent config, or set it to `oz`. See the [API reference](/reference/api-and-sdk/). -For a complete walkthrough, see the [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/). +For a complete walkthrough, see the [Cloud agents quickstart](/platform/quickstart/). ## Related pages -* [Harnesses in Oz](/agent-platform/cloud-agents/harnesses/) — choose between Warp Agent, Claude Code, and Codex. -* [Claude Code with Oz](/agent-platform/cloud-agents/harnesses/claude-code/) — Claude Code as a cloud harness. -* [Codex with Oz](/agent-platform/cloud-agents/harnesses/codex/) — Codex as a cloud harness. +* [Harnesses in Oz](/platform/harnesses/) — choose between Warp Agent, Claude Code, and Codex. +* [Claude Code with Oz](/platform/harnesses/claude-code/) — Claude Code as a cloud harness. +* [Codex with Oz](/platform/harnesses/codex/) — Codex as a cloud harness. * [Model choice](/agent-platform/inference/model-choice/) — the model catalog Warp Agent routes across. * [Agent Profiles and permissions](/agent-platform/capabilities/agent-profiles-permissions/) — configure the default model, autonomy, and tool access for Warp Agent. -* [Skills as agents](/agent-platform/cloud-agents/skills-as-agents/) — turn a saved skill into a reusable Warp Agent run. +* [Skills as agents](/platform/skills-as-agents/) — turn a saved skill into a reusable Warp Agent run. diff --git a/src/content/docs/agent-platform/cloud-agents/overview.mdx b/src/content/docs/platform/index.mdx similarity index 56% rename from src/content/docs/agent-platform/cloud-agents/overview.mdx rename to src/content/docs/platform/index.mdx index 087e45bb2..04a4cd550 100644 --- a/src/content/docs/agent-platform/cloud-agents/overview.mdx +++ b/src/content/docs/platform/index.mdx @@ -10,13 +10,13 @@ import VideoEmbed from '@components/VideoEmbed.astro'; Cloud agents are autonomous, background agents that run on Warp's cloud infrastructure or your own, triggered by system events, schedules, or integrations like Slack and GitHub. They execute tasks with full observability — every run is tracked, inspectable, and shareable across your team. -**New to cloud agents?** Start with the [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) to run your first cloud agent in ~10 minutes. +**New to cloud agents?** Start with the [Cloud agents quickstart](/platform/quickstart/) to run your first cloud agent in ~10 minutes. ### Monitor, inspect, and share cloud agent runs -To understand what a cloud agent did, start from the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs). From there, you can find a run by source, status, trigger, or owner; open the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review. +To understand what a cloud agent did, start from the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app or the [Runs page in the Oz web app](/platform/oz-web-app/#runs). From there, you can find a run by source, status, trigger, or owner; open the run transcript; inspect the prompt, plan, commands, logs, and output; and share the session link with teammates for review. -For a full walkthrough, see [Viewing cloud agent runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). If the run came from Slack, Linear, GitHub Actions, a schedule, the CLI, or the API, it still produces a reviewable cloud agent run record. +For a full walkthrough, see [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/). If the run came from Slack, Linear, GitHub Actions, a schedule, the CLI, or the API, it still produces a reviewable cloud agent run record. <VideoEmbed url="https://youtu.be/poLkJhO7fdo" title="Cloud agents overview" /> @@ -25,15 +25,15 @@ For a full walkthrough, see [Viewing cloud agent runs](/agent-platform/cloud-age Cloud agents are designed for situations where: * **You need agents to react to system events.** - * Examples include crashes, bug reports, [Slack interactions](/agent-platform/cloud-agents/integrations/slack/), cron timers, or CI steps. + * Examples include crashes, bug reports, [Slack interactions](/platform/integrations/slack/), cron timers, or CI steps. * **You want observability into agent activity across a team or system.** * This includes being able to see what ran, when it ran, what triggered it, what the agent did, and how teammates can review or share the result. * **You need more parallelism than local execution typically allows.** * For example, running many agent tasks concurrently in the cloud, sharding a repo-wide task into multiple runs, or fanning out the same task across multiple targets. * **You want agents to operate continuously as part of engineering infrastructure.** - * This includes [scheduled maintenance tasks](/agent-platform/cloud-agents/triggers/scheduled-agents/) and integration-driven automation. + * This includes [scheduled maintenance tasks](/platform/triggers/scheduled-agents/) and integration-driven automation. -![Oz use cases across the development lifecycle: Plan, Prototype, Build, Validate, Review + Merge, Deploy + Monitor](../../../../assets/agent-platform/oz-use-cases.png) +![Oz use cases across the development lifecycle: Plan, Prototype, Build, Validate, Review + Merge, Deploy + Monitor](../../../assets/agent-platform/oz-use-cases.png) --- @@ -44,7 +44,7 @@ A cloud agent run is represented as an agent task. A task is created when a trig Each task includes: * **Inputs**: a prompt, and often additional context from the triggering system (for example a Slack message, PR metadata, or CI logs). -* **Execution context (optional)**: an [Environment](/agent-platform/cloud-agents/environments/) that defines the repo, image, and startup commands the agent should run with. +* **Execution context (optional)**: an [Environment](/platform/environments/) that defines the repo, image, and startup commands the agent should run with. * **Lifecycle state**: created → running → completed / failed. * **Persistent record**: status, metadata, and a session transcript that can be reviewed after the task completes, including the prompt, plan, commands, logs, outputs, and follow-up messages where available. @@ -55,19 +55,19 @@ If you are evaluating whether something should be a cloud agent, a good test is ### How cloud agents work -Cloud agents run on the [Oz Platform](/agent-platform/cloud-agents/platform/), which provides the primitives for triggering work, orchestrating tasks, executing agents (optionally in environments), injecting secrets, and inspecting results. +Cloud agents run on the [Oz Platform](/platform/overview/), which provides the primitives for triggering work, orchestrating tasks, executing agents (optionally in environments), injecting secrets, and inspecting results. * Something **triggers** an agent task. * The **orchestrator creates** and tracks the task. -* The agent **executes** on a host, optionally inside an [environment](/agent-platform/cloud-agents/environments/), with whatever [secrets](/agent-platform/cloud-agents/secrets/) and credentials it needs. +* The agent **executes** on a host, optionally inside an [environment](/platform/environments/), with whatever [secrets](/platform/secrets/) and credentials it needs. -The exact way tasks are triggered and executed depends on your deployment model (for example CLI-only, Warp-hosted orchestration, or self-hosted execution). Those options are covered in the [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) pages. +The exact way tasks are triggered and executed depends on your deployment model (for example CLI-only, Warp-hosted orchestration, or self-hosted execution). Those options are covered in the [Deployment Patterns](/platform/deployment-patterns/) pages. -For teams that need execution to stay within their network boundary, self-hosting supports two architectures: a **managed** worker daemon that lets Oz orchestrate agents in Docker containers on your machines, and an **unmanaged** mode where you run `oz agent run` directly in your CI, Kubernetes, or dev environment. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for details. +For teams that need execution to stay within their network boundary, self-hosting supports two architectures: a **managed** worker daemon that lets Oz orchestrate agents in Docker containers on your machines, and an **unmanaged** mode where you run `oz agent run` directly in your CI, Kubernetes, or dev environment. See [Self-hosting](/platform/self-hosting/) for details. ### What you get by default -Because cloud agents run on the [Oz Platform](/agent-platform/cloud-agents/platform/), each run is tracked and produces a persistent record that can be observed, shared, and reviewed (even if execution happens outside the Warp app). +Because cloud agents run on the [Oz Platform](/platform/overview/), each run is tracked and produces a persistent record that can be observed, shared, and reviewed (even if execution happens outside the Warp app). #### Codebase Context @@ -77,17 +77,17 @@ Cloud agent runs automatically benefit from [Codebase Context](/agent-platform/c Cloud agent tasks are designed to be inspectable by the team: -* The [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs) surface task status, source, trigger, creator, history, and credit usage. -* [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) opens the run transcript so teammates can inspect the prompt, plan, commands, logs, files changed, outputs, and follow-up messages where available. +* The [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app and the [Runs page in the Oz web app](/platform/oz-web-app/#runs) surface task status, source, trigger, creator, history, and credit usage. +* [Cloud agent session sharing](/platform/viewing-cloud-agent-runs/) opens the run transcript so teammates can inspect the prompt, plan, commands, logs, files changed, outputs, and follow-up messages where available. * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) lets authorized teammates share, monitor, and steer live local or third-party agent sessions. #### Centralized configuration -Cloud agent workflows often rely on shared configuration such as [MCP servers](/agent-platform/cloud-agents/mcp/), rules, saved prompts, environment variables, and [secrets](/agent-platform/cloud-agents/secrets/). +Cloud agent workflows often rely on shared configuration such as [MCP servers](/platform/mcp/), rules, saved prompts, environment variables, and [secrets](/platform/secrets/). Warp supports centralized configuration so the same workflow behaves consistently across triggers (for example Slack + CI + schedules), without duplicating setup in every system. -For details on configuring MCP servers for cloud agents, see [MCP Servers](/agent-platform/cloud-agents/mcp/). +For details on configuring MCP servers for cloud agents, see [MCP Servers](/platform/mcp/). #### API access to tasks @@ -99,12 +99,12 @@ The Oz Platform exposes task visibility via the [**Oz API and SDKs**](/reference ### Using cloud agents with or without the Warp app -Cloud agents do not require the Warp app. Teams can deploy and operate them through the [Oz Platform](/agent-platform/cloud-agents/platform/) using: +Cloud agents do not require the Warp app. Teams can deploy and operate them through the [Oz Platform](/platform/overview/) using: * [Oz CLI](/reference/cli/) — run agents from scripts, CI, or the terminal -* [Oz web app](/agent-platform/cloud-agents/oz-web-app/) — visual interface for managing runs, schedules, environments, and integrations (works on mobile) +* [Oz web app](/platform/oz-web-app/) — visual interface for managing runs, schedules, environments, and integrations (works on mobile) * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) — attach to running tasks to monitor or steer -* [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) — view agent activity and run history in the Warp app +* [Agent Management Panel](/platform/managing-cloud-agents/) — view agent activity and run history in the Warp app * [APIs and SDKs](/reference/api-and-sdk/) — programmatic access for custom integrations If your team also uses Warp's terminal, you get an additional workflow: tasks launched via the CLI can be handed off into an interactive session for review, edits, or continuation. @@ -113,7 +113,7 @@ If your team also uses Warp's terminal, you get an additional workflow: tasks la ### Billing and plan requirements -Cloud agents and [integrations](/agent-platform/cloud-agents/integrations/) run on the [Oz Platform](/agent-platform/cloud-agents/platform/) control plane, and usage is billed using credits. +Cloud agents and [integrations](/platform/integrations/) run on the [Oz Platform](/platform/overview/) control plane, and usage is billed using credits. :::note [Bring Your Own API Key (BYOK)](/agent-platform/inference/bring-your-own-api-key/) is not supported for cloud agent runs. BYOK keys are stored locally on your device and are not accessible to cloud-hosted agents. All cloud agent runs consume Warp credits. @@ -137,7 +137,7 @@ Integrations require you to be part of a [Warp team](/knowledge-and-collaboratio * **Credit requirements** * Your team must have at least 20 credits available to run cloud agents and integrations. -For more details, see [Access, Billing, and Identity Permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/). +For more details, see [Access, Billing, and Identity Permissions](/platform/team-access-billing-and-identity/). :::caution If your credit balance reaches zero, cloud agent runs will not be able to execute until credits are replenished. @@ -147,16 +147,16 @@ If your credit balance reaches zero, cloud agent runs will not be able to execut ### Learn more -* [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) — run your first cloud agent with an environment in ~10 minutes. -* [Oz Platform](/agent-platform/cloud-agents/platform/) — CLI, Oz API/SDK, orchestration, tasks, environments, hosts, integrations, and more. -* [Harnesses](/agent-platform/cloud-agents/harnesses/) — pick between Warp Agent, Claude Code, and Codex for any cloud agent run. -* [Agents](/agent-platform/cloud-agents/agents/) — cloud agents that own and execute runs on your team. -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) — coordinate a parent agent and its child agents across local and cloud runs to build supervisor/worker, fan-out, critic, DAG, and swarm workflows. -* [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) — run agents based on reusable skill definitions from the CLI, web app, API, or on a schedule. +* [Cloud agents quickstart](/platform/quickstart/) — run your first cloud agent with an environment in ~10 minutes. +* [Oz Platform](/platform/overview/) — CLI, Oz API/SDK, orchestration, tasks, environments, hosts, integrations, and more. +* [Harnesses](/platform/harnesses/) — pick between Warp Agent, Claude Code, and Codex for any cloud agent run. +* [Agents](/platform/agents/) — cloud agents that own and execute runs on your team. +* [Multi-agent orchestration](/platform/orchestration/) — coordinate a parent agent and its child agents across local and cloud runs to build supervisor/worker, fan-out, critic, DAG, and swarm workflows. +* [Skills as Agents](/platform/skills-as-agents/) — run agents based on reusable skill definitions from the CLI, web app, API, or on a schedule. * [Oz CLI](/reference/cli/) — shows how to run agents in non-interactive mode from CI, scripts, or remote machines, including auth and common commands. -* [Environments](/agent-platform/cloud-agents/environments/) — explains how environments provide the runtime context (repo, image, startup commands) for agent tasks. +* [Environments](/platform/environments/) — explains how environments provide the runtime context (repo, image, startup commands) for agent tasks. * [Oz API and SDK](/reference/api-and-sdk/) — documents the REST API for creating, querying, and monitoring agent tasks programmatically. -* [Agent Secrets](/agent-platform/cloud-agents/secrets/) — covers how to store, scope, and inject credentials into agent runs safely. -* [MCP Servers](/agent-platform/cloud-agents/mcp/) — how to configure MCP servers for agent tool access and how MCP configuration is applied across runs. -* [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) (beta) — compares common ways to deploy cloud agents and when to use each. -* [Access, Billing, and Identity Permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) — explains individual and team-level requirements, credit billing behavior, and the permission model for who can run, view, and steer cloud agent tasks. +* [Agent Secrets](/platform/secrets/) — covers how to store, scope, and inject credentials into agent runs safely. +* [MCP Servers](/platform/mcp/) — how to configure MCP servers for agent tool access and how MCP configuration is applied across runs. +* [Deployment Patterns](/platform/deployment-patterns/) (beta) — compares common ways to deploy cloud agents and when to use each. +* [Access, Billing, and Identity Permissions](/platform/team-access-billing-and-identity/) — explains individual and team-level requirements, credit billing behavior, and the permission model for who can run, view, and steer cloud agent tasks. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx b/src/content/docs/platform/integrations/azure-devops.mdx similarity index 91% rename from src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx rename to src/content/docs/platform/integrations/azure-devops.mdx index 4ea16bc1c..a7cbf7702 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx +++ b/src/content/docs/platform/integrations/azure-devops.mdx @@ -47,7 +47,7 @@ For Azure DevOps Server (self-hosted), sign in at `https://{server}/{collection} ## Step 2: Store the token as a Warp-managed secret -Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. +Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/platform/secrets/) documentation for full details on scoping and managing secrets. 1. Run the following command: @@ -98,7 +98,7 @@ Use single quotes around setup commands that reference secrets. Double quotes ca * The second `--setup-command` with any dependency install or build steps your project requires. For example, `npm ci` or `pip install -r requirements.txt`. :::caution -Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/agent-platform/cloud-agents/environments/#environment-design-and-best-practices) for guidance. +Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/platform/environments/#environment-design-and-best-practices) for guidance. ::: 3. Note the environment ID returned. You will need it in the next step. @@ -121,9 +121,9 @@ oz agent run-cloud --environment <ENV_ID> --prompt "Your task here" With your environment configured, you can connect it to any Warp trigger exactly as you would with a GitHub-backed environment: -* **Slack** — Tag **@Oz** in a message to start an agent run against your Azure DevOps repo. See [Slack](/agent-platform/cloud-agents/integrations/slack/). -* **Linear** — Tag **@Oz** on an issue to kick off a workflow. See [Linear](/agent-platform/cloud-agents/integrations/linear/). -* **Scheduled agents** — Run agents on a recurring schedule. See [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). +* **Slack** — Tag **@Oz** in a message to start an agent run against your Azure DevOps repo. See [Slack](/platform/integrations/slack/). +* **Linear** — Tag **@Oz** on an issue to kick off a workflow. See [Linear](/platform/integrations/linear/). +* **Scheduled agents** — Run agents on a recurring schedule. See [Scheduled Agents](/platform/triggers/scheduled-agents/). :::note Native support for opening Azure DevOps pull requests from agent-generated changes is planned as a future enhancement. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx b/src/content/docs/platform/integrations/bitbucket.mdx similarity index 91% rename from src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx rename to src/content/docs/platform/integrations/bitbucket.mdx index 2f02af4d2..632cfcd8c 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx +++ b/src/content/docs/platform/integrations/bitbucket.mdx @@ -55,7 +55,7 @@ Bitbucket Cloud API tokens are managed through your Atlassian Account, which is ### Step 2: Store the token as a Warp-managed secret -Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. +Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/platform/secrets/) documentation for full details on scoping and managing secrets. 1. Run the following command: @@ -103,7 +103,7 @@ Use single quotes around setup commands that reference secrets. Double quotes ca * The second `--setup-command` with any dependency install or build steps your project requires (for example, `npm ci` or `pip install -r requirements.txt`) :::caution -Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/agent-platform/cloud-agents/environments/#environment-design-and-best-practices) for guidance. +Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/platform/environments/#environment-design-and-best-practices) for guidance. ::: 3. Note the environment ID returned. You will need it in the next step. @@ -130,7 +130,7 @@ Setup commands run on a fresh container for every agent run. Write them to be id ### Step 2: Store the token as a Warp-managed secret -Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. +Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/platform/secrets/) documentation for full details on scoping and managing secrets. 1. Run the following command: @@ -178,7 +178,7 @@ Use single quotes around setup commands that reference secrets, so `$BITBUCKET_T * The second `--setup-command` with any dependency install or build steps your project requires (for example, `npm ci` or `pip install -r requirements.txt`) :::caution -Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/agent-platform/cloud-agents/environments/#environment-design-and-best-practices) for guidance. +Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/platform/environments/#environment-design-and-best-practices) for guidance. ::: 3. Note the environment ID returned. You will need it in the next step. @@ -201,9 +201,9 @@ oz agent run-cloud --environment <ENV_ID> --prompt "Your task here" With your environment configured, you can connect it to any Warp trigger exactly as you would with a GitHub-backed environment: -* **Slack** — Tag **@Oz** in a message to start an agent run against your Bitbucket repo. See [Slack](/agent-platform/cloud-agents/integrations/slack/). -* **Linear** — Tag **@Oz** on an issue to kick off a workflow. See [Linear](/agent-platform/cloud-agents/integrations/linear/). -* **Scheduled agents** — Run agents on a recurring schedule. See [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). +* **Slack** — Tag **@Oz** in a message to start an agent run against your Bitbucket repo. See [Slack](/platform/integrations/slack/). +* **Linear** — Tag **@Oz** on an issue to kick off a workflow. See [Linear](/platform/integrations/linear/). +* **Scheduled agents** — Run agents on a recurring schedule. See [Scheduled Agents](/platform/triggers/scheduled-agents/). :::note Native support for opening Bitbucket pull requests from agent-generated changes is planned as a future enhancement. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx b/src/content/docs/platform/integrations/cloud-providers.mdx similarity index 95% rename from src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx rename to src/content/docs/platform/integrations/cloud-providers.mdx index fffeee3a6..675b7bf07 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx +++ b/src/content/docs/platform/integrations/cloud-providers.mdx @@ -127,7 +127,7 @@ To allow multiple specific principals, use a list of subjects: Finally, configure the cloud agent environment to use your new AWS role. 1. Open the [Oz web app](https://oz.warp.dev). -2. Create or edit an environment. See [Environments](/agent-platform/cloud-agents/oz-web-app/#environments) for instructions. +2. Create or edit an environment. See [Environments](/platform/oz-web-app/#environments) for instructions. 3. Expand the **AWS** section and enter the AWS role ARN from Step 2. 4. Save the environment. @@ -213,7 +213,7 @@ for the full syntax supported. Finally, configure the cloud agent environment to use your Workload Identity Federation provider. 1. Open the [Oz web app](https://oz.warp.dev). -2. Create or edit an environment. See [Environments](/agent-platform/cloud-agents/oz-web-app/#environments) for instructions. +2. Create or edit an environment. See [Environments](/platform/oz-web-app/#environments) for instructions. 3. Expand the **GCP** section and enter the project number, pool ID, and provider ID from Step 1. 4. Save the environment. @@ -313,10 +313,10 @@ The following claims are derived from an agent run: * `run_id`: the unique identifier for the individual run. This is not suitable for configuring access, but is useful to log for debugging. -* `environment`: the unique identifier for the agent's [Environment](/agent-platform/cloud-agents/environments/). -* `agent_name`: the name of the [Skill](/agent-platform/cloud-agents/skills-as-agents/) that the agent was invoked with. +* `environment`: the unique identifier for the agent's [Environment](/platform/environments/). +* `agent_name`: the name of the [Skill](/platform/skills-as-agents/) that the agent was invoked with. * `skill_spec`: the canonical identifier for the skill, such as `github-org/github-repo:.warp/skills/skill-name/SKILL.md`. -* `host`: the execution host. This will either be `warp`, for Warp-hosted agents, or the worker ID if [self-hosting](/agent-platform/cloud-agents/self-hosting/). +* `host`: the execution host. This will either be `warp`, for Warp-hosted agents, or the worker ID if [self-hosting](/platform/self-hosting/). ### Example token diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx b/src/content/docs/platform/integrations/github-actions.mdx similarity index 96% rename from src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx rename to src/content/docs/platform/integrations/github-actions.mdx index 14c3b07bb..a9f0a4dd3 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx +++ b/src/content/docs/platform/integrations/github-actions.mdx @@ -9,7 +9,7 @@ import VideoEmbed from '@components/VideoEmbed.astro'; Run agents directly in your GitHub Actions workflows using `oz-agent-action`. The agent integrates seamlessly into your CI pipeline, automating tasks like code review, issue triage, bug fixing, and maintenance using your repository context and GitHub permissions. This page covers how the integration works, how to set it up, and common automation patterns for development teams. :::note -**Getting started?** See the [GitHub Actions quickstart](/agent-platform/cloud-agents/integrations/quickstart-github-actions/) to set up your first workflow, or visit the [oz-agent-action repository](https://github.com/warpdotdev/oz-agent-action) for detailed setup instructions and ready-to-use workflow templates. +**Getting started?** See the [GitHub Actions quickstart](/platform/integrations/quickstart-github-actions/) to set up your first workflow, or visit the [oz-agent-action repository](https://github.com/warpdotdev/oz-agent-action) for detailed setup instructions and ready-to-use workflow templates. ::: If you're comparing GitHub Actions with schedules, Slack, Linear, the Oz CLI, or API-triggered runs, see [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/). @@ -43,7 +43,7 @@ The `oz-agent-action` is a GitHub Action that wraps the Oz CLI and: To use agents in GitHub Actions, you need: -* A [**Warp API Key**](/reference/cli/api-keys/) stored as a [GitHub secret](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions) — this authenticates the agent with Warp. Pick a personal key if you want commits attributed to you, or an agent key to run as a [cloud agent](/agent-platform/cloud-agents/agents/) on your team. See [API keys](/reference/cli/api-keys/) for when to pick each. +* A [**Warp API Key**](/reference/cli/api-keys/) stored as a [GitHub secret](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions) — this authenticates the agent with Warp. Pick a personal key if you want commits attributed to you, or an agent key to run as a [cloud agent](/platform/agents/) on your team. See [API keys](/reference/cli/api-keys/) for when to pick each. * Workflow permissions that match your intended actions (for example, `pull-requests: write` if the agent should commit or comment on PRs) — the agent performs actions on your behalf using the GitHub token available to the workflow * The `oz-agent-action` step added to your workflow * **For private repositories using `@oz-agent` mention workflows**: The [`oz-agent`](https://github.com/oz-agent) GitHub user must be [invited as a member](https://docs.github.com/en/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization) of your GitHub organization (see [Responding to comments with @ mentions](#1-responding-to-comments-with--mentions) for details) diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx b/src/content/docs/platform/integrations/gitlab.mdx similarity index 91% rename from src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx rename to src/content/docs/platform/integrations/gitlab.mdx index 6f9dcc651..6586594f3 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx +++ b/src/content/docs/platform/integrations/gitlab.mdx @@ -48,7 +48,7 @@ These steps generate a personal access token tied to your GitLab account. If you ## Step 2: Store the token as a Warp-managed secret -Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/agent-platform/cloud-agents/secrets/) documentation for full details on scoping and managing secrets. +Warp injects managed secrets as environment variables at runtime and never exposes them in logs or configuration files. See the [Secrets](/platform/secrets/) documentation for full details on scoping and managing secrets. 1. Run the following command: @@ -97,7 +97,7 @@ Use single quotes around setup commands that reference secrets. Double quotes ca * The second `--setup-command` with any dependency install or build steps your project requires. For example, `npm ci` or `pip install -r requirements.txt`. :::caution -Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/agent-platform/cloud-agents/environments/#environment-design-and-best-practices) for guidance. +Setup commands run on a fresh container for every agent run. Write them to be idempotent — commands that assume existing state (such as a partially cloned repo or a pre-built cache) can fail unpredictably. See [Environment design and best practices](/platform/environments/#environment-design-and-best-practices) for guidance. ::: 3. Note the environment ID returned. You will need it in the next step. @@ -120,9 +120,9 @@ oz agent run-cloud --environment <ENV_ID> --prompt "Your task here" With your environment configured, you can connect it to any Warp trigger exactly as you would with a GitHub-backed environment: -* **Slack** — Tag **@Oz** in a message to start an agent run against your GitLab repo. See [Slack](/agent-platform/cloud-agents/integrations/slack/). -* **Linear** — Tag **@Oz** on an issue to kick off a workflow. See [Linear](/agent-platform/cloud-agents/integrations/linear/). -* **Scheduled agents** — Run agents on a recurring schedule. See [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). +* **Slack** — Tag **@Oz** in a message to start an agent run against your GitLab repo. See [Slack](/platform/integrations/slack/). +* **Linear** — Tag **@Oz** on an issue to kick off a workflow. See [Linear](/platform/integrations/linear/). +* **Scheduled agents** — Run agents on a recurring schedule. See [Scheduled Agents](/platform/triggers/scheduled-agents/). :::note Native support for opening GitLab merge requests from agent-generated changes is planned as a future enhancement. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx b/src/content/docs/platform/integrations/index.mdx similarity index 52% rename from src/content/docs/agent-platform/cloud-agents/integrations/index.mdx rename to src/content/docs/platform/integrations/index.mdx index dd46a026c..2be2245d8 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx +++ b/src/content/docs/platform/integrations/index.mdx @@ -7,7 +7,7 @@ description: >- --- import VideoEmbed from '@components/VideoEmbed.astro'; -Warp integrations let your team trigger agents directly from the terminal, or from tools like [Slack](/agent-platform/cloud-agents/integrations/slack/) and [Linear](/agent-platform/cloud-agents/integrations/linear/). Once set up, agents can: +Warp integrations let your team trigger agents directly from the terminal, or from tools like [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/). Once set up, agents can: * Read conversation or issue context * Run code inside your codebase in a remote environment @@ -29,10 +29,10 @@ Use the setup walkthrough below for a quick look at how environments connect to <VideoEmbed url="https://www.youtube.com/watch?v=ahFfInVD0HQ" title="Cloud agents integrations overview video" /> -* [Integrations quickstart](/agent-platform/cloud-agents/integrations/quickstart/) - Trigger your first agent from Slack and watch the run from start to finish. +* [Integrations quickstart](/platform/integrations/quickstart/) - Trigger your first agent from Slack and watch the run from start to finish. * [Integration setup](/reference/cli/integration-setup/) - Configure environments, GitHub authorization, CLI flags, and integrations in more detail. -* [Slack](/agent-platform/cloud-agents/integrations/slack/) and [Linear](/agent-platform/cloud-agents/integrations/linear/) - Trigger agents from team conversations, issues, and comments. -* [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) - Run agents from CI workflows and repository events. -* [GitLab](/agent-platform/cloud-agents/integrations/gitlab/), [Bitbucket](/agent-platform/cloud-agents/integrations/bitbucket/), and [Azure DevOps](/agent-platform/cloud-agents/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. -* [AWS, GCP, and other cloud providers](/agent-platform/cloud-agents/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Monitor and review integration-triggered runs across your team by source, status, or creator. +* [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) - Trigger agents from team conversations, issues, and comments. +* [GitHub Actions](/platform/integrations/github-actions/) - Run agents from CI workflows and repository events. +* [GitLab](/platform/integrations/gitlab/), [Bitbucket](/platform/integrations/bitbucket/), and [Azure DevOps](/platform/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. +* [AWS, GCP, and other cloud providers](/platform/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. +* [Managing cloud agents](/platform/managing-cloud-agents/) - Monitor and review integration-triggered runs across your team by source, status, or creator. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx b/src/content/docs/platform/integrations/linear.mdx similarity index 80% rename from src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx rename to src/content/docs/platform/integrations/linear.mdx index eb0fdff49..791ee47f4 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx +++ b/src/content/docs/platform/integrations/linear.mdx @@ -22,7 +22,7 @@ This guide explains what the integration does, how it works end-to-end, and how Tagging @Oz on an issue or in a Linear comment starts an agent run. Oz clones the repositories defined in your environment, sets up your development environment using your Docker image and setup commands, and begins working through the task with full context from your codebase and the Linear issue. Agents post updates as they progress, including a task list, elapsed time, and checkpoints, so you can follow along without leaving Linear. -Agents also share a link to an interactive remote session using Warp's [cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). Opening this link lets you view the live terminal output for the running agent in Warp or in the browser. From there, you can interrupt or guide the agent with additional instructions when needed. Once the agent finishes, it will create a pull request on your behalf — using your GitHub permissions — and post a summary of its work and the PR link back into Linear. +Agents also share a link to an interactive remote session using Warp's [cloud agent session sharing](/platform/viewing-cloud-agent-runs/). Opening this link lets you view the live terminal output for the running agent in Warp or in the browser. From there, you can interrupt or guide the agent with additional instructions when needed. Once the agent finishes, it will create a pull request on your behalf — using your GitHub permissions — and post a summary of its work and the PR link back into Linear. You can start an agent in two ways: @@ -39,13 +39,13 @@ Agents keep you informed through: Session sharing works in Warp or in a browser view and allows multiple teammates to watch the session. -To monitor Linear-triggered runs alongside the rest of your team's agents, open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app, where integration-triggered runs appear in the **All** tab. +To monitor Linear-triggered runs alongside the rest of your team's agents, open the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app, where integration-triggered runs appear in the **All** tab. -![Live cloud agent session shared from a Linear issue, viewed in Warp on Web.](../../../../../assets/agent-platform/linear-warp-on-web.png) +![Live cloud agent session shared from a Linear issue, viewed in Warp on Web.](../../../../assets/agent-platform/linear-warp-on-web.png) #### Joining the remote session -Selecting [**Open in Warp**](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) (or the web option) opens the active session. You'll see: +Selecting [**Open in Warp**](/platform/viewing-cloud-agent-runs/) (or the web option) opens the active session. You'll see: * The agent’s full execution log * The plan pane with the task list @@ -68,8 +68,8 @@ Because PRs are created as _you_, this makes code review, auditing, and team col ### Requirements * **Team membership** - The Linear integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free. -* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details. -* **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/agent-platform/cloud-agents/self-hosting/) on their own infrastructure. +* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) for details. +* **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/platform/self-hosting/) on their own infrastructure. * **Identity** - You must be logged into Warp with the same email as your Linear workspace. * **GitHub authorization** - You must authorize the Warp GitHub app the first time you trigger an agent. * The repositories involved must be included in your environment and accessible to the Warp GitHub app. @@ -79,7 +79,7 @@ Because PRs are created as _you_, this makes code review, auditing, and team col ### How to configure the integration -Setup involves two steps powered by the [Oz CLI](/reference/cli/). For more instructions, see [Integrations Overview](/agent-platform/cloud-agents/integrations/). +Setup involves two steps powered by the [Oz CLI](/reference/cli/). For more instructions, see [Integrations Overview](/platform/integrations/). #### 1. Create an environment @@ -94,7 +94,7 @@ You can create an environment via: * The CLI * The guided flow using `/create-environment` ([Slash Commands](/agent-platform/capabilities/slash-commands/)) -For full instructions, see our [Environment Setup](/agent-platform/cloud-agents/integrations/) docs. +For full instructions, see our [Environment Setup](/platform/integrations/) docs. #### 2. Create the Linear integration @@ -137,4 +137,4 @@ After revoking access, Warp will no longer be able to read issues, receive trigg ### Troubleshooting -If something isn't working as expected—missing repos, PR failures, Linear not detecting Oz, or environment issues—see our [Integrations Troubleshooting](/agent-platform/cloud-agents/integrations/#troubleshooting) page for detailed guidance on GitHub permissions, environment configuration, and common setup problems. +If something isn't working as expected—missing repos, PR failures, Linear not detecting Oz, or environment issues—see our [Integrations Troubleshooting](/platform/integrations/#troubleshooting) page for detailed guidance on GitHub permissions, environment configuration, and common setup problems. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx b/src/content/docs/platform/integrations/quickstart-github-actions.mdx similarity index 87% rename from src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx rename to src/content/docs/platform/integrations/quickstart-github-actions.mdx index 0f752f397..db41a2bac 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx +++ b/src/content/docs/platform/integrations/quickstart-github-actions.mdx @@ -13,7 +13,7 @@ Add agents to your GitHub Actions workflows with [`oz-agent-action`](https://git ## Prerequisites -* **Warp API key** - Create one in the [Oz web app](https://oz.warp.dev/settings). Use a personal key if the agent should commit as you, or an agent key (which runs as a [cloud agent](/agent-platform/cloud-agents/agents/) on your team) with [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization). See [API Keys](/reference/cli/api-keys/) for the full creation flow. +* **Warp API key** - Create one in the [Oz web app](https://oz.warp.dev/settings). Use a personal key if the agent should commit as you, or an agent key (which runs as a [cloud agent](/platform/agents/) on your team) with [team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization). See [API Keys](/reference/cli/api-keys/) for the full creation flow. * **A GitHub repository with Actions enabled** - The workflow file will live in `.github/workflows/` in your repo. --- @@ -78,7 +78,7 @@ To verify the workflow ran: Each `oz-agent-action` step creates a cloud agent run you can inspect from the Oz dashboard: -* **Oz web app** - Go to the [Runs page in the Oz web app](https://oz.warp.dev/runs) to see the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for a complete walkthrough. +* **Oz web app** - Go to the [Runs page in the Oz web app](https://oz.warp.dev/runs) to see the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/platform/viewing-cloud-agent-runs/) for a complete walkthrough. * **Warp app** - Open the conversations panel to see the run alongside your other agent activity. When the run completes, the agent posts feedback as inline review comments on the PR. @@ -91,4 +91,4 @@ When the run completes, the agent posts feedback as inline review comments on th * **Explore more workflow patterns** - The [oz-agent-action repository](https://github.com/warpdotdev/oz-agent-action) includes ready-to-use consumer workflow templates for responding to `@oz-agent` comments, auto-fixing labeled issues, daily issue summaries, fixing failing CI checks, and suggesting review fixes. Copy any template from `consumer-workflows/` into `.github/workflows/` in your repo. * **Use skills for reusable behavior** - Replace the inline `prompt` with a `skill` parameter to apply consistent, version-controlled instructions across all your CI workflows. See [Skills](/agent-platform/capabilities/skills/). -* **Read the full reference** - [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) covers all action inputs, output handling, session sharing for debugging, and troubleshooting. +* **Read the full reference** - [GitHub Actions](/platform/integrations/github-actions/) covers all action inputs, output handling, session sharing for debugging, and troubleshooting. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx b/src/content/docs/platform/integrations/quickstart.mdx similarity index 78% rename from src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx rename to src/content/docs/platform/integrations/quickstart.mdx index 1e92c8e66..b4b4103b8 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx +++ b/src/content/docs/platform/integrations/quickstart.mdx @@ -10,15 +10,15 @@ sidebar: Oz integrations let you trigger cloud agents directly from the tools your team already uses. This guide walks you through connecting Oz to Slack. Once set up, anyone on your team can tag @Oz in a message or thread to kick off a cloud agent that runs the task and posts results back to the conversation. :::note -**Want to connect with Linear instead?** The setup is the same — just substitute `slack` with `linear` in the CLI commands, or select Linear in the Oz web app. See [Linear](/agent-platform/cloud-agents/integrations/linear/) for details. +**Want to connect with Linear instead?** The setup is the same — just substitute `slack` with `linear` in the CLI commands, or select Linear in the Oz web app. See [Linear](/platform/integrations/linear/) for details. ::: --- ## Prerequisites -* **Eligible plan** - The Slack integration requires a Warp team on Build, Max, or Business plan with at least 20 credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/). -* **A cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one yet, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) or run `/create-environment` in Warp. +* **Eligible plan** - The Slack integration requires a Warp team on Build, Max, or Business plan with at least 20 credits available. See [Access, Billing, and Identity](/platform/team-access-billing-and-identity/). +* **A cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one yet, follow the [Cloud Agents Quickstart](/platform/quickstart/) or run `/create-environment` in Warp. * **GitHub authorization** - Warp needs access to your repos to clone code and open PRs. You'll be prompted to authorize the Warp GitHub app when you first create the integration. --- @@ -41,7 +41,7 @@ Run `oz integration create` to connect the Slack integration: oz integration create slack --environment <ENV_ID> ``` -Replace `<ENV_ID>` with your environment ID (see [Environments](/agent-platform/cloud-agents/environments/) if you need to create one). Find it with `oz environment list` on the Oz CLI or in the [Oz web app](https://oz.warp.dev). The CLI opens a browser window to authorize the Oz app in your workspace. +Replace `<ENV_ID>` with your environment ID (see [Environments](/platform/environments/) if you need to create one). Find it with `oz environment list` on the Oz CLI or in the [Oz web app](https://oz.warp.dev). The CLI opens a browser window to authorize the Oz app in your workspace. :::tip If the integration cannot be created or your first run cannot start, use the returned error code to narrow the fix. Common errors include: @@ -73,7 +73,7 @@ You can also tag @Oz inside an existing thread. Oz picks up the full thread hist While the agent works, progress updates appear directly in the Slack thread. To inspect the run in more detail: * **Click the session link** - Oz posts a link in the thread to open a live terminal view of the agent. Watch in real time, add follow-up instructions, or let it run to completion. -* **Go to the [Runs page in the Oz web app](https://oz.warp.dev/runs)** - See the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for a complete walkthrough. +* **Go to the [Runs page in the Oz web app](https://oz.warp.dev/runs)** - See the full run transcript: status, commands executed, files changed, and agent output. See [Viewing Cloud Agent Runs](/platform/viewing-cloud-agent-runs/) for a complete walkthrough. When the task is complete, Oz posts a summary back to the original Slack thread. @@ -83,6 +83,6 @@ When the task is complete, Oz posts a summary back to the original Slack thread. ## Next steps -* **Customize agent behavior** - Use a [skill](/agent-platform/cloud-agents/skills-as-agents/) as the base prompt for your integration to give Oz consistent, reusable instructions across every run. +* **Customize agent behavior** - Use a [skill](/platform/skills-as-agents/) as the base prompt for your integration to give Oz consistent, reusable instructions across every run. * **Trigger agents programmatically** - Use the [API & SDK](/reference/api-and-sdk/) to build custom automations and integrations on top of agents. -* **Read the full Slack reference** - [Slack](/agent-platform/cloud-agents/integrations/slack/) covers identity mapping, team access, monitoring runs, troubleshooting, and uninstall instructions. +* **Read the full Slack reference** - [Slack](/platform/integrations/slack/) covers identity mapping, team access, monitoring runs, troubleshooting, and uninstall instructions. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx b/src/content/docs/platform/integrations/slack.mdx similarity index 84% rename from src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx rename to src/content/docs/platform/integrations/slack.mdx index 82ba3582d..f35c19add 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx +++ b/src/content/docs/platform/integrations/slack.mdx @@ -23,7 +23,7 @@ This page explains what the integration does, how it behaves inside Slack, and h Tagging @Oz in a message or thread starts an agent run. The agent clones the repositories in your environment, sets up your development environment using your Docker image and setup commands, and begins working with the context from the Slack conversation. Oz posts updates back into the thread as it progresses so you can follow along without opening your terminal. -Agents also share a link to an interactive remote session using Warp's [cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). Opening this link gives you a live terminal view of the cloud agent running your code. You can interrupt or steer the agent by providing additional instructions, and the agent will pick up where it left off with the new context. +Agents also share a link to an interactive remote session using Warp's [cloud agent session sharing](/platform/viewing-cloud-agent-runs/). Opening this link gives you a live terminal view of the cloud agent running your code. You can interrupt or steer the agent by providing additional instructions, and the agent will pick up where it left off with the new context. When the work is complete, Warp will create a pull request on your behalf using your GitHub permissions and send a summary and PR link back to the original Slack thread. @@ -50,12 +50,12 @@ Agents keep you informed directly in Slack via: * Activity updates showing progress throughout the run * An evolving task list and timeline * Checkpoints indicating major steps completed -* A direct link to the Oz run in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/), where you can view the full run transcript and metadata +* A direct link to the Oz run in the [Oz web app](/platform/oz-web-app/), where you can view the full run transcript and metadata * A session-sharing link that opens a live terminal view of the remote agent -[Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) works in Warp or in your browser and supports multiple teammates joining the same live session. +[Cloud agent session sharing](/platform/viewing-cloud-agent-runs/) works in Warp or in your browser and supports multiple teammates joining the same live session. -To monitor Slack-triggered runs alongside the rest of your team's agents, open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app, where integration-triggered runs appear in the **All** tab. +To monitor Slack-triggered runs alongside the rest of your team's agents, open the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app, where integration-triggered runs appear in the **All** tab. ### Joining the live remote session @@ -84,8 +84,8 @@ Because PRs are created as you, the workflow slots seamlessly into your team’s ### Requirements * **Team membership** - The Slack integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free. -* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details. -* **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/agent-platform/cloud-agents/self-hosting/) on their own infrastructure. +* **Plan and credits** - Your team must be on a plan that supports integrations (Build, Max, or Business) and have at least 20 credits available. See [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) for details. +* **Infrastructure** - By default, agents run on Warp-hosted infrastructure. Enterprise teams can [self-host agents](/platform/self-hosting/) on their own infrastructure. * **Identity** - You must be logged into Warp with the same email used in your Slack workspace. * **GitHub authorization** - You must authorize the **Warp GitHub app** the first time you trigger a Slack integration request. * The repositories involved must be included in your environment and accessible to the Warp GitHub app. @@ -119,7 +119,7 @@ oz environment create \ This flow analyzes your repos, recommends a Docker image, suggests setup commands, and can build + push a custom image if needed. -See the [Environment Setup](/agent-platform/cloud-agents/integrations/) docs for detailed instructions. +See the [Environment Setup](/platform/integrations/) docs for detailed instructions. #### 2. Create the Slack integration @@ -173,17 +173,17 @@ To remove the Oz app from your Slack workspace: 6. Confirm the removal. <figure> -![Warpy is just an internal Slackbot, your Warp slackbot should be called Oz.](../../../../../assets/agent-platform/delete-warpy.png) +![Warpy is just an internal Slackbot, your Warp slackbot should be called Oz.](../../../../assets/agent-platform/delete-warpy.png) <figcaption>The Oz Slackbot in Slack.</figcaption> </figure> -![Confirmation dialog to remove the Oz app from a Slack workspace.](../../../../../assets/agent-platform/remove-slack-app.png) +![Confirmation dialog to remove the Oz app from a Slack workspace.](../../../../assets/agent-platform/remove-slack-app.png) Once removed, Slack will immediately disable the integration for all teammates. Events for a disabled integration can return [`integration_disabled`](/reference/api-and-sdk/troubleshooting/errors/integration-disabled/). ### Troubleshooting -If something isn't working—missing repos, Slack not detecting @Oz, PR failures, or environment configuration issues—see the [Integrations Troubleshooting](/agent-platform/cloud-agents/integrations/#troubleshooting) page. It covers: +If something isn't working—missing repos, Slack not detecting @Oz, PR failures, or environment configuration issues—see the [Integrations Troubleshooting](/platform/integrations/#troubleshooting) page. It covers: * GitHub authorization and repo access * Docker image pull errors diff --git a/src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx b/src/content/docs/platform/managing-cloud-agents.mdx similarity index 79% rename from src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx rename to src/content/docs/platform/managing-cloud-agents.mdx index c69afe97f..aadee771c 100644 --- a/src/content/docs/agent-platform/cloud-agents/managing-cloud-agents.mdx +++ b/src/content/docs/platform/managing-cloud-agents.mdx @@ -8,7 +8,7 @@ sidebar: --- import VideoEmbed from '@components/VideoEmbed.astro'; -Warp provides two management surfaces for tracking and observing agent activity across your account and, where applicable, your team: the **Agent Management Panel** in the Warp app and the [**Runs** page in the Oz web app](/agent-platform/cloud-agents/oz-web-app/#runs), which also works on mobile devices. +Warp provides two management surfaces for tracking and observing agent activity across your account and, where applicable, your team: the **Agent Management Panel** in the Warp app and the [**Runs** page in the Oz web app](/platform/oz-web-app/#runs), which also works on mobile devices. Use these surfaces as the starting point for real-time agent observability in Warp. They help you see which agents are active, which runs are blocked or failed, where each run started, and which session link opens the prompt, plan, commands, logs, outputs, and follow-up messages behind the work. @@ -25,10 +25,10 @@ Warp's agent observability is run- and session-oriented. It is not a replacement <VideoEmbed url="https://www.loom.com/share/679c267ddd2d44519abf79edcb1122c7" title="Managing cloud agent runs video" /> -These management surfaces include your **local (interactive) agents** and [cloud agent](/agent-platform/cloud-agents/overview/) runs. +These management surfaces include your **local (interactive) agents** and [cloud agent](/platform/) runs. <figure style={{ maxWidth: "563px" }}> -![Warp's Agent Management Panel showing interactive and cloud agent runs.](../../../../assets/agent-platform/management-view-scannable-list.png) +![Warp's Agent Management Panel showing interactive and cloud agent runs.](../../../assets/agent-platform/management-view-scannable-list.png) <figcaption>Warp's Agent Management Panel showing interactive and cloud agent runs.</figcaption> </figure> @@ -66,7 +66,7 @@ Use the Agent Management Panel or Oz web app Runs page as the starting point whe 4. Share the session link with teammates if they need to review the same context. 5. For PR-producing workflows, include the session link alongside the PR link so reviewers can inspect both the code diff and the agent's execution context. -For cloud agent runs, the session opens in [Cloud agent session sharing](/agent-platform/cloud-agents/viewing-cloud-agent-runs/). For local interactive agents, the conversation opens in Warp and can be shared with [Agent Session Sharing](/agent-platform/local-agents/session-sharing/). +For cloud agent runs, the session opens in [Cloud agent session sharing](/platform/viewing-cloud-agent-runs/). For local interactive agents, the conversation opens in Warp and can be shared with [Agent Session Sharing](/agent-platform/local-agents/session-sharing/). --- @@ -83,8 +83,8 @@ Where the agent was launched from. Common sources include: * **Interactive:** an [agent conversation](/agent-platform/local-agents/overview/) started in the Warp app * **CLI**: a local run triggered by the [Oz CLI](/reference/cli/) * **API**: a run triggered by [Warp's API](/reference/api-and-sdk/) -* **Slack / Linear**: runs triggered by [integrations](/agent-platform/cloud-agents/integrations/) -* **Scheduled**: runs triggered on a [cron schedule](/agent-platform/cloud-agents/triggers/scheduled-agents/) +* **Slack / Linear**: runs triggered by [integrations](/platform/integrations/) +* **Scheduled**: runs triggered on a [cron schedule](/platform/triggers/scheduled-agents/) **Status** @@ -103,7 +103,7 @@ Warp uses a small set of statuses to help you quickly identify what needs attent **The primary interaction is simple:** -* Clicking a cloud agent row opens the [shared session](/agent-platform/cloud-agents/viewing-cloud-agent-runs/) for that run (prompt, plan, commands, logs, messages, and output where available). +* Clicking a cloud agent row opens the [shared session](/platform/viewing-cloud-agent-runs/) for that run (prompt, plan, commands, logs, messages, and output where available). * Clicking an interactive row opens the conversation locally in the Warp app. This makes the agents list a navigation surface: find the thing you care about, click once, and you’re in the right context to inspect or continue work. @@ -123,18 +123,18 @@ This is the fastest way to isolate "everything that failed today," "runs from Sl ### Orchestrated runs (parent and child) -When a parent agent spawns one or more child agents through [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/), the parent and each child are tracked as separate runs. Where you see them depends on the surface: +When a parent agent spawns one or more child agents through [multi-agent orchestration](/platform/orchestration/), the parent and each child are tracked as separate runs. Where you see them depends on the surface: * **Local children in the Warp app** - while you're viewing the parent agent, an orchestration pill bar above the agent view header shows one pill per child with a live status badge. Click a child pill to switch the pane to that child's conversation in place; click the parent pill - or the breadcrumb that replaces the pill bar while you're viewing a child - to return. Local children don't appear as separate rows in the Agent Management Panel list. * **Cloud children in the Warp app** - appear in the Agent Management Panel list as their own rows alongside the parent and other runs. Filter by source, status, or creator to isolate them. -* **Cloud children in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/)** - grouped under the parent's row on the Runs page, and surfaced together inside the parent's detail pane on a **Sub-agents** tab. +* **Cloud children in the [Oz web app](/platform/oz-web-app/)** - grouped under the parent's row on the Runs page, and surfaced together inside the parent's detail pane on a **Sub-agents** tab. The parent's own status reflects only its work - a parent can finish successfully while a child is still running or has failed. To verify that an orchestration completed, check each child individually from the pill bar (in the Warp app) or the **Sub-agents** tab (in the Oz web app). ## Related pages -* [Cloud agents overview](/agent-platform/cloud-agents/overview/) — What cloud agents are and when to use them. -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) — Parent/child model, run state transitions, and common orchestration patterns. -* [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. +* [Cloud agents overview](/platform/) — What cloud agents are and when to use them. +* [Multi-agent orchestration](/platform/orchestration/) — Parent/child model, run state transitions, and common orchestration patterns. +* [Viewing cloud agent runs](/platform/viewing-cloud-agent-runs/) — Open and inspect a remote cloud agent run. +* [Handoff between local and cloud agents](/platform/handoff/) — Move agent work between local and cloud, or continue a finished cloud run. +* [Oz web app](/platform/oz-web-app/) — Manage runs and schedules from any browser. diff --git a/src/content/docs/agent-platform/cloud-agents/mcp.mdx b/src/content/docs/platform/mcp.mdx similarity index 95% rename from src/content/docs/agent-platform/cloud-agents/mcp.mdx rename to src/content/docs/platform/mcp.mdx index 754fdd0ca..7dab1dc02 100644 --- a/src/content/docs/agent-platform/cloud-agents/mcp.mdx +++ b/src/content/docs/platform/mcp.mdx @@ -121,5 +121,5 @@ As a workaround, you can pass Figma mockups as **image context** to the agent, w * [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/) — choose between local, cloud, and shared MCP setup paths * [MCP Servers (CLI reference)](/reference/cli/mcp-servers/) — how to pass MCP configuration using the `--mcp` flag * [Model Context Protocol (MCP)](/agent-platform/capabilities/mcp/) — configuring MCP servers in Warp for local agents -* [Environments](/agent-platform/cloud-agents/environments/) — set up the runtime context (repo, image, startup commands) for cloud agent tasks -* [Secrets](/agent-platform/cloud-agents/secrets/) — store and inject credentials into agent runs safely +* [Environments](/platform/environments/) — set up the runtime context (repo, image, startup commands) for cloud agent tasks +* [Secrets](/platform/secrets/) — store and inject credentials into agent runs safely diff --git a/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx b/src/content/docs/platform/orchestration/index.mdx similarity index 84% rename from src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx rename to src/content/docs/platform/orchestration/index.mdx index 77df63359..b8a4d49ab 100644 --- a/src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx +++ b/src/content/docs/platform/orchestration/index.mdx @@ -12,7 +12,7 @@ Watch this walkthrough to see how a cloud agent can coordinate a team of agents <VideoEmbed url="https://www.youtube.com/watch?v=qeR79bhyFOw" title="How to orchestrate a team of agents in the cloud with Warp" /> -This page covers the orchestration model and the patterns it supports. To learn how to start an orchestrated run, see [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/). +This page covers the orchestration model and the patterns it supports. To learn how to start an orchestrated run, see [Running orchestrated agents](/platform/orchestration/multi-agent-runs/). ## The parent/child model @@ -21,14 +21,14 @@ An orchestrated workflow always has one **parent agent** and one or more **child * **Parent agent** - the agent that decides what work needs to be done, spawns child agents, and (optionally) merges their results. Any agent can become a parent the first time it spawns a child. * **Child agent** - an agent spawned by a parent with its own prompt, environment, and (optionally) a different model or agent runtime. A child runs its own work and reports back; it does not spawn its own children. -Orchestrations today are exactly one level deep: a parent and its direct children. The Warp app, the [Oz web app](/agent-platform/cloud-agents/oz-web-app/), and the [Oz API](/reference/api-and-sdk/) render that single level. The parent and each child each have an independent **run** with its own lifecycle, transcript, conversation, and credit usage. +Orchestrations today are exactly one level deep: a parent and its direct children. The Warp app, the [Oz web app](/platform/oz-web-app/), and the [Oz API](/reference/api-and-sdk/) render that single level. The parent and each child each have an independent **run** with its own lifecycle, transcript, conversation, and credit usage. ### Where parent and child agents can run The parent and child don't have to run in the same place. Orchestration supports four combinations: * **Local → local** - a [Warp Agent](/agent-platform/local-agents/overview/) conversation in the Warp app spawns child Warp Agent conversations on the same machine. Useful for trying orchestration patterns without spinning up cloud infrastructure. -* **Local → cloud** - a local parent spawns one or more cloud children that run in [environments](/agent-platform/cloud-agents/environments/) on Warp-hosted or self-hosted infrastructure. The parent keeps working while children execute in parallel. +* **Local → cloud** - a local parent spawns one or more cloud children that run in [environments](/platform/environments/) on Warp-hosted or self-hosted infrastructure. The parent keeps working while children execute in parallel. * **Cloud → cloud** - a cloud parent spawns cloud children that each run in their own environment. This is the canonical pattern for review swarms, large fan-outs, and any orchestration triggered from Slack, Linear, a schedule, or the API. * **Cloud → cloud-local** - a cloud parent spawns children that run inside the parent's own cloud environment, rather than each child getting its own environment. Useful when children need to share state with the parent (a filesystem, a long-running process, a shell session) or when spinning up an environment per child would be wasteful. @@ -88,7 +88,7 @@ The parent (the "writer") proposes a solution, then spawns a critic child to rev ### Review swarm (cloud → cloud) -A [scheduled](/agent-platform/cloud-agents/triggers/scheduled-agents/) or webhook-triggered parent spawns one cloud child per open pull request to run reviews in parallel. Each child posts its findings as a comment and exits. The parent fans in the results and posts a summary back to the triggering system. +A [scheduled](/platform/triggers/scheduled-agents/) or webhook-triggered parent spawns one cloud child per open pull request to run reviews in parallel. Each child posts its findings as a comment and exits. The parent fans in the results and posts a summary back to the triggering system. ### DAG @@ -111,15 +111,15 @@ In both cases, approval is required before the parent launches children. Approvi Because every parent and child is tracked as its own conversation or run, the existing observability surfaces work without changes: -* **[Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/)** - in the Warp app, the orchestration pill bar above the agent view header lets you switch between the parent and each child while you're viewing the parent. Cloud children also appear as their own rows in the Agent Management Panel list. -* **[Oz web app](/agent-platform/cloud-agents/oz-web-app/)** - the Runs page groups cloud children under the parent's row, and the parent's detail pane adds a **Sub-agents** tab. -* **[Oz API](/reference/api-and-sdk/)** - list every descendant of a parent in one call and fetch any run with its conversation, transcript, and artifacts. See [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/#retrieving-conversations-and-artifacts). +* **[Managing cloud agents](/platform/managing-cloud-agents/)** - in the Warp app, the orchestration pill bar above the agent view header lets you switch between the parent and each child while you're viewing the parent. Cloud children also appear as their own rows in the Agent Management Panel list. +* **[Oz web app](/platform/oz-web-app/)** - the Runs page groups cloud children under the parent's row, and the parent's detail pane adds a **Sub-agents** tab. +* **[Oz API](/reference/api-and-sdk/)** - list every descendant of a parent in one call and fetch any run with its conversation, transcript, and artifacts. See [Running orchestrated agents](/platform/orchestration/multi-agent-runs/#retrieving-conversations-and-artifacts). * **[Agent notifications](/agent-platform/capabilities/agent-notifications/)** - in-app notifications fire on the parent agent's conversation only. Use the pill bar or the **Sub-agents** tab to drill into a specific child. ## Related pages -* [Running orchestrated agents](/agent-platform/cloud-agents/orchestration/multi-agent-runs/) - how to start an orchestrated run from the CLI, slash command, web app, or API. +* [Running orchestrated agents](/platform/orchestration/multi-agent-runs/) - how to start an orchestrated run from the CLI, slash command, web app, or API. * [How to run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/) - practical guidance for splitting tasks, assigning worktrees, validating child output, and handing work off for review. * [Oz API and SDK](/reference/api-and-sdk/) - REST endpoints for runs, conversations, and artifacts. -* [Cloud agents overview](/agent-platform/cloud-agents/overview/) - what a cloud agent run is and how it fits into the Oz Platform. -* [Deployment patterns](/agent-platform/cloud-agents/deployment-patterns/) - higher-level deployment models that orchestration composes with. +* [Cloud agents overview](/platform/) - what a cloud agent run is and how it fits into the Oz Platform. +* [Deployment patterns](/platform/deployment-patterns/) - higher-level deployment models that orchestration composes with. diff --git a/src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx b/src/content/docs/platform/orchestration/multi-agent-runs.mdx similarity index 92% rename from src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx rename to src/content/docs/platform/orchestration/multi-agent-runs.mdx index e106b251a..469cc1150 100644 --- a/src/content/docs/agent-platform/cloud-agents/orchestration/multi-agent-runs.mdx +++ b/src/content/docs/platform/orchestration/multi-agent-runs.mdx @@ -19,7 +19,7 @@ Pick where the parent will run. Every orchestration starts with a single parent * **Parent in the Warp app** - use the `/orchestrate` or `/plan` slash command. This is the fastest way to try orchestration. * **Parent in the cloud** - trigger the parent through the Oz CLI (`oz agent run-cloud`), the [Oz API](/reference/api-and-sdk/), or any integration (Slack, Linear, schedule). The parent runs in an environment and spawns children from there. -Cloud parents that spawn cloud children need access to one or more [environments](/agent-platform/cloud-agents/environments/) the children can run in. +Cloud parents that spawn cloud children need access to one or more [environments](/platform/environments/) the children can run in. ## Starting an orchestrated run from Warp @@ -45,7 +45,7 @@ You can also reach the same approval flow from `/plan`. When you ask the agent t A local parent - a Warp Agent conversation in the Warp app - can spawn cloud children by specifying an environment for each child. The parent asks for the environment if it isn't already clear from context. You can select any environment from your account or team. -Cloud children inherit the parent's authentication; the same credit and credentials rules from the [Cloud agents overview](/agent-platform/cloud-agents/overview/) apply. +Cloud children inherit the parent's authentication; the same credit and credentials rules from the [Cloud agents overview](/platform/) apply. ## Starting an orchestrated run from the CLI @@ -76,7 +76,7 @@ The parent run starts and children appear in the Runs list as the parent spawns ## Starting an orchestrated run from the API -Spawn the parent with `POST /agent/runs`. Children can either be spawned by the parent agent at runtime, or you can spawn each child explicitly from your code and link it to the parent with `parent_run_id`. Once they're running, coordination between the parent and its children flows through Warp's durable agent-to-agent messaging - see [Messaging between agents](/agent-platform/cloud-agents/orchestration/#messaging-between-agents) for the model. +Spawn the parent with `POST /agent/runs`. Children can either be spawned by the parent agent at runtime, or you can spawn each child explicitly from your code and link it to the parent with `parent_run_id`. Once they're running, coordination between the parent and its children flows through Warp's durable agent-to-agent messaging - see [Messaging between agents](/platform/orchestration/#messaging-between-agents) for the model. ### Agent-driven orchestration @@ -188,9 +188,9 @@ Self-hosted, local, and GitHub Action runs cannot be cancelled through this endp ## Related pages -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) - parent/child model, run state transitions, and common patterns. +* [Multi-agent orchestration](/platform/orchestration/) - parent/child model, run state transitions, and common patterns. * [How to run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/) - practical task decomposition, worktree ownership, validation, and review handoff guidance. * [Oz CLI](/reference/cli/) - command reference for `oz agent run-cloud` and `oz run`. * [Oz API and SDK](/reference/api-and-sdk/) - full HTTP reference and typed SDKs. -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - how parent and child runs appear in the Agent Management Panel in the Warp app and the Runs page in the Oz web app. -* [Environments](/agent-platform/cloud-agents/environments/) - configure the runtime context cloud children execute in. +* [Managing cloud agents](/platform/managing-cloud-agents/) - how parent and child runs appear in the Agent Management Panel in the Warp app and the Runs page in the Oz web app. +* [Environments](/platform/environments/) - configure the runtime context cloud children execute in. diff --git a/src/content/docs/agent-platform/cloud-agents/platform.mdx b/src/content/docs/platform/overview.mdx similarity index 83% rename from src/content/docs/agent-platform/cloud-agents/platform.mdx rename to src/content/docs/platform/overview.mdx index fbb9dee09..fe714627f 100644 --- a/src/content/docs/agent-platform/cloud-agents/platform.mdx +++ b/src/content/docs/platform/overview.mdx @@ -8,12 +8,12 @@ sidebar: --- import VideoEmbed from '@components/VideoEmbed.astro'; -Cloud agents run on the **Oz Platform**. The platform gives you a consistent way to **trigger work**, **orchestrate and track tasks**, **execute agents** (in an optional [environment](/agent-platform/cloud-agents/environments/), on a host), and inspect outcomes with team visibility. First-party [integrations](/agent-platform/cloud-agents/integrations/) connect external events — like Slack messages, GitHub PRs, or CI failures — to cloud agents automatically. +Cloud agents run on the **Oz Platform**. The platform gives you a consistent way to **trigger work**, **orchestrate and track tasks**, **execute agents** (in an optional [environment](/platform/environments/), on a host), and inspect outcomes with team visibility. First-party [integrations](/platform/integrations/) connect external events — like Slack messages, GitHub PRs, or CI failures — to cloud agents automatically. <VideoEmbed url="https://youtu.be/poLkJhO7fdo" title="Oz Platform cloud agents overview video" /> :::note -**New to cloud agents?** Start with the [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) to run your first agent in ~10 minutes. +**New to cloud agents?** Start with the [Cloud agents quickstart](/platform/quickstart/) to run your first agent in ~10 minutes. ::: **Most production setups follow the same flow:** @@ -23,9 +23,9 @@ Cloud agents run on the **Oz Platform**. The platform gives you a consistent way 3. The agent executes on a **host**, optionally inside an environment, using the required configuration and credentials. 4. The task produces a **persistent record** (status, metadata, transcript, outputs) your team can review and manage. -![Oz Platform architecture showing Trigger, Agent, Environment, and Artifacts components](../../../../assets/agent-platform/most-flexible-platform-for-building-with-agents.png) +![Oz Platform architecture showing Trigger, Agent, Environment, and Artifacts components](../../../assets/agent-platform/most-flexible-platform-for-building-with-agents.png) -![Oz Platform detailed architecture showing components, triggers, orchestrator, and agent runners](../../../../assets/agent-platform/oz-diagram.png) +![Oz Platform detailed architecture showing components, triggers, orchestrator, and agent runners](../../../assets/agent-platform/oz-diagram.png) The sections below describe the Oz Platform primitives that power this flow, and how they compose. @@ -90,7 +90,7 @@ The orchestrator: * Tracks lifecycle state (created → running → completed/failed) and associated metadata. * Exposes task lifecycle operations via the [Oz CLI](/reference/cli/) and a [REST API](/reference/api-and-sdk/) (create tasks, query history, and inspect status/outputs). * Powers SDKs (TypeScript/Python) for programmatic usage on top of the orchestrator API. -* Supports [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) for parent/child workflows, fan-out, and review swarms. +* Supports [multi-agent orchestration](/platform/orchestration/) for parent/child workflows, fan-out, and review swarms. #### When teams use the API/SDK @@ -105,7 +105,7 @@ Teams typically use the API/SDK when: ### Environments -[Environments](/agent-platform/cloud-agents/environments/) define the execution context an agent should run in. +[Environments](/platform/environments/) define the execution context an agent should run in. **An Environment typically includes:** @@ -175,7 +175,7 @@ With Warp hosting: * Warp runs the environment on Warp-managed infrastructure. * This is the default model for teams that want the simplest setup and do not need execution to occur inside their network boundary. -* For more details, see [Warp-hosted execution](/agent-platform/cloud-agents/warp-hosting/). +* For more details, see [Warp-hosted execution](/platform/warp-hosting/). #### Self-hosted execution @@ -186,14 +186,14 @@ With self-hosting: * This is used when teams want code and execution to remain on their own systems rather than being cloned or executed in Warp's cloud. :::note -**Enterprise feature**: Self-hosted execution requires an Enterprise plan. See [Self-hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions. +**Enterprise feature**: Self-hosted execution requires an Enterprise plan. See [Self-hosting](/platform/self-hosting/) for setup instructions. ::: --- ### Integrations -[Integrations](/agent-platform/cloud-agents/integrations/) connect external events to cloud agent tasks. When an event occurs in a third-party system, Warp creates a task with the relevant context and starts it automatically. +[Integrations](/platform/integrations/) connect external events to cloud agent tasks. When an event occurs in a third-party system, Warp creates a task with the relevant context and starts it automatically. Warp supports two integration models: @@ -208,12 +208,12 @@ First-party integrations can be configured with a simple setup flow (for example oz integration create … ``` -Warp registers webhooks with the third-party system, receives events, extracts context (payload, metadata, links, logs), and creates a task — optionally in an [Environment](/agent-platform/cloud-agents/environments/). +Warp registers webhooks with the third-party system, receives events, extracts context (payload, metadata, links, logs), and creates a task — optionally in an [Environment](/platform/environments/). Examples of context extracted by first-party integrations: -* [Slack](/agent-platform/cloud-agents/integrations/slack/): message text, channel, thread, and user identity -* [GitHub](/agent-platform/cloud-agents/integrations/github-actions/): PR metadata, diffs, labels, and check results +* [Slack](/platform/integrations/slack/): message text, channel, thread, and user identity +* [GitHub](/platform/integrations/github-actions/): PR metadata, diffs, labels, and check results * CI: logs, job metadata, and artifacts #### Custom integrations @@ -230,7 +230,7 @@ Custom integrations are a good fit when: ### Secrets -Cloud agents often need credentials to access external systems (APIs, cloud providers, databases, internal tools, MCP servers). Warp provides a [secrets store](/agent-platform/cloud-agents/secrets/) that can inject secrets at runtime so agents can use authenticated tools without exposing secret values in logs or UI. +Cloud agents often need credentials to access external systems (APIs, cloud providers, databases, internal tools, MCP servers). Warp provides a [secrets store](/platform/secrets/) that can inject secrets at runtime so agents can use authenticated tools without exposing secret values in logs or UI. #### What secrets are for @@ -258,7 +258,7 @@ While a task is executing, the agent reports progress and status back to Warp. A Warp provides multiple surfaces for observability: -* [Management UI](/agent-platform/cloud-agents/managing-cloud-agents/): lists tasks, status, timing, metadata, and history. +* [Management UI](/platform/managing-cloud-agents/): lists tasks, status, timing, metadata, and history. * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/): authorized teammates can attach to a running task to monitor and, where supported, steer it. * [APIs](/reference/api-and-sdk/) and SDKs: query task history, build monitoring, and generate reports. @@ -273,11 +273,11 @@ Warp provides multiple surfaces for observability: Cloud agent setups often include shared configuration such as: -* [MCP Servers](/agent-platform/cloud-agents/mcp/) +* [MCP Servers](/platform/mcp/) * [rules / guardrails](/agent-platform/capabilities/rules/) * [saved prompts](/knowledge-and-collaboration/warp-drive/prompts/) * [environment variables](/knowledge-and-collaboration/warp-drive/environment-variables/) -* [secrets](/agent-platform/cloud-agents/secrets/) +* [secrets](/platform/secrets/) Warp supports centralized configuration so these settings apply consistently regardless of where a task is launched. @@ -285,12 +285,12 @@ This is especially useful when the same workflow can be triggered from multiple ### Using the Oz Platform with or without the Warp app -[Cloud agents](/agent-platform/cloud-agents/overview/) do not require Warp's desktop terminal. Teams can operate cloud agent workflows using: +[Cloud agents](/platform/) do not require Warp's desktop terminal. Teams can operate cloud agent workflows using: * [Oz CLI](/reference/cli/) — run agents from scripts, CI, or the terminal -* [Oz web app](/agent-platform/cloud-agents/oz-web-app/) — visual interface for managing runs, schedules, environments, and integrations from any browser, including mobile +* [Oz web app](/platform/oz-web-app/) — visual interface for managing runs, schedules, environments, and integrations from any browser, including mobile * [Session sharing](/agent-platform/local-agents/session-sharing/) — attach to running tasks to monitor or steer -* [Management UI](/agent-platform/cloud-agents/managing-cloud-agents/) — view agent activity and run history +* [Management UI](/platform/managing-cloud-agents/) — view agent activity and run history * [APIs and SDKs](/reference/api-and-sdk/) — programmatic access for custom integrations **If your team also uses Warp’s terminal, you gain an additional workflow:** diff --git a/src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx b/src/content/docs/platform/oz-web-app.mdx similarity index 84% rename from src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx rename to src/content/docs/platform/oz-web-app.mdx index 0a56cc7e1..26a4235b9 100644 --- a/src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx +++ b/src/content/docs/platform/oz-web-app.mdx @@ -22,7 +22,7 @@ Watch this short demo to create an environment and run an agent using the Oz web <table><thead><tr><th width="150">Page</th><th width="120">Path</th><th>What you can do</th></tr></thead><tbody><tr><td><strong>Runs</strong></td><td><code>/runs</code></td><td>View all runs, filter by status/source/creator, start new runs, inspect transcripts</td></tr><tr><td><strong>Agents</strong></td><td><code>/agents</code></td><td>Browse saved agents, create agents, configure defaults, and start runs</td></tr><tr><td><strong>Skills</strong></td><td><code>/skills</code></td><td>Browse skills from your environments, view suggested skills, create skills for agents, and start runs</td></tr><tr><td><strong>Schedules</strong></td><td><code>/schedules</code></td><td>Create scheduled agents, pause/enable schedules, view run history</td></tr><tr><td><strong>Environments</strong></td><td><code>/environments</code></td><td>Create and manage environments with repos, Docker images, and setup commands</td></tr><tr><td><strong>Secrets</strong></td><td><code>/secrets</code></td><td>Create and manage Warp-managed secrets for cloud agent runs</td></tr><tr><td><strong>Integrations</strong></td><td><code>/integrations</code></td><td>Connect Slack and Linear to trigger agents from external tools</td></tr></tbody></table> <figure style={{ maxWidth: "563px" }}> -![The Oz web app's Runs page.](../../../../assets/agent-platform/oz-web-app-runs-view.png) +![The Oz web app's Runs page.](../../../assets/agent-platform/oz-web-app-runs-view.png) <figcaption>The Oz web app Runs page.</figcaption> </figure> @@ -47,7 +47,7 @@ The onboarding asks "What brings you to Oz?" and offers three paths: * **Create an agent automation** — Walks you through setting up a scheduled agent, integration-triggered agent, or other automation * **Run Cloud Agents in Warp** — Opens the Warp app (or takes you to the download page) to run cloud agents interactively -* **Build an app that uses agents** — Links to the [Oz Platform](/agent-platform/cloud-agents/platform/) docs for using the CLI, SDK, or API +* **Build an app that uses agents** — Links to the [Oz Platform](/platform/overview/) docs for using the CLI, SDK, or API You can skip onboarding at any time to go directly to the Runs page. @@ -82,7 +82,7 @@ To start a new run: ### Inspecting orchestrated runs -The Oz web app renders [multi-agent orchestrations](/agent-platform/cloud-agents/orchestration/) as nested rows on the **Runs** page, so you can follow parent and child execution together. +The Oz web app renders [multi-agent orchestrations](/platform/orchestration/) as nested rows on the **Runs** page, so you can follow parent and child execution together. Open a parent run from the Runs page. When the run has children, the detail pane adds a **Sub-agents** tab next to **Details**: @@ -93,12 +93,12 @@ Open a parent run from the Runs page. When the run has children, the detail pane The **Agents** page (`/agents`) is where you browse, create, and run saved agents. Agents are reusable cloud agent configurations that can include a prompt, skills, harness, model, environment, and secrets. -Skills are reusable instruction sets stored in repositories. You can attach existing skills to an agent through the **Skills** field; for more details, see [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/). +Skills are reusable instruction sets stored in repositories. You can attach existing skills to an agent through the **Skills** field; for more details, see [Skills as Agents](/platform/skills-as-agents/). -Saved agents use Warp's team-scoped identity model, which lets a reusable agent own runs and carry default configuration for teammates. You manage saved agents from the Agents page. For plan limits, API endpoints, and API key binding behavior, see [Agents](/agent-platform/cloud-agents/agents/). +Saved agents use Warp's team-scoped identity model, which lets a reusable agent own runs and carry default configuration for teammates. You manage saved agents from the Agents page. For plan limits, API endpoints, and API key binding behavior, see [Agents](/platform/agents/). <figure style={{ maxWidth: "563px" }}> -![The Agents page in the Oz web app.](../../../../assets/agent-platform/oz-web-app-agents.png) +![The Agents page in the Oz web app.](../../../assets/agent-platform/oz-web-app-agents.png) <figcaption>The Agents page in the Oz web app.</figcaption> </figure> @@ -116,10 +116,10 @@ To create a saved agent: 2. Define the instructions and defaults. Add a name, description, prompt, optional skills, harness, model, environment, and secrets. 3. Click **Create agent**. The saved agent appears on the Agents page and is available for runs. -For deeper guidance on reusable skills and team-scoped identities, see [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) and [Agents](/agent-platform/cloud-agents/agents/). +For deeper guidance on reusable skills and team-scoped identities, see [Skills as Agents](/platform/skills-as-agents/) and [Agents](/platform/agents/). <figure style={{ maxWidth: "563px" }}> -![Creating a new agent in the Oz web app.](../../../../assets/agent-platform/oz-web-app-new-agent.png) +![Creating a new agent in the Oz web app.](../../../assets/agent-platform/oz-web-app-new-agent.png) <figcaption>Creating a new agent in the Oz web app.</figcaption> </figure> @@ -143,7 +143,7 @@ To create a skill for agents: 4. Click **Open Skill PR** to create a pull request that adds the skill to the selected repository. <figure style={{ maxWidth: "563px" }}> -![Creating a skill for agents in the Oz web app.](../../../../assets/agent-platform/oz-web-app-new-skill.png) +![Creating a skill for agents in the Oz web app.](../../../assets/agent-platform/oz-web-app-new-skill.png) <figcaption>Creating a skill in the Oz web app.</figcaption> </figure> @@ -160,7 +160,7 @@ Each schedule displays: <table><thead><tr><th width="150">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>A descriptive name for the scheduled task</td></tr><tr><td><strong>Frequency</strong></td><td>Human-readable description of the cron schedule (e.g., "Every Monday at 10am")</td></tr><tr><td><strong>Next run</strong></td><td>When the schedule will next execute</td></tr><tr><td><strong>Environment</strong></td><td>Which environment the scheduled agent runs in</td></tr><tr><td><strong>Agent</strong></td><td>Which saved agent the schedule uses (if any)</td></tr><tr><td><strong>Status</strong></td><td>Whether the schedule is active or paused</td></tr></tbody></table> <figure style={{ maxWidth: "563px" }}> -![The Schedules page in the Oz web app.](../../../../assets/agent-platform/oz-web-app-schedules.png) +![The Schedules page in the Oz web app.](../../../assets/agent-platform/oz-web-app-schedules.png) <figcaption>The Schedules page in the Oz web app.</figcaption> </figure> @@ -186,7 +186,7 @@ Click any schedule to view its details and recent run history. From the detail p * **View past runs** triggered by this schedule :::note -For CLI-based schedule management, see [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). +For CLI-based schedule management, see [Scheduled Agents](/platform/triggers/scheduled-agents/). ::: ## Environments @@ -200,7 +200,7 @@ Each environment displays: <table><thead><tr><th width="170">Field</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The environment's identifier</td></tr><tr><td><strong>Docker image</strong></td><td>The container image used for execution</td></tr><tr><td><strong>Repositories</strong></td><td>Which repos the agent can access</td></tr><tr><td><strong>Setup commands</strong></td><td>Commands run before the agent starts</td></tr></tbody></table> <figure style={{ maxWidth: "563px" }}> -![The Environments page in the Oz web app.](../../../../assets/agent-platform/oz-web-app-environments.png) +![The Environments page in the Oz web app.](../../../assets/agent-platform/oz-web-app-environments.png) <figcaption>The Environments page in the Oz web app.</figcaption> </figure> @@ -216,7 +216,7 @@ To create a new environment: 6. Click **Create environment**. The environment appears on the Environments page. :::note -For advanced environment configuration, see [Environments](/agent-platform/cloud-agents/environments/) and the [CLI reference](/reference/cli/integration-setup/). +For advanced environment configuration, see [Environments](/platform/environments/) and the [CLI reference](/reference/cli/integration-setup/). ::: ## Integrations @@ -228,7 +228,7 @@ The **Integrations** page (`/integrations`) lets you configure first-party integ <table><thead><tr><th width="120">Integration</th><th>Description</th></tr></thead><tbody><tr><td><strong>Slack</strong></td><td>Tag @Oz in messages or threads to trigger agents directly from Slack conversations</td></tr><tr><td><strong>Linear</strong></td><td>Tag @Oz on issues to trigger agents from your issue tracker</td></tr></tbody></table> <figure style={{ maxWidth: "563px" }}> -![The Integrations page in the Oz web app.](../../../../assets/agent-platform/oz-web-app-integrations.png) +![The Integrations page in the Oz web app.](../../../assets/agent-platform/oz-web-app-integrations.png) <figcaption>The Integrations page in the Oz web app.</figcaption> </figure> @@ -237,16 +237,16 @@ The **Integrations** page (`/integrations`) lets you configure first-party integ Click an integration to start the guided setup flow. You'll authorize Warp to connect with the external service, select an environment, and configure any integration-specific settings. :::note -For detailed integration setup instructions, see [Slack](/agent-platform/cloud-agents/integrations/slack/) and [Linear](/agent-platform/cloud-agents/integrations/linear/). +For detailed integration setup instructions, see [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/). ::: ## Related resources -* [Cloud Agents overview](/agent-platform/cloud-agents/overview/) — Learn about cloud agents and when to use them -* [Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) — Parent/child model and common orchestration patterns -* [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) — Run agents based on reusable skill definitions -* [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) — Run agents automatically on a cron schedule -* [Environments](/agent-platform/cloud-agents/environments/) — Configure runtime context for cloud agents -* [Managing Cloud Agents](/agent-platform/cloud-agents/managing-cloud-agents/) — Monitor agent activity and inspect runs +* [Cloud Agents overview](/platform/) — Learn about cloud agents and when to use them +* [Multi-agent orchestration](/platform/orchestration/) — Parent/child model and common orchestration patterns +* [Skills as Agents](/platform/skills-as-agents/) — Run agents based on reusable skill definitions +* [Scheduled Agents](/platform/triggers/scheduled-agents/) — Run agents automatically on a cron schedule +* [Environments](/platform/environments/) — Configure runtime context for cloud agents +* [Managing Cloud Agents](/platform/managing-cloud-agents/) — Monitor agent activity and inspect runs * [Oz CLI](/reference/cli/) — Command-line interface for running agents * [Oz API & SDK](/reference/api-and-sdk/) — Programmatic access to cloud agents diff --git a/src/content/docs/agent-platform/cloud-agents/quickstart.mdx b/src/content/docs/platform/quickstart.mdx similarity index 79% rename from src/content/docs/agent-platform/cloud-agents/quickstart.mdx rename to src/content/docs/platform/quickstart.mdx index 1676d1b95..4947762e3 100644 --- a/src/content/docs/agent-platform/cloud-agents/quickstart.mdx +++ b/src/content/docs/platform/quickstart.mdx @@ -85,7 +85,7 @@ You can view details of your agent's run, including commands executed, files cha * In the Warp app, open the [conversations panel](/agent-platform/local-agents/interacting-with-agents/#conversation-panel) to see all your agent runs. * Click the session link in your terminal output. * Go to the [Oz web app](https://oz.warp.dev) and navigate to the **Runs** tab. -* Access from mobile via the [Oz web app](/agent-platform/cloud-agents/oz-web-app/). +* Access from mobile via the [Oz web app](/platform/oz-web-app/). **Breaking it down:** Every cloud agent run is auto-tracked. You get a shareable link, a run record, and full visibility into what the agent did. You or your teammates can watch the agent's progress in real-time and even steer it if needed. The run record persists after completion so you can review it later. @@ -99,7 +99,7 @@ Turn your successful run into a skill that you can reuse: Follow the prompts to save your task definition. Once created, you can run it again, schedule it, trigger it from Slack/Linear, or share it with your team. -**How this works:** Skills capture successful agent workflows as reusable building blocks. Instead of typing the same prompt repeatedly, you define it once. You can use it yourself, share it with teammates, schedule it to run automatically, or trigger it from integrations. Learn more about [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/). +**How this works:** Skills capture successful agent workflows as reusable building blocks. Instead of typing the same prompt repeatedly, you define it once. You can use it yourself, share it with teammates, schedule it to run automatically, or trigger it from integrations. Learn more about [Skills as Agents](/platform/skills-as-agents/). **Prefer using the CLI?** See the [Oz CLI quickstart](/reference/cli/quickstart/) for CLI-based workflows. @@ -120,7 +120,7 @@ Now that you've run your first cloud agent, here are some next steps: ### Automate recurring tasks -[Schedule agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) to run on cron schedules for maintenance tasks like weekly dependency checks or daily dead code cleanup. +[Schedule agents](/platform/triggers/scheduled-agents/) to run on cron schedules for maintenance tasks like weekly dependency checks or daily dead code cleanup. ```bash oz schedule create \ @@ -132,11 +132,11 @@ oz schedule create \ ### Trigger agents from integrations -**Slack integration** - Tag @Oz in any Slack channel to get immediate help with code reviews, debugging, or incident response. Your team can discuss problems in Slack while Oz analyzes code, opens PRs, or investigates issues in the background. Results post directly back to the thread. See [Slack integration setup](/agent-platform/cloud-agents/integrations/slack/). +**Slack integration** - Tag @Oz in any Slack channel to get immediate help with code reviews, debugging, or incident response. Your team can discuss problems in Slack while Oz analyzes code, opens PRs, or investigates issues in the background. Results post directly back to the thread. See [Slack integration setup](/platform/integrations/slack/). -**Linear integration** - Connect Oz to Linear to automate bug triage and fixes. Tag @Oz on an issue to reproduce the bug, identify root causes, and open a PR with a fix—closing the loop from bug report to resolution without leaving Linear. See [Linear integration setup](/agent-platform/cloud-agents/integrations/linear/). +**Linear integration** - Connect Oz to Linear to automate bug triage and fixes. Tag @Oz on an issue to reproduce the bug, identify root causes, and open a PR with a fix—closing the loop from bug report to resolution without leaving Linear. See [Linear integration setup](/platform/integrations/linear/). -**GitHub Actions** - Run agents in CI/CD pipelines to automate tasks like generating release notes, running security audits, or validating migrations. Trigger agents on PRs, commits, or releases to keep workflows moving without manual intervention. See [GitHub Actions integration setup](/agent-platform/cloud-agents/integrations/github-actions/). +**GitHub Actions** - Run agents in CI/CD pipelines to automate tasks like generating release notes, running security audits, or validating migrations. Trigger agents on PRs, commits, or releases to keep workflows moving without manual intervention. See [GitHub Actions integration setup](/platform/integrations/github-actions/). :::note Integrations require a team on Build, Max, or Business plan. @@ -151,19 +151,19 @@ Use the [Oz API & SDK](/reference/api-and-sdk/) to trigger agents programmatical ## Troubleshooting **Environment creation fails**\ -Use official Docker Hub images like `node`, `python`, or `rust` for best compatibility. Ensure your GitHub repos are accessible. If using a custom image, avoid Alpine/musl-based images—the agent runtime requires glibc. See [Environments](/agent-platform/cloud-agents/environments/) for more guidance on choosing Docker images and [`environment_setup_failed`](/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed/) for the related API error. +Use official Docker Hub images like `node`, `python`, or `rust` for best compatibility. Ensure your GitHub repos are accessible. If using a custom image, avoid Alpine/musl-based images—the agent runtime requires glibc. See [Environments](/platform/environments/) for more guidance on choosing Docker images and [`environment_setup_failed`](/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed/) for the related API error. **Agent can't access repos**\ -Warp prompts you to authorize GitHub when you create an environment or trigger your first agent. If authorization fails or needs updating, see [How GitHub Authorization works](/reference/cli/integration-setup/#how-github-authorization-works) and [`external_authentication_required`](/reference/api-and-sdk/troubleshooting/errors/external-authentication-required/). For automated workflows using an agent API key, make sure [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) is configured in the Admin Panel. Also verify that repos are correctly configured in your environment with `oz environment get <ENV_ID>`; permission mismatches can surface as [`not_authorized`](/reference/api-and-sdk/troubleshooting/errors/not-authorized/). +Warp prompts you to authorize GitHub when you create an environment or trigger your first agent. If authorization fails or needs updating, see [How GitHub Authorization works](/reference/cli/integration-setup/#how-github-authorization-works) and [`external_authentication_required`](/reference/api-and-sdk/troubleshooting/errors/external-authentication-required/). For automated workflows using an agent API key, make sure [team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization) is configured in the Admin Panel. Also verify that repos are correctly configured in your environment with `oz environment get <ENV_ID>`; permission mismatches can surface as [`not_authorized`](/reference/api-and-sdk/troubleshooting/errors/not-authorized/). **Not enough credits to run cloud agents**\ -Your team needs at least 20 credits available. Check your credit balance in Settings or see [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) for details on credit requirements and which plans support cloud agents. If a run is blocked because the billed principal has no remaining credits, see [`insufficient_credits`](/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/). +Your team needs at least 20 credits available. Check your credit balance in Settings or see [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) for details on credit requirements and which plans support cloud agents. If a run is blocked because the billed principal has no remaining credits, see [`insufficient_credits`](/reference/api-and-sdk/troubleshooting/errors/insufficient-credits/). **More resources** -* [Environments deep dive](/agent-platform/cloud-agents/environments/) -* [Cloud Agents FAQs](/agent-platform/cloud-agents/faqs/) -* [Managing Cloud Agents](/agent-platform/cloud-agents/managing-cloud-agents/) +* [Environments deep dive](/platform/environments/) +* [Cloud Agents FAQs](/platform/faqs/) +* [Managing Cloud Agents](/platform/managing-cloud-agents/) --- @@ -171,6 +171,6 @@ Your team needs at least 20 credits available. Check your credit balance in Sett Now that you've run your first cloud agent, automate recurring work or connect agents to your team's tools. -* **[Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/)** - Set up an agent to run on a cron schedule for recurring tasks like weekly dependency checks. -* **[Integrations quickstart](/agent-platform/cloud-agents/integrations/quickstart/)** - Connect Oz to Slack and Linear so your team can trigger agents from mentions and issues. +* **[Scheduled Agents quickstart](/platform/triggers/scheduled-agents-quickstart/)** - Set up an agent to run on a cron schedule for recurring tasks like weekly dependency checks. +* **[Integrations quickstart](/platform/integrations/quickstart/)** - Connect Oz to Slack and Linear so your team can trigger agents from mentions and issues. * **[Skills](/agent-platform/capabilities/skills/)** - Turn successful agent workflows into reusable instructions you can schedule, trigger, or share. diff --git a/src/content/docs/agent-platform/cloud-agents/secrets.mdx b/src/content/docs/platform/secrets.mdx similarity index 84% rename from src/content/docs/agent-platform/cloud-agents/secrets.mdx rename to src/content/docs/platform/secrets.mdx index e9d3b8a81..76bf48a56 100644 --- a/src/content/docs/agent-platform/cloud-agents/secrets.mdx +++ b/src/content/docs/platform/secrets.mdx @@ -9,12 +9,12 @@ description: >- Cloud agents often need to interact with external systems such as APIs, databases, cloud providers, or internal tooling. To do this safely, Warp provides Warp-managed **agent secrets**, a secure way to store, scope, and inject credentials into cloud agent runs without exposing secret values to users or logs. -Warp-managed secrets are designed to work across [cloud agent](/agent-platform/cloud-agents/overview/) and [integration](/agent-platform/cloud-agents/integrations/) triggers (CLI, Slack, Linear, and schedules), support both team-wide and personal credentials, and give engineering and security teams visibility into what agents can access. +Warp-managed secrets are designed to work across [cloud agent](/platform/) and [integration](/platform/integrations/) triggers (CLI, Slack, Linear, and schedules), support both team-wide and personal credentials, and give engineering and security teams visibility into what agents can access. **Warp-managed secrets are useful when:** * A cloud agent needs to call an API or CLI that does not support OAuth -* You are using [MCP servers](/agent-platform/cloud-agents/mcp/) that expect static tokens or keys +* You are using [MCP servers](/platform/mcp/) that expect static tokens or keys * An agent needs credentials for tools like cloud CLIs, databases, monitoring systems, or internal services * You want centralized auditing and control over what credentials agents can access @@ -57,7 +57,7 @@ Team secrets are shared across the entire team and are available to all cloud ag * Ideal for shared infrastructure credentials, service accounts, and read-only API keys :::note -Because team secrets are broadly available and may be used by fully automated or scheduled agents, they should generally be created **using bot or service accounts**, rather than credentials tied to an individual person. When you want a credential to be available to one workflow only, attach it to a [cloud agent](/agent-platform/cloud-agents/agents/) instead of giving every run access to it. +Because team secrets are broadly available and may be used by fully automated or scheduled agents, they should generally be created **using bot or service accounts**, rather than credentials tied to an individual person. When you want a credential to be available to one workflow only, attach it to a [cloud agent](/platform/agents/) instead of giving every run access to it. ::: **For example:** @@ -69,7 +69,7 @@ Because team secrets are broadly available and may be used by fully automated or This ensures credentials remain valid as team membership changes, permissions are tightly scoped, and ownership and rotation align with internal security policies. :::note -Team secrets can also be attached directly to a [cloud agent](/agent-platform/cloud-agents/agents/), so only runs executing as that cloud agent receive them. The secret itself still lives in the team's secret scope; the cloud agent only references it by name. +Team secrets can also be attached directly to a [cloud agent](/platform/agents/), so only runs executing as that cloud agent receive them. The secret itself still lives in the team's secret scope; the cloud agent only references it by name. ::: #### Personal secrets @@ -84,7 +84,7 @@ Personal secrets belong to an **individual user**. ## Creating secrets in the Oz web app -The [Oz web app](/agent-platform/cloud-agents/oz-web-app/) provides a guided side pane for creating Warp-managed secrets. Use it when you want a point-and-click flow without leaving the browser; the CLI flow below remains available for scripting and automation. +The [Oz web app](/platform/oz-web-app/) provides a guided side pane for creating Warp-managed secrets. Use it when you want a point-and-click flow without leaving the browser; the CLI flow below remains available for scripting and automation. To create a secret in the web app: @@ -234,8 +234,8 @@ It **does not receive personal secrets** belonging to other team members. When an agent is triggered without a user context, such as: -* [Scheduled (cron) agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) -* Fully automated [integrations](/agent-platform/cloud-agents/integrations/) +* [Scheduled (cron) agents](/platform/triggers/scheduled-agents/) +* Fully automated [integrations](/platform/integrations/) The agent receives: @@ -249,15 +249,15 @@ Personal secrets are never injected in these cases. ## Scoping secrets to environments and runs -Owner scoping (team versus personal) controls **which secrets exist** for a caller. Two additional layers — environments and individual runs — let you narrow **which of those secrets are actually injected** for a given execution. Together with [cloud agents](/agent-platform/cloud-agents/agents/), these layers form a broader access-scoping model where each layer contributes the secrets a run ends up with at execution time. +Owner scoping (team versus personal) controls **which secrets exist** for a caller. Two additional layers — environments and individual runs — let you narrow **which of those secrets are actually injected** for a given execution. Together with [cloud agents](/platform/agents/), these layers form a broader access-scoping model where each layer contributes the secrets a run ends up with at execution time. ### Environment-level scoping -A [cloud environment](/agent-platform/cloud-agents/environments/) can declare its own list of secrets. When a run uses that environment, the environment's attached secrets are added to the run's allowlist by default. The run can still narrow the allowlist further by passing its own `secrets` list, which then takes precedence. Use this when a workflow's runtime needs a known, fixed set of credentials — for example, an `ops-tools` environment that only needs `DEPLOY_TOKEN` and `PAGERDUTY_API_KEY`. +A [cloud environment](/platform/environments/) can declare its own list of secrets. When a run uses that environment, the environment's attached secrets are added to the run's allowlist by default. The run can still narrow the allowlist further by passing its own `secrets` list, which then takes precedence. Use this when a workflow's runtime needs a known, fixed set of credentials — for example, an `ops-tools` environment that only needs `DEPLOY_TOKEN` and `PAGERDUTY_API_KEY`. #### Attach secrets to an environment -Use the environment form in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) to attach secrets to an environment: +Use the environment form in the [Oz web app](/platform/oz-web-app/) to attach secrets to an environment: 1. In the Oz web app (oz.warp.dev), open the **Environments** page. 2. Click an existing environment to edit it, or click **New environment** to create one. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx b/src/content/docs/platform/self-hosting/index.mdx similarity index 63% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx rename to src/content/docs/platform/self-hosting/index.mdx index 96b204963..34a4714a4 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx +++ b/src/content/docs/platform/self-hosting/index.mdx @@ -8,9 +8,9 @@ description: >- Self-hosting lets your team run cloud agent workloads on your own infrastructure instead of Warp-managed servers. You control the execution environment, compute resources, and network access. Repository clones, source files, build artifacts, runtime secrets, and agent execution workspaces stay on your infrastructure, and agents can reach services behind your VPN or firewall. -**New to self-hosting?** Start with the [Self-hosting quickstart](/agent-platform/cloud-agents/self-hosting/quickstart/) to get a managed worker running on Docker in under 10 minutes. +**New to self-hosting?** Start with the [Self-hosting quickstart](/platform/self-hosting/quickstart/) to get a managed worker running on Docker in under 10 minutes. -**Want a CLI-only path with no Docker requirement?** Jump straight to the [Unmanaged quickstart](/agent-platform/cloud-agents/self-hosting/unmanaged/#unmanaged-quickstart) to run `oz agent run` directly on any host. +**Want a CLI-only path with no Docker requirement?** Jump straight to the [Unmanaged quickstart](/platform/self-hosting/unmanaged/#unmanaged-quickstart) to run `oz agent run` directly on any host. :::note **Enterprise feature**: Self-hosted agents are available exclusively to teams on an Enterprise plan. To enable self-hosting for your team, [contact sales](https://www.warp.dev/contact-sales). @@ -31,7 +31,7 @@ Self-hosting has two architectures. The core distinction is **who orchestrates a | **What runs on your infra** | Long-lived `oz-agent-worker` daemon | One-shot `oz agent run` invocations | | **OS support** | Linux (macOS/Windows coming) | Linux, macOS, Windows | | **Execution isolation** | Docker container, Kubernetes Job, or direct host | Whatever your host provides | -| **Automatic environment setup** | Yes (via Warp [environments](/agent-platform/cloud-agents/environments/)) | No (you manage it) | +| **Automatic environment setup** | Yes (via Warp [environments](/platform/environments/)) | No (you manage it) | | **Session tracking and steering** | Yes | Yes | The two architectures are not mutually exclusive. Some teams run managed workers for integration-triggered work and unmanaged agents in CI pipelines. @@ -40,9 +40,9 @@ The two architectures are not mutually exclusive. Some teams run managed workers Warp uses a split-plane architecture: **execution happens on your infrastructure**, while **orchestration, session management, and LLM inference route through Warp's backend**. Agent interactions — including code context in session transcripts and LLM prompts — transit Warp's control plane under [Zero Data Retention (ZDR)](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr) agreements. Warp does not persistently store your source code or train on it. -If your security requirement is "repository clones and execution must stay on our infrastructure," self-hosting is designed for that. If your requirement is "no code context can ever route through Warp or an external LLM provider," review [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) with your Warp account team before deploying. +If your security requirement is "repository clones and execution must stay on our infrastructure," self-hosting is designed for that. If your requirement is "no code context can ever route through Warp or an external LLM provider," review [Security and networking](/platform/self-hosting/security-and-networking/) with your Warp account team before deploying. -![Self-hosted Oz architecture showing customer-managed execution with Oz orchestration](../../../../../assets/agent-platform/customer-dedicated-saas.png) +![Self-hosted Oz architecture showing customer-managed execution with Oz orchestration](../../../../assets/agent-platform/customer-dedicated-saas.png) With any self-hosted architecture: @@ -59,23 +59,23 @@ Enterprise teams that need full control over LLM inference routing can use [Brin ## Choosing an architecture :::caution -**OS support:** The managed architecture is **Linux-only** today (macOS and Windows support is coming). If you need agents to run on macOS or Windows, use the [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) architecture, which works on any platform Warp supports. +**OS support:** The managed architecture is **Linux-only** today (macOS and Windows support is coming). If you need agents to run on macOS or Windows, use the [unmanaged](/platform/self-hosting/unmanaged/) architecture, which works on any platform Warp supports. ::: Use these questions to decide between managed and unmanaged: 1. **Do you need agents to run on Windows or macOS?** - * Yes → Use the [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) architecture. Managed is Linux-only today. + * Yes → Use the [unmanaged](/platform/self-hosting/unmanaged/) architecture. Managed is Linux-only today. * No, Linux works → Continue to the next question. 2. **Do you want Oz to handle starting and stopping agents** (from Slack, the web interface, the Warp app, schedules, or the API)? * Yes → Use the [managed](#managed-architecture) architecture. - * No, you have your own triggering mechanism → Use the [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) architecture. + * No, you have your own triggering mechanism → Use the [unmanaged](/platform/self-hosting/unmanaged/) architecture. 3. **Can your development environment run in a Docker container or Kubernetes pod?** - * Yes, Docker → [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) backend. - * Yes, Kubernetes → [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) backend. - * No (multi-service stacks that don't fit a single container, or environments where container runtimes aren't available) → [Unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) or [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/). + * Yes, Docker → [Managed: Docker](/platform/self-hosting/managed-docker/) backend. + * Yes, Kubernetes → [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/) backend. + * No (multi-service stacks that don't fit a single container, or environments where container runtimes aren't available) → [Unmanaged](/platform/self-hosting/unmanaged/) or [Managed: Direct](/platform/self-hosting/managed-direct/). 4. **Do you have your own orchestrator** (CI/CD, Kubernetes, internal job scheduler) **that starts agents on demand?** - * Yes → [Unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/), using `oz agent run` as a drop-in. + * Yes → [Unmanaged](/platform/self-hosting/unmanaged/), using `oz agent run` as a drop-in. * No → [Managed](#managed-architecture). ### Choosing a managed backend @@ -83,17 +83,17 @@ Use these questions to decide between managed and unmanaged: The managed architecture supports three backends for task execution: 1. **Are you deploying the worker into a Kubernetes cluster?** - * Yes → Use the [Kubernetes backend](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/). Each task runs as a Kubernetes Job in your cluster; install with the included Helm chart. + * Yes → Use the [Kubernetes backend](/platform/self-hosting/managed-kubernetes/). Each task runs as a Kubernetes Job in your cluster; install with the included Helm chart. * No → Continue. 2. **Is Docker available on your worker host?** - * Yes → Use the [Docker backend](/agent-platform/cloud-agents/self-hosting/managed-docker/) (default). Tasks run in isolated containers. - * No → Use the [Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/). Tasks run directly on the host. + * Yes → Use the [Docker backend](/platform/self-hosting/managed-docker/) (default). Tasks run in isolated containers. + * No → Use the [Direct backend](/platform/self-hosting/managed-direct/). Tasks run directly on the host. 3. **Do you need container-level isolation between tasks?** - * Yes → [Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) or [Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) backend. + * Yes → [Docker](/platform/self-hosting/managed-docker/) or [Kubernetes](/platform/self-hosting/managed-kubernetes/) backend. * No → Any backend works. 4. **Do you need Kubernetes-native scheduling, resource management, or policy enforcement?** - * Yes → [Kubernetes backend](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/). - * No → [Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) or [Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/) is simpler to set up. + * Yes → [Kubernetes backend](/platform/self-hosting/managed-kubernetes/). + * No → [Docker](/platform/self-hosting/managed-docker/) or [Direct](/platform/self-hosting/managed-direct/) is simpler to set up. --- @@ -101,15 +101,15 @@ The managed architecture supports three backends for task execution: With the managed architecture, you run the `oz-agent-worker` daemon on your infrastructure. The daemon connects to Oz's backend, waits for tasks to be assigned to it, and executes those tasks on its host using one of three backends: -* **[Docker backend](/agent-platform/cloud-agents/self-hosting/managed-docker/)** (default) — Runs each task in an isolated Docker container. -* **[Kubernetes backend](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/)** — Runs each task as a Kubernetes Job in your cluster. -* **[Direct backend](/agent-platform/cloud-agents/self-hosting/managed-direct/)** — Runs each task directly on the host without a container runtime. +* **[Docker backend](/platform/self-hosting/managed-docker/)** (default) — Runs each task in an isolated Docker container. +* **[Kubernetes backend](/platform/self-hosting/managed-kubernetes/)** — Runs each task as a Kubernetes Job in your cluster. +* **[Direct backend](/platform/self-hosting/managed-direct/)** — Runs each task directly on the host without a container runtime. The managed architecture enables full orchestration by Oz — it can remotely start agents via Slack, Linear, the [Oz web app](https://oz.warp.dev), the API/SDK, and the `oz agent run-cloud` command. Agents can access host resources through volume mounts (Docker), Kubernetes-native configuration (Kubernetes), and injected environment variables. ## Unmanaged architecture -With the [unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/), you run `oz agent run` inside your own orchestrator or dev environment. This works on any platform Warp supports (Linux, macOS, Windows), with no dependency on Docker or any other sandboxing platform. +With the [unmanaged architecture](/platform/self-hosting/unmanaged/), you run `oz agent run` inside your own orchestrator or dev environment. This works on any platform Warp supports (Linux, macOS, Windows), with no dependency on Docker or any other sandboxing platform. You're responsible for executing `oz agent run` on your infrastructure — similar to how you'd integrate Claude Code or Codex CLI. The agent runs directly on the host, which could itself be a Kubernetes pod, VM, container, or CI runner. @@ -181,12 +181,12 @@ When creating a run, schedule, or integration in the [Oz web app](https://oz.war ## Environments with self-hosted workers -Self-hosted workers fully support [environments](/agent-platform/cloud-agents/environments/). When a task specifies an environment, the worker resolves the Docker image, clones the repositories, runs setup commands, and executes the agent inside the prepared container or Kubernetes Job. +Self-hosted workers fully support [environments](/platform/environments/). When a task specifies an environment, the worker resolves the Docker image, clones the repositories, runs setup commands, and executes the agent inside the prepared container or Kubernetes Job. -The same environment can be used for both Warp-hosted and self-hosted runs without modification. If your agents need custom tools, binaries, scripts, or system packages, add them to the environment's Docker image. See [Environments](/agent-platform/cloud-agents/environments/) for details on creating and configuring custom images. +The same environment can be used for both Warp-hosted and self-hosted runs without modification. If your agents need custom tools, binaries, scripts, or system packages, add them to the environment's Docker image. See [Environments](/platform/environments/) for details on creating and configuring custom images. :::note -With the Kubernetes backend, setting a [`default_image`](/agent-platform/cloud-agents/self-hosting/reference/#kubernetes-backend-config) on the worker lets you skip creating a Warp environment when all your tasks use the same base image. +With the Kubernetes backend, setting a [`default_image`](/platform/self-hosting/reference/#kubernetes-backend-config) on the worker lets you skip creating a Warp environment when all your tasks use the same base image. ::: :::caution @@ -201,21 +201,21 @@ Self-hosted runs have the same observability as Warp-hosted runs: * **Session sharing** — Authorized teammates can attach to running tasks to monitor progress. * **APIs and SDKs** — Query task history and build monitoring using the [Oz API](/reference/api-and-sdk/). -For infrastructure-level observability, the `oz-agent-worker` daemon can export OpenTelemetry metrics (worker health, task throughput, capacity saturation) to Prometheus, an OTLP collector, or the console. See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for setup, the full metric catalog, and sample PromQL queries. +For infrastructure-level observability, the `oz-agent-worker` daemon can export OpenTelemetry metrics (worker health, task throughput, capacity saturation) to Prometheus, an OTLP collector, or the console. See [Monitoring](/platform/self-hosting/monitoring/) for setup, the full metric catalog, and sample PromQL queries. --- ## Related pages -* [Self-hosting quickstart](/agent-platform/cloud-agents/self-hosting/quickstart/) — Get a managed worker running in ~10 minutes. -* [Unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) — Run `oz agent run` in your CI, K8s, or dev environment. -* [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) — Default managed setup with the Docker backend. -* [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) — Managed setup with the Kubernetes backend and Helm chart. -* [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/) — Managed setup with no container runtime. -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — CLI flags and config file schema. -* [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) — OpenTelemetry metrics for worker health, task throughput, and capacity. -* [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) — Data boundaries, network egress, and security considerations. -* [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/) — Worker won't start, tasks not picked up, and other common issues. -* [Deployment patterns](/agent-platform/cloud-agents/deployment-patterns/) — How self-hosting compares to CLI-only and Warp-hosted deployment. -* [Environments](/agent-platform/cloud-agents/environments/) — Define the runtime context for agent tasks. -* [Customizing workspace snapshots](/agent-platform/cloud-agents/handoff/snapshots/) — Configure end-of-run snapshots so handoff works when running outside the bundled cloud agent image. +* [Self-hosting quickstart](/platform/self-hosting/quickstart/) — Get a managed worker running in ~10 minutes. +* [Unmanaged](/platform/self-hosting/unmanaged/) — Run `oz agent run` in your CI, K8s, or dev environment. +* [Managed: Docker](/platform/self-hosting/managed-docker/) — Default managed setup with the Docker backend. +* [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/) — Managed setup with the Kubernetes backend and Helm chart. +* [Managed: Direct](/platform/self-hosting/managed-direct/) — Managed setup with no container runtime. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — CLI flags and config file schema. +* [Monitoring](/platform/self-hosting/monitoring/) — OpenTelemetry metrics for worker health, task throughput, and capacity. +* [Security and networking](/platform/self-hosting/security-and-networking/) — Data boundaries, network egress, and security considerations. +* [Troubleshooting](/platform/self-hosting/troubleshooting/) — Worker won't start, tasks not picked up, and other common issues. +* [Deployment patterns](/platform/deployment-patterns/) — How self-hosting compares to CLI-only and Warp-hosted deployment. +* [Environments](/platform/environments/) — Define the runtime context for agent tasks. +* [Customizing workspace snapshots](/platform/handoff/snapshots/) — Configure end-of-run snapshots so handoff works when running outside the bundled cloud agent image. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx b/src/content/docs/platform/self-hosting/managed-direct.mdx similarity index 77% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx rename to src/content/docs/platform/self-hosting/managed-direct.mdx index 6f7cfa1b3..e1b744e94 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-direct.mdx +++ b/src/content/docs/platform/self-hosting/managed-direct.mdx @@ -10,7 +10,7 @@ sidebar: Run the `oz-agent-worker` daemon with the **Direct backend** — tasks execute directly on the worker host without Docker or Kubernetes. Oz still orchestrates runs end to end (Slack, Linear, schedules, API, `oz agent run-cloud`); the worker just runs the agent in a per-task workspace on its own filesystem. :::note -This page covers the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture) with the Direct backend. For container-based task isolation, see [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) or [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/). For invocation-driven use cases, see [Unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/). +This page covers the [managed architecture](/platform/self-hosting/#managed-architecture) with the Direct backend. For container-based task isolation, see [Managed: Docker](/platform/self-hosting/managed-docker/) or [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/). For invocation-driven use cases, see [Unmanaged](/platform/self-hosting/unmanaged/). ::: ## When to use the Direct backend @@ -61,7 +61,7 @@ Pass `--backend direct`: oz-agent-worker --api-key "$WARP_API_KEY" --worker-id "my-worker" --backend direct ``` -Or with a [config file](/agent-platform/cloud-agents/self-hosting/reference/#config-file): +Or with a [config file](/platform/self-hosting/reference/#config-file): ```yaml worker_id: "my-worker" @@ -123,8 +123,8 @@ backend: ## Related pages -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/#direct-backend-config) — Full config schema for the Direct backend. -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Managed vs unmanaged and the backend decision guide. -* [Routing runs to self-hosted workers](/agent-platform/cloud-agents/self-hosting/#routing-runs-to-self-hosted-workers) — How to send tasks to your connected worker from the CLI, schedules, integrations, the API, and the web UI. -* [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) — Data boundaries and security considerations for the Direct backend. -* [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/#direct-backend) — Common Direct-backend issues. +* [Self-hosted worker reference](/platform/self-hosting/reference/#direct-backend-config) — Full config schema for the Direct backend. +* [Self-hosting overview](/platform/self-hosting/) — Managed vs unmanaged and the backend decision guide. +* [Routing runs to self-hosted workers](/platform/self-hosting/#routing-runs-to-self-hosted-workers) — How to send tasks to your connected worker from the CLI, schedules, integrations, the API, and the web UI. +* [Security and networking](/platform/self-hosting/security-and-networking/) — Data boundaries and security considerations for the Direct backend. +* [Troubleshooting](/platform/self-hosting/troubleshooting/#direct-backend) — Common Direct-backend issues. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-docker.mdx b/src/content/docs/platform/self-hosting/managed-docker.mdx similarity index 79% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/managed-docker.mdx rename to src/content/docs/platform/self-hosting/managed-docker.mdx index 0efc23294..85e26543c 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-docker.mdx +++ b/src/content/docs/platform/self-hosting/managed-docker.mdx @@ -10,7 +10,7 @@ sidebar: Run the `oz-agent-worker` daemon with the **Docker backend** — the default managed path. Each agent task runs in an isolated Docker container spawned from the worker, with full orchestration by Oz (Slack, Linear, schedules, API, `oz agent run-cloud`). :::note -This page covers the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture) with the Docker backend. For the Kubernetes backend, see [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/). For host execution without a container runtime, see [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/). If you'd rather invoke agents yourself, see [Unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/). +This page covers the [managed architecture](/platform/self-hosting/#managed-architecture) with the Docker backend. For the Kubernetes backend, see [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/). For host execution without a container runtime, see [Managed: Direct](/platform/self-hosting/managed-direct/). If you'd rather invoke agents yourself, see [Unmanaged](/platform/self-hosting/unmanaged/). ::: ## When to use the Docker backend @@ -58,7 +58,7 @@ The `oz-agent-worker` is open source. See the [oz-agent-worker repository](https There are three ways to install and run the worker with the Docker backend. Docker is recommended for production; `go install` and building from source are primarily useful for contributors and one-off testing. -The worker can be configured entirely via CLI flags, or via a YAML [config file](/agent-platform/cloud-agents/self-hosting/reference/#config-file) for more complex setups. +The worker can be configured entirely via CLI flags, or via a YAML [config file](/platform/self-hosting/reference/#config-file) for more complex setups. ### Option 1: Docker (recommended) @@ -96,7 +96,7 @@ You can run multiple workers with the same `--worker-id` for redundancy — Oz d ## Docker backend configuration -The worker can take configuration either via CLI flags or via a YAML [config file](/agent-platform/cloud-agents/self-hosting/reference/#config-file). CLI flags take precedence over config file values. +The worker can take configuration either via CLI flags or via a YAML [config file](/platform/self-hosting/reference/#config-file). CLI flags take precedence over config file values. **Common CLI flags:** @@ -144,7 +144,7 @@ backend: - name: GITHUB_TOKEN # inherits from host environment ``` -Pass it with `--config-file config.yaml`. See the [self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) for the full flag and config schema. +Pass it with `--config-file config.yaml`. See the [self-hosted worker reference](/platform/self-hosting/reference/) for the full flag and config schema. --- @@ -180,7 +180,7 @@ oz-agent-worker --api-key "$WARP_API_KEY" --worker-id "my-worker" ## Private Docker registries -The worker automatically uses credentials from your Docker config (`~/.docker/config.json`) when pulling task images. If your [environments](/agent-platform/cloud-agents/environments/) use images from a private registry, authenticate the worker's host first: +The worker automatically uses credentials from your Docker config (`~/.docker/config.json`) when pulling task images. If your [environments](/platform/environments/) use images from a private registry, authenticate the worker's host first: ```bash docker login your-registry.example.com @@ -204,14 +204,14 @@ Sidecar images (the `oz` binary and dependencies) are pulled from public registr ## Routing runs to this worker -Once your Docker worker is connected, route tasks to it with `--host "<your-worker-id>"`. Routing is the same across all managed backends — see [Routing runs to self-hosted workers](/agent-platform/cloud-agents/self-hosting/#routing-runs-to-self-hosted-workers) for CLI, scheduled, integration, API, and web UI examples. +Once your Docker worker is connected, route tasks to it with `--host "<your-worker-id>"`. Routing is the same across all managed backends — see [Routing runs to self-hosted workers](/platform/self-hosting/#routing-runs-to-self-hosted-workers) for CLI, scheduled, integration, API, and web UI examples. --- ## Related pages -* [Self-hosting quickstart](/agent-platform/cloud-agents/self-hosting/quickstart/) — ~10-minute path to a running Docker worker. -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — Full CLI flag and config file schema. -* [Environments](/agent-platform/cloud-agents/environments/) — Define the Docker image, repos, and setup commands for tasks. -* [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) — Data boundaries, egress, and Docker socket considerations. -* [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/) — Common issues with the Docker backend. +* [Self-hosting quickstart](/platform/self-hosting/quickstart/) — ~10-minute path to a running Docker worker. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — Full CLI flag and config file schema. +* [Environments](/platform/environments/) — Define the Docker image, repos, and setup commands for tasks. +* [Security and networking](/platform/self-hosting/security-and-networking/) — Data boundaries, egress, and Docker socket considerations. +* [Troubleshooting](/platform/self-hosting/troubleshooting/) — Common issues with the Docker backend. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx b/src/content/docs/platform/self-hosting/managed-kubernetes.mdx similarity index 83% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx rename to src/content/docs/platform/self-hosting/managed-kubernetes.mdx index e2a0b9936..cddee1a43 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/managed-kubernetes.mdx +++ b/src/content/docs/platform/self-hosting/managed-kubernetes.mdx @@ -10,7 +10,7 @@ sidebar: Deploy the `oz-agent-worker` daemon into a Kubernetes cluster using the included Helm chart. Each agent task runs as a **Kubernetes Job** in your cluster. Oz orchestrates runs end to end (Slack, Linear, schedules, API, `oz agent run-cloud`); your cluster provides the compute, scheduling, and policy enforcement. :::note -This page covers the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture) with the Kubernetes backend. For the default Docker backend, see [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/). For host execution without a container runtime, see [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/). To route runs to a connected worker, see [Routing runs to self-hosted workers](/agent-platform/cloud-agents/self-hosting/managed-docker/#routing-runs-to-self-hosted-workers). +This page covers the [managed architecture](/platform/self-hosting/#managed-architecture) with the Kubernetes backend. For the default Docker backend, see [Managed: Docker](/platform/self-hosting/managed-docker/). For host execution without a container runtime, see [Managed: Direct](/platform/self-hosting/managed-direct/). To route runs to a connected worker, see [Routing runs to self-hosted workers](/platform/self-hosting/managed-docker/#routing-runs-to-self-hosted-workers). ::: ## When to use the Kubernetes backend @@ -123,7 +123,7 @@ To scale horizontally, deploy multiple Helm releases with distinct worker IDs ra **Kubernetes backend:** * `kubernetesBackend.namespace` — Namespace for task Jobs. Defaults to the release namespace. -* `kubernetesBackend.defaultImage` — Default Docker image for task pods when no [Warp environment](/agent-platform/cloud-agents/environments/) has been supplied. Leave empty (default) to fall back to `ubuntu:22.04`. +* `kubernetesBackend.defaultImage` — Default Docker image for task pods when no [Warp environment](/platform/environments/) has been supplied. Leave empty (default) to fall back to `ubuntu:22.04`. * `kubernetesBackend.imagePullPolicy` — Image pull policy for task pods. Defaults to `IfNotPresent`. * `kubernetesBackend.preflightImage` — Image for the startup preflight Job. Set this if your cluster restricts allowed registries. * `kubernetesBackend.unschedulableTimeout` — How long a pod may remain unschedulable before failing. Defaults to `30s`. @@ -133,7 +133,7 @@ To scale horizontally, deploy multiple Helm releases with distinct worker IDs ra * `kubernetesBackend.extraAnnotations` — Additional annotations for task Jobs and Pods. * `kubernetesBackend.activeDeadlineSeconds` — Maximum task Job lifetime. * `kubernetesBackend.workspaceSizeLimit` — Size limit for workspace `emptyDir` volume. -* `kubernetesBackend.podTemplate` — Raw PodSpec YAML for task Jobs (same as `backend.kubernetes.pod_template` in the [config file](/agent-platform/cloud-agents/self-hosting/reference/#config-file)). +* `kubernetesBackend.podTemplate` — Raw PodSpec YAML for task Jobs (same as `backend.kubernetes.pod_template` in the [config file](/platform/self-hosting/reference/#config-file)). **API key Secret:** @@ -142,7 +142,7 @@ To scale horizontally, deploy multiple Helm releases with distinct worker IDs ra * `warp.apiKeySecret.name` — Name of the Secret containing `WARP_API_KEY`. Defaults to `oz-agent-worker`. * `warp.apiKeySecret.key` — Key within the Secret. Defaults to `WARP_API_KEY`. -See the [self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/#kubernetes-backend-config) for the full config file schema. +See the [self-hosted worker reference](/platform/self-hosting/reference/#kubernetes-backend-config) for the full config file schema. --- @@ -229,7 +229,7 @@ If your organization uses an external secrets manager (HashiCorp Vault, AWS Secr ## Setup and teardown commands -Use `kubernetesBackend.setupCommand` (Helm value) or `backend.kubernetes.setup_command` ([config file](/agent-platform/cloud-agents/self-hosting/reference/#kubernetes-backend-config)) to run a shell command before each task. Use `teardownCommand` / `teardown_command` for cleanup after the task finishes. These run inside the task Pod and are useful for workspace bootstrapping or post-run reporting. +Use `kubernetesBackend.setupCommand` (Helm value) or `backend.kubernetes.setup_command` ([config file](/platform/self-hosting/reference/#kubernetes-backend-config)) to run a shell command before each task. Use `teardownCommand` / `teardown_command` for cleanup after the task finishes. These run inside the task Pod and are useful for workspace bootstrapping or post-run reporting. --- @@ -249,7 +249,7 @@ With the default `metrics.exporter=prometheus`, the chart creates a `Service` wi To push metrics to an OTLP collector instead, set `metrics.exporter=otlp` and configure the endpoint via `metrics.extraEnv`. -See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the full list of Helm values, the metric catalog, and sample PromQL queries. +See [Monitoring](/platform/self-hosting/monitoring/) for the full list of Helm values, the metric catalog, and sample PromQL queries. --- @@ -265,10 +265,10 @@ See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the ## Related pages -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — Full CLI flag and config file schema, including every Kubernetes backend field. -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Managed vs unmanaged and the backend decision guide. -* [Routing runs to self-hosted workers](/agent-platform/cloud-agents/self-hosting/#routing-runs-to-self-hosted-workers) — How to send tasks to your connected worker from the CLI, schedules, integrations, the API, and the web UI. -* [Environments](/agent-platform/cloud-agents/environments/) — Define the task image, repos, and setup commands. -* [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) — OpenTelemetry metrics, including Helm chart metrics values. -* [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) — RBAC, admission policies, and data boundaries. -* [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/#kubernetes-backend) — Common Kubernetes-backend issues. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — Full CLI flag and config file schema, including every Kubernetes backend field. +* [Self-hosting overview](/platform/self-hosting/) — Managed vs unmanaged and the backend decision guide. +* [Routing runs to self-hosted workers](/platform/self-hosting/#routing-runs-to-self-hosted-workers) — How to send tasks to your connected worker from the CLI, schedules, integrations, the API, and the web UI. +* [Environments](/platform/environments/) — Define the task image, repos, and setup commands. +* [Monitoring](/platform/self-hosting/monitoring/) — OpenTelemetry metrics, including Helm chart metrics values. +* [Security and networking](/platform/self-hosting/security-and-networking/) — RBAC, admission policies, and data boundaries. +* [Troubleshooting](/platform/self-hosting/troubleshooting/#kubernetes-backend) — Common Kubernetes-backend issues. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/monitoring.mdx b/src/content/docs/platform/self-hosting/monitoring.mdx similarity index 91% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/monitoring.mdx rename to src/content/docs/platform/self-hosting/monitoring.mdx index 993ad87f0..a66d52f47 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/monitoring.mdx +++ b/src/content/docs/platform/self-hosting/monitoring.mdx @@ -78,7 +78,7 @@ The worker pushes metrics at the SDK's default interval. Configure the collector ## Helm chart configuration -The [Helm chart](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) includes built-in support for metrics. Enable metrics with `metrics.enabled=true`: +The [Helm chart](/platform/self-hosting/managed-kubernetes/) includes built-in support for metrics. Enable metrics with `metrics.enabled=true`: ```bash helm install oz-agent-worker ./charts/oz-agent-worker \ @@ -219,8 +219,8 @@ metrics: ## Related pages -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Architecture, decision guide, and Enterprise requirements. -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — CLI flags, config file schema, and metrics environment variables. -* [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) — Helm chart deployment, including metrics values. -* [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/) — Diagnostics for metrics issues and other common problems. -* [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) — Network egress and data boundaries. +* [Self-hosting overview](/platform/self-hosting/) — Architecture, decision guide, and Enterprise requirements. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — CLI flags, config file schema, and metrics environment variables. +* [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/) — Helm chart deployment, including metrics values. +* [Troubleshooting](/platform/self-hosting/troubleshooting/) — Diagnostics for metrics issues and other common problems. +* [Security and networking](/platform/self-hosting/security-and-networking/) — Network egress and data boundaries. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx b/src/content/docs/platform/self-hosting/quickstart.mdx similarity index 70% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx rename to src/content/docs/platform/self-hosting/quickstart.mdx index 537e381ef..a7cd3a2b6 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx +++ b/src/content/docs/platform/self-hosting/quickstart.mdx @@ -10,7 +10,7 @@ sidebar: Run your first cloud agent on your own infrastructure in ~10 minutes using the managed architecture with the Docker backend — the default and fastest path to self-hosting. :::note -This quickstart sets up the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture), where Oz orchestrates the agent and your worker provides the compute. **Prefer a CLI-only path with no Docker requirement?** Jump to the [Unmanaged quickstart](/agent-platform/cloud-agents/self-hosting/unmanaged/#unmanaged-quickstart) to run `oz agent run` directly on any host. +This quickstart sets up the [managed architecture](/platform/self-hosting/#managed-architecture), where Oz orchestrates the agent and your worker provides the compute. **Prefer a CLI-only path with no Docker requirement?** Jump to the [Unmanaged quickstart](/platform/self-hosting/unmanaged/#unmanaged-quickstart) to run `oz agent run` directly on any host. ::: --- @@ -70,12 +70,12 @@ Open the [Oz dashboard](https://oz.warp.dev), find the new task, and confirm the ## Next steps -* [Unmanaged quickstart](/agent-platform/cloud-agents/self-hosting/unmanaged/#unmanaged-quickstart) — ~5-minute CLI-only path: run `oz agent run` in your CI, Kubernetes pod, or dev box with no worker daemon and no Docker requirement. -* [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) — Full Docker backend setup, including private registries, volume mounts, and runtime configuration. -* [Environments](/agent-platform/cloud-agents/environments/) — Define a repository, Docker image, and setup commands so agents have a reproducible workspace for every run. -* [Routing runs to self-hosted workers](/agent-platform/cloud-agents/self-hosting/#routing-runs-to-self-hosted-workers) — How to route tasks from schedules, integrations (Slack, Linear), the API, and the Oz web app. -* [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) — Deploy workers into a Kubernetes cluster with Helm. -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — All CLI flags and config file options. +* [Unmanaged quickstart](/platform/self-hosting/unmanaged/#unmanaged-quickstart) — ~5-minute CLI-only path: run `oz agent run` in your CI, Kubernetes pod, or dev box with no worker daemon and no Docker requirement. +* [Managed: Docker](/platform/self-hosting/managed-docker/) — Full Docker backend setup, including private registries, volume mounts, and runtime configuration. +* [Environments](/platform/environments/) — Define a repository, Docker image, and setup commands so agents have a reproducible workspace for every run. +* [Routing runs to self-hosted workers](/platform/self-hosting/#routing-runs-to-self-hosted-workers) — How to route tasks from schedules, integrations (Slack, Linear), the API, and the Oz web app. +* [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/) — Deploy workers into a Kubernetes cluster with Helm. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — All CLI flags and config file options. ## Troubleshooting @@ -88,4 +88,4 @@ Verify your API key has team scope. Ensure the machine has outbound internet acc **Task stays queued and never runs**\ Confirm the `--host` value you passed to `oz agent run-cloud` matches your `--worker-id` exactly (case-sensitive). Check that the worker's team matches the team creating the task. -For more, see [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/). +For more, see [Troubleshooting](/platform/self-hosting/troubleshooting/). diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/reference.mdx b/src/content/docs/platform/self-hosting/reference.mdx similarity index 81% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/reference.mdx rename to src/content/docs/platform/self-hosting/reference.mdx index 255c720fe..1a6783963 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/reference.mdx +++ b/src/content/docs/platform/self-hosting/reference.mdx @@ -5,10 +5,10 @@ description: >- file schema for the Docker, Kubernetes, and Direct backends. --- -Reference for the `oz-agent-worker` daemon: CLI flags and the full YAML config-file schema for all three [managed backends](/agent-platform/cloud-agents/self-hosting/#managed-architecture) — Docker, Kubernetes, and Direct. +Reference for the `oz-agent-worker` daemon: CLI flags and the full YAML config-file schema for all three [managed backends](/platform/self-hosting/#managed-architecture) — Docker, Kubernetes, and Direct. :::note -This page documents every flag and config option. For installation and backend-specific setup walkthroughs, see [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/), [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/), or [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/). This reference applies to the managed architecture only; the [unmanaged architecture](/agent-platform/cloud-agents/self-hosting/unmanaged/) uses `oz agent run` instead. +This page documents every flag and config option. For installation and backend-specific setup walkthroughs, see [Managed: Docker](/platform/self-hosting/managed-docker/), [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/), or [Managed: Direct](/platform/self-hosting/managed-direct/). This reference applies to the managed architecture only; the [unmanaged architecture](/platform/self-hosting/unmanaged/) uses `oz agent run` instead. ::: --- @@ -25,7 +25,7 @@ The following flags are available when starting the worker. ### Optional * `--config-file` — Path to a YAML [config file](#config-file). CLI flags take precedence over config file values. -* `--backend` — Backend type: `docker` (default), `kubernetes`, or `direct`. See [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) and [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/) for backend-specific setup. +* `--backend` — Backend type: `docker` (default), `kubernetes`, or `direct`. See [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/) and [Managed: Direct](/platform/self-hosting/managed-direct/) for backend-specific setup. * `--log-level` — Log verbosity. One of `debug`, `info`, `warn`, `error`. Defaults to `info`. * `--no-cleanup` — Keep task containers, Kubernetes Jobs, or workspace directories after execution instead of removing them. Useful for debugging failed tasks. * `-v` / `--volumes` — Mount host directories into task containers (Docker backend only). Format: `HOST_PATH:CONTAINER_PATH` or `HOST_PATH:CONTAINER_PATH:MODE` (where MODE is `ro` or `rw`). Can be specified multiple times. @@ -185,22 +185,22 @@ The worker exports metrics over OpenTelemetry. Exporter selection is controlled * `OTEL_EXPORTER_OTLP_ENDPOINT` — OTLP collector endpoint (e.g., `http://otel-collector.observability.svc:4318`). * `OTEL_EXPORTER_OTLP_PROTOCOL` — OTLP protocol: `http/protobuf` (default) or `grpc`. -When deploying with the Helm chart, use the `metrics.*` values instead of setting these variables manually. See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the full setup guide, metric catalog, Helm values, and sample PromQL queries. +When deploying with the Helm chart, use the `metrics.*` values instead of setting these variables manually. See [Monitoring](/platform/self-hosting/monitoring/) for the full setup guide, metric catalog, Helm values, and sample PromQL queries. --- ## Routing runs to self-hosted workers -Once a worker is running, route cloud agent runs to it with the `--host` flag or its equivalents. See [Routing runs to self-hosted workers](/agent-platform/cloud-agents/self-hosting/#routing-runs-to-self-hosted-workers) for examples across the CLI, schedules, integrations, the API, and the web UI. +Once a worker is running, route cloud agent runs to it with the `--host` flag or its equivalents. See [Routing runs to self-hosted workers](/platform/self-hosting/#routing-runs-to-self-hosted-workers) for examples across the CLI, schedules, integrations, the API, and the web UI. --- ## Related pages -* [Managed: Docker](/agent-platform/cloud-agents/self-hosting/managed-docker/) — Docker backend setup, connectivity, and private registries. -* [Managed: Kubernetes](/agent-platform/cloud-agents/self-hosting/managed-kubernetes/) — Kubernetes backend setup, Helm chart, pod template, and operational notes. -* [Managed: Direct](/agent-platform/cloud-agents/self-hosting/managed-direct/) — Direct backend setup and workspace model. -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Architecture, decision guide, and Enterprise requirements. -* [Environments](/agent-platform/cloud-agents/environments/) — Define the Docker image, repos, and setup commands used by task containers. -* [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) — OpenTelemetry metrics for worker health, task throughput, and capacity. -* [Troubleshooting](/agent-platform/cloud-agents/self-hosting/troubleshooting/) — Worker and task failure diagnostics. +* [Managed: Docker](/platform/self-hosting/managed-docker/) — Docker backend setup, connectivity, and private registries. +* [Managed: Kubernetes](/platform/self-hosting/managed-kubernetes/) — Kubernetes backend setup, Helm chart, pod template, and operational notes. +* [Managed: Direct](/platform/self-hosting/managed-direct/) — Direct backend setup and workspace model. +* [Self-hosting overview](/platform/self-hosting/) — Architecture, decision guide, and Enterprise requirements. +* [Environments](/platform/environments/) — Define the Docker image, repos, and setup commands used by task containers. +* [Monitoring](/platform/self-hosting/monitoring/) — OpenTelemetry metrics for worker health, task throughput, and capacity. +* [Troubleshooting](/platform/self-hosting/troubleshooting/) — Worker and task failure diagnostics. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx b/src/content/docs/platform/self-hosting/security-and-networking.mdx similarity index 88% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx rename to src/content/docs/platform/self-hosting/security-and-networking.mdx index da253c006..0ae922c6e 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx +++ b/src/content/docs/platform/self-hosting/security-and-networking.mdx @@ -8,7 +8,7 @@ description: >- Self-hosting uses a split-plane architecture. Understanding which data stays on your infrastructure and which data routes through Warp is critical for security evaluation. This page summarizes the data model, network egress requirements, and backend-specific security considerations for self-hosted workers. :::note -This page applies to both the [managed](/agent-platform/cloud-agents/self-hosting/#managed-architecture) and [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) architectures. Backend-specific notes call out Docker-, Kubernetes-, and Direct-only considerations. +This page applies to both the [managed](/platform/self-hosting/#managed-architecture) and [unmanaged](/platform/self-hosting/unmanaged/) architectures. Backend-specific notes call out Docker-, Kubernetes-, and Direct-only considerations. ::: ## Data boundaries @@ -52,9 +52,9 @@ Tasks use the following Docker images: * [`warpdotdev/warp-xvfb-sidecar:latest`](https://hub.docker.com/r/warpdotdev/warp-xvfb-sidecar) (only if [computer use](/agent-platform/capabilities/computer-use/) is enabled) * [`warpdotdev/warp-claude-cli-sidecar:latest`](https://hub.docker.com/r/warpdotdev/warp-claude-cli-sidecar) (only if using Claude Code) * [`warpdotdev/warp-codex-cli-sidecar:latest`](https://hub.docker.com/r/warpdotdev/warp-codex-cli-sidecar) (only if using Codex) -* The base image specified by your [environment](/agent-platform/cloud-agents/environments/) +* The base image specified by your [environment](/platform/environments/) -**GitHub (`github.com`)** — only with the managed architecture, when using a Warp [environment](/agent-platform/cloud-agents/environments/) with configured GitHub repositories. +**GitHub (`github.com`)** — only with the managed architecture, when using a Warp [environment](/platform/environments/) with configured GitHub repositories. **Linux distribution-specific package repositories** — only with the managed architecture, when using a Warp environment whose base image does not have Git pre-installed. The exact repositories depend on the package manager configuration in the environment's base image. @@ -96,7 +96,7 @@ All traffic uses HTTPS (port 443). No inbound ports need to be opened. Since self-hosted agents run on your infrastructure, they inherit your network access. Self-hosted agents can reach services behind VPNs, self-hosted GitLab/Bitbucket instances, databases, and any other internal resources your host can reach. This is one of the primary reasons teams choose self-hosting. -See [GitLab](/agent-platform/cloud-agents/integrations/gitlab/) and [Bitbucket](/agent-platform/cloud-agents/integrations/bitbucket/) setup guides for SCM integration details. +See [GitLab](/platform/integrations/gitlab/) and [Bitbucket](/platform/integrations/bitbucket/) setup guides for SCM integration details. --- @@ -110,7 +110,7 @@ BYOLLM currently applies to interactive (local) agents; cloud agent BYOLLM suppo ## Related pages -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Managed vs unmanaged and architecture decision guide. +* [Self-hosting overview](/platform/self-hosting/) — Managed vs unmanaged and architecture decision guide. * [Security overview](/enterprise/security-and-compliance/security-overview/) — Warp's broader security model, including ZDR. * [Bring Your Own LLM (BYOLLM)](/enterprise/enterprise-features/bring-your-own-llm/) — Route inference through your own cloud provider accounts. -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — CLI flags and config schema, including every security-relevant option. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — CLI flags and config schema, including every security-relevant option. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx b/src/content/docs/platform/self-hosting/troubleshooting.mdx similarity index 85% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx rename to src/content/docs/platform/self-hosting/troubleshooting.mdx index d0b90d83f..6ad79eeb8 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/troubleshooting.mdx +++ b/src/content/docs/platform/self-hosting/troubleshooting.mdx @@ -10,7 +10,7 @@ sidebar: Diagnostic guides for the `oz-agent-worker` daemon and its task execution. Use this page when a worker won't start, won't connect, tasks stay queued, or tasks fail. :::note -The steps below apply to the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture) (`oz-agent-worker` daemon). For [unmanaged](/agent-platform/cloud-agents/self-hosting/unmanaged/) deployments, refer to the documentation for the environment running `oz agent run` (e.g., GitHub Actions, Kubernetes). +The steps below apply to the [managed architecture](/platform/self-hosting/#managed-architecture) (`oz-agent-worker` daemon). For [unmanaged](/platform/self-hosting/unmanaged/) deployments, refer to the documentation for the environment running `oz agent run` (e.g., GitHub Actions, Kubernetes). ::: --- @@ -62,7 +62,7 @@ The steps below apply to the [managed architecture](/agent-platform/cloud-agents 4. Check that no firewall rules are blocking WebSocket connections to `wss://oz.warp.dev`. 5. Increase log verbosity with `--log-level debug` to see connection details. -See [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/#network-requirements) for the full list of outbound endpoints the worker needs. +See [Security and networking](/platform/self-hosting/security-and-networking/#network-requirements) for the full list of outbound endpoints the worker needs. --- @@ -92,7 +92,7 @@ See [Security and networking](/agent-platform/cloud-agents/self-hosting/security 6. If using `metrics.podMonitor.create=true`, verify the `monitoring.coreos.com` CRDs are installed in the cluster. The `PodMonitor` resource requires the Prometheus Operator. 7. Restart the worker with `--log-level debug` and look for metrics-related error messages at startup. -See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the full setup guide. +See [Monitoring](/platform/self-hosting/monitoring/) for the full setup guide. --- @@ -132,7 +132,7 @@ See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the ### Docker backend (image pull) -1. If using a private registry, ensure Docker credentials are available to the worker. See [Private Docker registries](/agent-platform/cloud-agents/self-hosting/managed-docker/#private-docker-registries). +1. If using a private registry, ensure Docker credentials are available to the worker. See [Private Docker registries](/platform/self-hosting/managed-docker/#private-docker-registries). 2. Try pulling the image manually on the worker host: `docker pull <image>`. ### Kubernetes backend (image pull) @@ -149,7 +149,7 @@ See [Monitoring](/agent-platform/cloud-agents/self-hosting/monitoring/) for the ## Related pages -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Architecture and decision guide. -* [Self-hosted worker reference](/agent-platform/cloud-agents/self-hosting/reference/) — CLI flags and config schema, including every flag mentioned here. -* [Security and networking](/agent-platform/cloud-agents/self-hosting/security-and-networking/) — Outbound endpoints the worker needs. +* [Self-hosting overview](/platform/self-hosting/) — Architecture and decision guide. +* [Self-hosted worker reference](/platform/self-hosting/reference/) — CLI flags and config schema, including every flag mentioned here. +* [Security and networking](/platform/self-hosting/security-and-networking/) — Outbound endpoints the worker needs. * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) — Attach to running tasks to debug interactively. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx b/src/content/docs/platform/self-hosting/unmanaged.mdx similarity index 84% rename from src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx rename to src/content/docs/platform/self-hosting/unmanaged.mdx index e230752d9..25f4f1e72 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx +++ b/src/content/docs/platform/self-hosting/unmanaged.mdx @@ -10,7 +10,7 @@ sidebar: With the unmanaged architecture, **you orchestrate agent runs** by invoking `oz agent run` directly from your existing CI pipelines, Kubernetes pods, VMs, or dev boxes. The agent runs on whatever host the command is executed from; Warp tracks the session for you but does not start or stop agents. :::note -Unmanaged is the right choice if you already have a system that schedules work (CI, internal orchestrators, cron, dev environments). If you'd rather have Oz trigger and route runs from Slack, Linear, schedules, or the API, use the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture) instead. +Unmanaged is the right choice if you already have a system that schedules work (CI, internal orchestrators, cron, dev environments). If you'd rather have Oz trigger and route runs from Slack, Linear, schedules, or the API, use the [managed architecture](/platform/self-hosting/#managed-architecture) instead. ::: ## When to use unmanaged @@ -79,7 +79,7 @@ Warp maintains the [`warpdotdev/oz-agent-action`](https://github.com/warpdotdev/ warp_api_key: ${{ secrets.WARP_API_KEY }} ``` -See [GitHub Actions integration](/agent-platform/cloud-agents/integrations/github-actions/) for full details. +See [GitHub Actions integration](/platform/integrations/github-actions/) for full details. ## Example: Kubernetes @@ -124,16 +124,16 @@ Unmanaged agents are tracked on Warp's backend. Each run creates a persistent se * **Attach to** via [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) to monitor or steer. * **Query** through the [Oz API/SDK](/reference/api-and-sdk/) for custom dashboards or monitoring. -Unmanaged sessions benefit from the same shared configuration as other cloud agent runs — [MCP servers](/agent-platform/cloud-agents/mcp/), [secrets](/agent-platform/cloud-agents/secrets/), Warp Drive context, and saved prompts all apply. +Unmanaged sessions benefit from the same shared configuration as other cloud agent runs — [MCP servers](/platform/mcp/), [secrets](/platform/secrets/), Warp Drive context, and saved prompts all apply. -Unmanaged runs don't ship with the bundled declarations script, so end-of-run workspace snapshots are a no-op by default. To enable [handoff](/agent-platform/cloud-agents/handoff/) into a follow-up run, see [Customizing workspace snapshots](/agent-platform/cloud-agents/handoff/snapshots/). +Unmanaged runs don't ship with the bundled declarations script, so end-of-run workspace snapshots are a no-op by default. To enable [handoff](/platform/handoff/) into a follow-up run, see [Customizing workspace snapshots](/platform/handoff/snapshots/). --- ## Related pages -* [Self-hosting overview](/agent-platform/cloud-agents/self-hosting/) — Compare managed and unmanaged, plus the architecture decision guide. -* [GitHub Actions integration](/agent-platform/cloud-agents/integrations/github-actions/) — Run agents in CI with the official action. -* [Deployment patterns](/agent-platform/cloud-agents/deployment-patterns/) — Pattern 1 (CLI-only) explains the unmanaged model conceptually. +* [Self-hosting overview](/platform/self-hosting/) — Compare managed and unmanaged, plus the architecture decision guide. +* [GitHub Actions integration](/platform/integrations/github-actions/) — Run agents in CI with the official action. +* [Deployment patterns](/platform/deployment-patterns/) — Pattern 1 (CLI-only) explains the unmanaged model conceptually. * [Oz CLI](/reference/cli/) — Full CLI reference for `oz agent run` and related commands. * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) — Attach to running sessions to monitor or steer them. diff --git a/src/content/docs/agent-platform/cloud-agents/skills-as-agents.mdx b/src/content/docs/platform/skills-as-agents.mdx similarity index 77% rename from src/content/docs/agent-platform/cloud-agents/skills-as-agents.mdx rename to src/content/docs/platform/skills-as-agents.mdx index e2e47e72c..c6ee42253 100644 --- a/src/content/docs/agent-platform/cloud-agents/skills-as-agents.mdx +++ b/src/content/docs/platform/skills-as-agents.mdx @@ -42,7 +42,7 @@ You can also specify a skill from any accessible repository using the fully qual ### Cloud agents -For cloud agent runs (`oz agent run-cloud`), skills are discovered from repositories configured in your [environments](/agent-platform/cloud-agents/environments/). +For cloud agent runs (`oz agent run-cloud`), skills are discovered from repositories configured in your [environments](/platform/environments/). **Discovery workflow:** @@ -62,14 +62,14 @@ You can start an agent from a skill using multiple entry points. ### Oz web app -Use the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) to run skill-based agents from a visual interface. From the web app, you can: +Use the [Oz web app](/platform/oz-web-app/) to run skill-based agents from a visual interface. From the web app, you can: * Browse all skills available from your environments on the **Agents** page * View suggested agents from Warp's public [oz-skills repository](https://github.com/warpdotdev/oz-skills) * Start a new run by selecting a skill, environment, and prompt * Create scheduled agents that run skills on a cron schedule -For a complete walkthrough of the web app interface, see [Oz Web App](/agent-platform/cloud-agents/oz-web-app/). +For a complete walkthrough of the web app interface, see [Oz Web App](/platform/oz-web-app/). ### CLI @@ -108,7 +108,7 @@ For full API documentation, see [Agent configuration](/reference/api-and-sdk/#ag ## Running skills on a schedule -One of the most powerful uses for skill-based agents is running them on a schedule. [Scheduled agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) execute automatically at specified times, making them ideal for: +One of the most powerful uses for skill-based agents is running them on a schedule. [Scheduled agents](/platform/triggers/scheduled-agents/) execute automatically at specified times, making them ideal for: * **Dead code cleanup** — Weekly scans for unused code or stale feature flags * **Dependency updates** — Daily or weekly checks for security updates @@ -125,15 +125,15 @@ oz schedule create \ --prompt "Scan for dead code and unused feature flags. Open a PR with removals." ``` -You can also create schedules from the [Oz web app](/agent-platform/cloud-agents/oz-web-app/) using the **New schedule** action. +You can also create schedules from the [Oz web app](/platform/oz-web-app/) using the **New schedule** action. -For full scheduling documentation, see [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/). +For full scheduling documentation, see [Scheduled Agents](/platform/triggers/scheduled-agents/). --- ## Suggested Skills -The [Oz web app](/agent-platform/cloud-agents/oz-web-app/) displays suggested agents from the public [warpdotdev/oz-skills](https://github.com/warpdotdev/oz-skills) repository. These are pre-built skills that demonstrate common use cases and can be used as starting points for your own workflows. +The [Oz web app](/platform/oz-web-app/) displays suggested agents from the public [warpdotdev/oz-skills](https://github.com/warpdotdev/oz-skills) repository. These are pre-built skills that demonstrate common use cases and can be used as starting points for your own workflows. Suggested skills appear on the Agents page under the **Suggested** filter. @@ -142,8 +142,8 @@ Suggested skills appear on the Agents page under the **Suggested** filter. ## Related resources * [Skills](/agent-platform/capabilities/skills/) — How to create skills and skill file format -* [Environments](/agent-platform/cloud-agents/environments/) — Configure repositories and runtime context for cloud agents -* [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) — Run agents automatically on a cron schedule -* [Oz Web App](/agent-platform/cloud-agents/oz-web-app/) — Visual interface for managing cloud agents +* [Environments](/platform/environments/) — Configure repositories and runtime context for cloud agents +* [Scheduled Agents](/platform/triggers/scheduled-agents/) — Run agents automatically on a cron schedule +* [Oz Web App](/platform/oz-web-app/) — Visual interface for managing cloud agents * [Oz CLI](/reference/cli/) — Command-line interface for running agents * [Oz API & SDK](/reference/api-and-sdk/) — Programmatic access to cloud agents diff --git a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx b/src/content/docs/platform/team-access-billing-and-identity.mdx similarity index 95% rename from src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx rename to src/content/docs/platform/team-access-billing-and-identity.mdx index b18ef3c63..2d38e7d9a 100644 --- a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx +++ b/src/content/docs/platform/team-access-billing-and-identity.mdx @@ -72,7 +72,7 @@ When someone triggers a cloud agent for the first time, Warp may prompt them to #### Requirements for integrations -Integrations and [cloud agents](/agent-platform/cloud-agents/overview/) run inside Warp's cloud, which means usage is billed based on [credits](/support-and-community/plans-and-billing/credits/). +Integrations and [cloud agents](/platform/) run inside Warp's cloud, which means usage is billed based on [credits](/support-and-community/plans-and-billing/credits/). Your team must meet the following requirements to run integrations: @@ -129,22 +129,22 @@ There are two places you may encounter this installation flow: ::: <figure> - ![Oz by Warp GitHub App installation page showing repository access options](../../../../assets/agent-platform/oz-github-app-installation.png) + ![Oz by Warp GitHub App installation page showing repository access options](../../../assets/agent-platform/oz-github-app-installation.png) <figcaption>Installing the Oz by Warp GitHub App.</figcaption> </figure> 2. **Enable the GitHub org for your Warp team.** A Warp team admin opens the Admin Panel in the Warp app (**Settings** > **Admin Panel** > **Platform**) and adds the GitHub organization under **Enabled GitHub Orgs**. This associates the GitHub App installation with your Warp team. <figure> - ![Enabled GitHub Orgs setting in the Admin Panel Platform section](../../../../assets/agent-platform/admin-panel-enabled-github-orgs.png) + ![Enabled GitHub Orgs setting in the Admin Panel Platform section](../../../assets/agent-platform/admin-panel-enabled-github-orgs.png) <figcaption>Enabled GitHub Orgs setting in the Admin Panel.</figcaption> </figure> -3. **Use an agent API key.** Tasks initiated with an agent API key on the team now use tokens from the GitHub App installation to clone repos and push changes. No individual GitHub authorization is needed. On GitHub, commits and pull requests are opened by the Oz by Warp GitHub App rather than any individual user; in the Oz dashboard, the run is attributed to the bound [cloud agent](/agent-platform/cloud-agents/agents/). +3. **Use an agent API key.** Tasks initiated with an agent API key on the team now use tokens from the GitHub App installation to clone repos and push changes. No individual GitHub authorization is needed. On GitHub, commits and pull requests are opened by the Oz by Warp GitHub App rather than any individual user; in the Oz dashboard, the run is attributed to the bound [cloud agent](/platform/agents/). ### How this relates to environments -An [environment](/agent-platform/cloud-agents/environments/) is a template for a cloud agent's sandbox — it defines the Docker image, repos, and setup commands, but it does not carry its own GitHub permissions. The same environment can be used by different users or by agent API key runs, and each will authenticate to GitHub independently. +An [environment](/platform/environments/) is a template for a cloud agent's sandbox — it defines the Docker image, repos, and setup commands, but it does not carry its own GitHub permissions. The same environment can be used by different users or by agent API key runs, and each will authenticate to GitHub independently. The environment configuration and the **Enabled GitHub Orgs** setting in the Admin Panel serve different purposes: @@ -156,7 +156,7 @@ The environment configuration and the **Enabled GitHub Orgs** setting in the Adm Team GitHub authorization is complementary to the existing personal token flow: * **User-triggered runs** (personal API key, Slack, Linear, Warp app) - The agent authenticates as Oz acting on the triggering user's behalf. PRs and commits are attributed to that user. -* **Agent API key runs with GitHub App authorization** - The agent authenticates as the GitHub App installation. On GitHub, PRs and commits are attributed to the Oz by Warp GitHub App rather than any individual user. In the Oz dashboard, the run is attributed to the bound [cloud agent](/agent-platform/cloud-agents/agents/), which controls run filtering and audit attribution on the Warp side. +* **Agent API key runs with GitHub App authorization** - The agent authenticates as the GitHub App installation. On GitHub, PRs and commits are attributed to the Oz by Warp GitHub App rather than any individual user. In the Oz dashboard, the run is attributed to the bound [cloud agent](/platform/agents/), which controls run filtering and audit attribution on the Warp side. Both flows can coexist on the same team. Personal tokens are still used for user-triggered runs, and the GitHub App installation token is used when a task is initiated with an agent API key. diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx b/src/content/docs/platform/triggers/index.mdx similarity index 66% rename from src/content/docs/agent-platform/cloud-agents/triggers/index.mdx rename to src/content/docs/platform/triggers/index.mdx index cf13dc1cb..a72fc16dc 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx +++ b/src/content/docs/platform/triggers/index.mdx @@ -7,15 +7,15 @@ description: >- Triggers allow you to run cloud agents automatically without manual intervention. You can set up agents to run on schedules, in response to webhooks, or through other automation patterns. -To set up your first recurring agent, follow the [Scheduled Agents Quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/). +To set up your first recurring agent, follow the [Scheduled Agents Quickstart](/platform/triggers/scheduled-agents-quickstart/). If you're choosing between schedules, Slack, Linear, GitHub Actions, the Oz CLI, or the API, start with [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/). ## Available trigger types -* **[Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/)** - Run agents on a recurring schedule using cron expressions. +* **[Scheduled Agents](/platform/triggers/scheduled-agents/)** - Run agents on a recurring schedule using cron expressions. * **[CLI](/reference/cli/)** - Trigger cloud agents directly from your terminal using the Oz CLI. * **[API & SDK](/reference/api-and-sdk/)** - Programmatically trigger agents via the Warp API or SDK. -* **[Integrations](/agent-platform/cloud-agents/integrations/)** - Trigger agents from external services like Slack, Linear, or GitHub Actions. +* **[Integrations](/platform/integrations/)** - Trigger agents from external services like Slack, Linear, or GitHub Actions. -After a trigger fires, track and review the resulting runs across your team from the [Agent Management Panel and Oz web app Runs page](/agent-platform/cloud-agents/managing-cloud-agents/), where you can filter by source, status, day, or creator. +After a trigger fires, track and review the resulting runs across your team from the [Agent Management Panel and Oz web app Runs page](/platform/managing-cloud-agents/), where you can filter by source, status, day, or creator. diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx b/src/content/docs/platform/triggers/scheduled-agents-quickstart.mdx similarity index 81% rename from src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx rename to src/content/docs/platform/triggers/scheduled-agents-quickstart.mdx index b1c14aa80..ca1a342fc 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx +++ b/src/content/docs/platform/triggers/scheduled-agents-quickstart.mdx @@ -17,8 +17,8 @@ Watch this short demo of creating and testing a scheduled agent: ## Prerequisites -* **A Warp account on an eligible plan** - Build, Max, or Business, with credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/). -* **A cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) to create one first. +* **A Warp account on an eligible plan** - Build, Max, or Business, with credits available. See [Access, Billing, and Identity](/platform/team-access-billing-and-identity/). +* **A cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one, follow the [Cloud Agents Quickstart](/platform/quickstart/) to create one first. --- @@ -31,7 +31,7 @@ Watch this short demo of creating and testing a scheduled agent: 5. Under **Frequency**, choose a preset or enter a custom cron expression (e.g., `0 9 * * 1` for every Monday at 9 AM). 6. Click **Create schedule**. -**Breaking it down:** The schedule lives in Oz's cloud infrastructure. Unlike a local cron job, it fires even when your machine is off. Each run starts a fresh, isolated session with no state carried over from previous executions, and every run is tracked and reviewable in the [Oz web app](/agent-platform/cloud-agents/oz-web-app/). +**Breaking it down:** The schedule lives in Oz's cloud infrastructure. Unlike a local cron job, it fires even when your machine is off. Each run starts a fresh, isolated session with no state carried over from previous executions, and every run is tracked and reviewable in the [Oz web app](/platform/oz-web-app/). --- @@ -47,7 +47,7 @@ Your test run will appear under **All** on the [Runs page](https://oz.warp.dev/r Runs are also accessible from the conversation panel view in the Warp app and on mobile via the Oz web app. :::note -**Prefer the CLI?** See [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) for `oz schedule create`, `oz schedule list`, and full schedule management commands. To use a custom skill instead of a prebundled one, see [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/). +**Prefer the CLI?** See [Scheduled Agents](/platform/triggers/scheduled-agents/) for `oz schedule create`, `oz schedule list`, and full schedule management commands. To use a custom skill instead of a prebundled one, see [Skills as Agents](/platform/skills-as-agents/). ::: --- @@ -55,6 +55,6 @@ Runs are also accessible from the conversation panel view in the Warp app and on ## Next steps * **Choose the right unattended trigger** - Compare schedules, Slack, Linear, GitHub Actions, CLI, and API workflows in [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/). -* **Trigger agents from your tools** - Connect Oz to Slack or Linear to trigger agents from mentions or issue updates. See [Integrations Quickstart](/agent-platform/cloud-agents/integrations/quickstart/). -* **Manage and refine your schedule** - Change the frequency, swap skills, or pause and resume the schedule. See [Scheduled Agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) for the full reference. +* **Trigger agents from your tools** - Connect Oz to Slack or Linear to trigger agents from mentions or issue updates. See [Integrations Quickstart](/platform/integrations/quickstart/). +* **Manage and refine your schedule** - Change the frequency, swap skills, or pause and resume the schedule. See [Scheduled Agents](/platform/triggers/scheduled-agents/) for the full reference. * **Share with your team** - Schedules and environments are shared across your Warp team, so everyone benefits automatically. diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx b/src/content/docs/platform/triggers/scheduled-agents.mdx similarity index 89% rename from src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx rename to src/content/docs/platform/triggers/scheduled-agents.mdx index 9bc88ecda..109d13bd9 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx +++ b/src/content/docs/platform/triggers/scheduled-agents.mdx @@ -14,7 +14,7 @@ Warp's Scheduled Agents let you run cloud agents automatically on a **recurring Scheduled Agents run in the background on Warp’s infrastructure. Each run starts from a clean session, executes a fixed prompt, and produces its own task and session history that can be inspected after the fact. -For a guided, no-CLI walkthrough that creates a recurring agent from the Oz web app, see the [Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/). This page is the full reference for managing schedules with the Oz CLI. +For a guided, no-CLI walkthrough that creates a recurring agent from the Oz web app, see the [Scheduled Agents quickstart](/platform/triggers/scheduled-agents-quickstart/). This page is the full reference for managing schedules with the Oz CLI. If you're deciding whether to use a schedule, Slack or Linear trigger, GitHub Actions, the Oz CLI, or the API, see [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/). @@ -22,7 +22,7 @@ If you're deciding whether to use a schedule, Slack or Linear trigger, GitHub Ac ### What are Scheduled Agents? -A Scheduled Agent is a [cloud agent](/agent-platform/cloud-agents/overview/) that runs on a cron-based schedule. +A Scheduled Agent is a [cloud agent](/platform/) that runs on a cron-based schedule. **Key characteristics:** @@ -37,7 +37,7 @@ Scheduled Agents are ideal for work that should happen regularly and predictably ### Common use cases -Scheduled Agents are best suited for maintenance-style workflows, including skills that automate recurring tasks. For more on running skill-based agents on schedules, see [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/). +Scheduled Agents are best suited for maintenance-style workflows, including skills that automate recurring tasks. For more on running skill-based agents on schedules, see [Skills as Agents](/platform/skills-as-agents/). Common use cases include: @@ -69,7 +69,7 @@ Use `oz schedule create` (with required flags) to define a new Scheduled Agent. * A prompt or skill that the agent will execute. * An optional environment in which the agent will run. * An optional [model selection](/reference/cli/#using-agent-profiles). -* [Optional MCP server configuration](/agent-platform/cloud-agents/mcp/). +* [Optional MCP server configuration](/platform/mcp/). ```bash oz schedule create \ @@ -86,7 +86,7 @@ oz schedule create \ **Optional flags:** -* `--skill <SPEC>` — use a skill as the base prompt (format: `repo:skill_name` or `org/repo:skill_name`). See [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/). +* `--skill <SPEC>` — use a skill as the base prompt (format: `repo:skill_name` or `org/repo:skill_name`). See [Skills as Agents](/platform/skills-as-agents/). * `--host <WORKER_ID>` — run on a specific self-hosted worker instead of Warp-hosted infrastructure. * `--mcp <SPEC>` — attach MCP servers (inline JSON, file path, or UUID). Can be repeated. * `--model <MODEL_ID>` — override the default model. @@ -110,7 +110,7 @@ oz schedule create \ Once created, the agent will automatically run at the specified times without further action. -Scheduled Agents support the same [model selection](/reference/cli/) and [MCP server configuration](/agent-platform/cloud-agents/mcp/) as other cloud agent triggers. +Scheduled Agents support the same [model selection](/reference/cli/) and [MCP server configuration](/platform/mcp/) as other cloud agent triggers. #### Cron schedule format @@ -158,7 +158,7 @@ Each completed run also includes links to: * The task created by the agent. * The full agent session, including logs and outputs. -This makes it easy to review what ran, when it ran, and what the agent did. You can also monitor scheduled runs alongside your other agents in the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app, where you can filter by the **Scheduled** source to isolate them. +This makes it easy to review what ran, when it ran, and what the agent did. You can also monitor scheduled runs alongside your other agents in the [Agent Management Panel](/platform/managing-cloud-agents/) in the Warp app, where you can filter by the **Scheduled** source to isolate them. #### Viewing a specific Scheduled Agent @@ -302,6 +302,6 @@ Carefully review prompts and schedules before deploying them broadly, especially Scheduled Agents are best when work should happen on a predictable cadence. -If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use [integrations](/agent-platform/cloud-agents/integrations/) to trigger cloud agents instead. +If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use [integrations](/platform/integrations/) to trigger cloud agents instead. -Many teams use both together: [triggers](/agent-platform/cloud-agents/triggers/) for reactive workflows, and Scheduled Agents for proactive maintenance. +Many teams use both together: [triggers](/platform/triggers/) for reactive workflows, and Scheduled Agents for proactive maintenance. diff --git a/src/content/docs/agent-platform/cloud-agents/viewing-cloud-agent-runs.mdx b/src/content/docs/platform/viewing-cloud-agent-runs.mdx similarity index 85% rename from src/content/docs/agent-platform/cloud-agents/viewing-cloud-agent-runs.mdx rename to src/content/docs/platform/viewing-cloud-agent-runs.mdx index a9fc19c35..8bb3d84be 100644 --- a/src/content/docs/agent-platform/cloud-agents/viewing-cloud-agent-runs.mdx +++ b/src/content/docs/platform/viewing-cloud-agent-runs.mdx @@ -8,7 +8,7 @@ sidebar: --- import VideoEmbed from '@components/VideoEmbed.astro'; -Cloud agent session sharing lets you open, inspect, and continue interacting with agent tasks that are running on remote virtual machines. Whether a cloud agent was triggered from [integrations](/agent-platform/cloud-agents/integrations/) like Slack, Linear, GitHub Actions, or the [Oz CLI](/reference/cli/), you can view its full session, follow along in real time, ask follow-up questions, and even "fork" the work into your local Warp environment. +Cloud agent session sharing lets you open, inspect, and continue interacting with agent tasks that are running on remote virtual machines. Whether a cloud agent was triggered from [integrations](/platform/integrations/) like Slack, Linear, GitHub Actions, or the [Oz CLI](/reference/cli/), you can view its full session, follow along in real time, ask follow-up questions, and even "fork" the work into your local Warp environment. Use cloud agent session sharing when you need to inspect a cloud agent run, debug a failed automation, or give teammates a shared record of what the agent did. The shared session is the review surface for the run: it shows the prompt, plan, commands, logs, outputs, and follow-up messages where available. @@ -38,8 +38,8 @@ Everything is accessible whether or not Warp is installed on the viewer’s mach When a cloud agent starts working — for example, from a Slack mention, a Linear issue, or a [CLI](/reference/cli/) trigger — Warp attaches a shareable link to the run. -* From [Slack](/agent-platform/cloud-agents/integrations/slack/), click **View Agent** in the agent response to open the session. -* From [Linear](/agent-platform/cloud-agents/integrations/linear/), click the ↗ **Warp** button ("Open in Warp") on the ticket to open the session. +* From [Slack](/platform/integrations/slack/), click **View Agent** in the agent response to open the session. +* From [Linear](/platform/integrations/linear/), click the ↗ **Warp** button ("Open in Warp") on the ticket to open the session. You can also open the session directly in your browser without installing Warp. Here, you’ll see the complete agent session running on a cloud VM, including all steps, logs, and context. @@ -76,7 +76,7 @@ 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 is the cloud-to-local direction of [Handoff between local and cloud agents](/platform/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. @@ -102,6 +102,6 @@ You get consistent visibility into the work regardless of where you open it. ### Related pages -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) — Find cloud agent runs by source, status, trigger, or owner. +* [Managing cloud agents](/platform/managing-cloud-agents/) — Find cloud agent runs by source, status, trigger, or owner. * [Attach agent session context to GitHub PRs](/guides/agent-workflows/how-to-attach-agent-session-context-to-github-prs/) — Share a run link with a PR so reviewers can inspect the agent's execution context. * [Agent Session Sharing](/agent-platform/local-agents/session-sharing/) — Share local Warp agent or third-party CLI agent sessions. diff --git a/src/content/docs/agent-platform/cloud-agents/warp-hosting.mdx b/src/content/docs/platform/warp-hosting.mdx similarity index 85% rename from src/content/docs/agent-platform/cloud-agents/warp-hosting.mdx rename to src/content/docs/platform/warp-hosting.mdx index 16c62dfbc..13cf9741d 100644 --- a/src/content/docs/agent-platform/cloud-agents/warp-hosting.mdx +++ b/src/content/docs/platform/warp-hosting.mdx @@ -16,7 +16,7 @@ All Warp-hosted agents run in fully-isolated sandboxes. Warp uses a mix of infra ### OS and architecture -Warp-hosted agents use the container image specified in your [environment](/agent-platform/cloud-agents/environments/). +Warp-hosted agents use the container image specified in your [environment](/platform/environments/). They are compatible with any Linux x86-64 image that includes a `bash` shell and core utilities like `ls` and `mkdir`. ### Resources @@ -50,5 +50,5 @@ Warp's hosted agents have network egress enabled by default. Outgoing requests m ## Related pages -* [Oz Platform](/agent-platform/cloud-agents/platform/) - Learn how Warp-hosted agents fit into the Oz Platform. -* [Self-hosting](/agent-platform/cloud-agents/self-hosting/) - Run agents on infrastructure you manage when execution must stay inside your network. +* [Oz Platform](/platform/overview/) - Learn how Warp-hosted agents fit into the Oz Platform. +* [Self-hosting](/platform/self-hosting/) - Run agents on infrastructure you manage when execution must stay inside your network. diff --git a/src/content/docs/quickstart.mdx b/src/content/docs/quickstart.mdx index dad1a0ac1..b23b17b9c 100644 --- a/src/content/docs/quickstart.mdx +++ b/src/content/docs/quickstart.mdx @@ -116,5 +116,5 @@ Now that you have the basics, check out the features that make Warp a full devel * **[Customizing Warp](/getting-started/quickstart/customizing-warp/)** — Pick a theme, configure your prompt, choose your AI model, and import keybindings from another terminal. * **[Codebase Context](/agent-platform/capabilities/codebase-context/)** — Index your Git repositories so agents understand your code and give context-aware answers across large, multi-repo systems. -* **[Cloud agents](/agent-platform/cloud-agents/overview/)** — Run agents in the background for PR review, issue triage, dependency updates, and other tasks that don't need your immediate attention. +* **[Cloud agents](/platform/)** — Run agents in the background for PR review, issue triage, dependency updates, and other tasks that don't need your immediate attention. * **[Keyboard shortcuts](/getting-started/keyboard-shortcuts/)** — The full shortcut reference for power users. diff --git a/src/content/docs/reference/api-and-sdk/index.mdx b/src/content/docs/reference/api-and-sdk/index.mdx index 12706836c..56632f84a 100644 --- a/src/content/docs/reference/api-and-sdk/index.mdx +++ b/src/content/docs/reference/api-and-sdk/index.mdx @@ -12,7 +12,7 @@ The Oz API and SDKs let you create, monitor, and inspect cloud agent runs progra ### Oz API -The Oz API lets you create and inspect [Cloud Agent](/agent-platform/cloud-agents/overview/) runs over HTTP from any system (CI, cron, backend services, internal tools), without requiring the Warp desktop app. +The Oz API lets you create and inspect [Cloud Agent](/platform/) runs over HTTP from any system (CI, cron, backend services, internal tools), without requiring the Warp desktop app. **With the API you can:** diff --git a/src/content/docs/reference/api-and-sdk/quickstart.mdx b/src/content/docs/reference/api-and-sdk/quickstart.mdx index 547b26ffb..52d9b7721 100644 --- a/src/content/docs/reference/api-and-sdk/quickstart.mdx +++ b/src/content/docs/reference/api-and-sdk/quickstart.mdx @@ -17,8 +17,8 @@ Watch this short demo of how the REST API can power agent-backed apps like [Powe ## Prerequisites -* **A Warp API key** - Create one in the [Oz web app](https://oz.warp.dev/settings) and copy the raw value. Use a personal key if you want runs attributed to you, or an agent key to attribute runs to a [cloud agent](/agent-platform/cloud-agents/agents/). See [API Keys](/reference/cli/api-keys/) for the full flow. -* **An Oz cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have an environment yet, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) first. +* **A Warp API key** - Create one in the [Oz web app](https://oz.warp.dev/settings) and copy the raw value. Use a personal key if you want runs attributed to you, or an agent key to attribute runs to a [cloud agent](/platform/agents/). See [API Keys](/reference/cli/api-keys/) for the full flow. +* **An Oz cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have an environment yet, follow the [Cloud Agents Quickstart](/platform/quickstart/) first. --- @@ -94,4 +94,4 @@ You can also view and manage all runs in the [Oz dashboard](https://oz.warp.dev/ * **Read the full API reference** - [Oz API](/reference/api-and-sdk/) documents all endpoint parameters, query filters, and response schemas. * **Explore the SDKs** - [Python SDK](https://github.com/warpdotdev/oz-sdk-python) and [TypeScript SDK](https://github.com/warpdotdev/oz-sdk-typescript) include typed request/response models, retries, and error handling. * **See a real-world example** - [Demo: Sentry monitoring with SDK](/reference/api-and-sdk/demo-sentry-monitoring-with-sdk/) shows how to build a webhook handler that triggers agents from production errors. -* **Schedule and automate** - See [Scheduled Agents Quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/) to run agents on a cron, or [Integrations Quickstart](/agent-platform/cloud-agents/integrations/quickstart/) to trigger agents from Slack or Linear. +* **Schedule and automate** - See [Scheduled Agents Quickstart](/platform/triggers/scheduled-agents-quickstart/) to run agents on a cron, or [Integrations Quickstart](/platform/integrations/quickstart/) to trigger agents from Slack or Linear. diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/agent-process-failed.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/agent-process-failed.mdx index a2af0e20a..41b8898b0 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/agent-process-failed.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/agent-process-failed.mdx @@ -57,6 +57,6 @@ This error is returned when: ## Related -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent tasks work +* [Cloud Agents Overview](/platform/) — How cloud agent tasks work * [environment_setup_failed](/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed/) — Errors during environment setup * [internal_error](/reference/api-and-sdk/troubleshooting/errors/internal-error/) — Catch-all for unexpected server-side errors diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/authentication-required.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/authentication-required.mdx index c6d477082..ec348aefd 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/authentication-required.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/authentication-required.mdx @@ -57,4 +57,4 @@ This error is returned when: ## Related * [Oz API & SDK](/reference/api-and-sdk/) — API authentication -* [Oz Platform](/agent-platform/cloud-agents/platform/) — API key management +* [Oz Platform](/platform/overview/) — API key management diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/budget-exceeded.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/budget-exceeded.mdx index 87acb458b..f483a50b5 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/budget-exceeded.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/budget-exceeded.mdx @@ -54,4 +54,4 @@ If you are not a team admin, contact your team admin to adjust the budget. ## Related -* [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) — Budget configuration and billing details +* [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) — Budget configuration and billing details diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/conflict.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/conflict.mdx index 24346d285..f13e52c50 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/conflict.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/conflict.mdx @@ -55,5 +55,5 @@ For task cancellation specifically, wait until the task moves from **pending** t ## Related -* [Managing Cloud Agents](/agent-platform/cloud-agents/managing-cloud-agents/) — Viewing and managing agent tasks +* [Managing Cloud Agents](/platform/managing-cloud-agents/) — Viewing and managing agent tasks * [Oz API & SDK](/reference/api-and-sdk/) — API reference for managing agent tasks diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/content-policy-violation.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/content-policy-violation.mdx index 6f25fbdb5..3b6480de1 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/content-policy-violation.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/content-policy-violation.mdx @@ -56,5 +56,5 @@ For security reasons, the error message is intentionally generic and does not de ## Related -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent tasks work -* [Environments](/agent-platform/cloud-agents/environments/) — Configuring setup commands +* [Cloud Agents Overview](/platform/) — How cloud agent tasks work +* [Environments](/platform/environments/) — Configuring setup commands diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed.mdx index f03c20c9f..b356fc21e 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/environment-setup-failed.mdx @@ -51,16 +51,16 @@ The `title` field in the response will describe the specific setup failure. ## How to resolve -1. **Check repository configuration** — Verify the repository URL and branch name in your [environment settings](/agent-platform/cloud-agents/environments/). Ensure the repository exists and is accessible. +1. **Check repository configuration** — Verify the repository URL and branch name in your [environment settings](/platform/environments/). Ensure the repository exists and is accessible. 2. **Check setup commands** — Run the setup commands locally to confirm they work. Look for missing dependencies, incorrect paths, or syntax errors. 3. **Check working directory** — Ensure the working directory path exists relative to the cloned repository root. 4. **Check MCP server configuration** — Verify MCP server startup commands and that any required dependencies or credentials are available. See [MCP Servers for Agents](/reference/cli/mcp-servers/). -5. **Check secrets** — If setup commands reference environment variables from [secrets](/agent-platform/cloud-agents/secrets/), verify the secrets are configured and in scope. +5. **Check secrets** — If setup commands reference environment variables from [secrets](/platform/secrets/), verify the secrets are configured and in scope. --- ## Related -* [Environments](/agent-platform/cloud-agents/environments/) — Configuring cloud agent environments -* [Secrets](/agent-platform/cloud-agents/secrets/) — Managing credentials for agent environments +* [Environments](/platform/environments/) — Configuring cloud agent environments +* [Secrets](/platform/secrets/) — Managing credentials for agent environments * [MCP Servers for Agents](/reference/cli/mcp-servers/) — Configuring MCP servers diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/external-authentication-required.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/external-authentication-required.mdx index 0052e7c1b..9089edb9f 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/external-authentication-required.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/external-authentication-required.mdx @@ -101,7 +101,7 @@ This error includes extra fields beyond the standard response format: 2. Ensure the app has access to all repositories listed in `inaccessible_repos`. 3. Retry the task. -If you are using an **agent API key** bound to a [cloud agent](/agent-platform/cloud-agents/agents/), ensure the Warp GitHub App is installed on the organization that owns the repositories. +If you are using an **agent API key** bound to a [cloud agent](/platform/agents/), ensure the Warp GitHub App is installed on the organization that owns the repositories. ### Account matching failed @@ -113,5 +113,5 @@ If you are using an **agent API key** bound to a [cloud agent](/agent-platform/c ## Related -* [Environments](/agent-platform/cloud-agents/environments/) — Configuring GitHub repositories for cloud agent environments -* [Integrations](/agent-platform/cloud-agents/integrations/) — Setting up Slack and Linear integrations +* [Environments](/platform/environments/) — Configuring GitHub repositories for cloud agent environments +* [Integrations](/platform/integrations/) — Setting up Slack and Linear integrations diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/feature-not-available.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/feature-not-available.mdx index 2da615ebb..1d255c180 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/feature-not-available.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/feature-not-available.mdx @@ -49,11 +49,11 @@ The `title` field in the response will describe the specific feature that is una 2. Upgrade to a plan that includes the required feature. 3. Retry the operation. -For plan comparisons and feature availability, see [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/). +For plan comparisons and feature availability, see [Access, Billing, and Identity](/platform/team-access-billing-and-identity/). --- ## Related -* [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) — Plan requirements and feature availability -* [Integrations](/agent-platform/cloud-agents/integrations/) — Integration requirements by plan +* [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) — Plan requirements and feature availability +* [Integrations](/platform/integrations/) — Integration requirements by plan diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx index 74640b831..e8f2a92fc 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/index.mdx @@ -87,5 +87,5 @@ When an error response includes a `trace_id`, you can include it when [contactin ## Related * [Oz API & SDK](/reference/api-and-sdk/) — API reference for creating and managing agent tasks -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agents work -* [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) — Plan requirements and billing details +* [Cloud Agents Overview](/platform/) — How cloud agents work +* [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) — Plan requirements and billing details diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/infrastructure-timeout.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/infrastructure-timeout.mdx index 41d25a90e..fff2a0222 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/infrastructure-timeout.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/infrastructure-timeout.mdx @@ -50,13 +50,13 @@ This error is returned when: ## How to resolve 1. Retry the task. If it consistently times out, break the work into smaller, shorter-running subtasks or reduce the scope of the prompt. -2. Review the [environment configuration](/agent-platform/cloud-agents/environments/) for setup commands or MCP servers that block on user input, long downloads, or unresponsive network calls. +2. Review the [environment configuration](/platform/environments/) for setup commands or MCP servers that block on user input, long downloads, or unresponsive network calls. 3. Contact [Warp support](/support-and-community/troubleshooting-and-support/sending-us-feedback/) and include the `trace_id` from the error response if the issue persists. --- ## Related -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent tasks work +* [Cloud Agents Overview](/platform/) — How cloud agent tasks work * [internal_error](/reference/api-and-sdk/troubleshooting/errors/internal-error/) — Other platform-level errors -* [Cloud Agents FAQs](/agent-platform/cloud-agents/faqs/) — Common questions about cloud agents +* [Cloud Agents FAQs](/platform/faqs/) — Common questions about cloud agents diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx index 76f3521ec..18230470a 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/insufficient-credits.mdx @@ -72,7 +72,7 @@ If you are not a team admin or the team owner, contact them to top up the right ## Related -* [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) — Credit billing for individual user runs and agent API key runs. +* [Access, billing, and identity permissions](/platform/team-access-billing-and-identity/) — Credit billing for individual user runs and agent API key runs. * [Add-on credits](/support-and-community/plans-and-billing/add-on-credits/) — Purchase additional credits and configure auto-reload. * [Platform credits](/support-and-community/plans-and-billing/platform-credits/) — The third credit bucket alongside AI credits and compute credits. -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — Billing and plan requirements for cloud agents. +* [Cloud Agents Overview](/platform/) — Billing and plan requirements for cloud agents. diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-disabled.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-disabled.mdx index 1c22831f4..1573fcebc 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-disabled.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-disabled.mdx @@ -51,5 +51,5 @@ This error is returned when: ## Related -* [Integrations](/agent-platform/cloud-agents/integrations/) — Configuring Slack, Linear, and GitHub integrations -* [Oz Web App](/agent-platform/cloud-agents/oz-web-app/) — Managing integrations via the web interface +* [Integrations](/platform/integrations/) — Configuring Slack, Linear, and GitHub integrations +* [Oz Web App](/platform/oz-web-app/) — Managing integrations via the web interface diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-not-configured.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-not-configured.mdx index c2ce1f4f6..23d638cb0 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-not-configured.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/integration-not-configured.mdx @@ -63,6 +63,6 @@ This error includes extra fields beyond the standard response format: ## Related -* [Integrations](/agent-platform/cloud-agents/integrations/) — Integration setup guides -* [Slack Integration](/agent-platform/cloud-agents/integrations/slack/) — Slack-specific setup -* [Linear Integration](/agent-platform/cloud-agents/integrations/linear/) — Linear-specific setup +* [Integrations](/platform/integrations/) — Integration setup guides +* [Slack Integration](/platform/integrations/slack/) — Slack-specific setup +* [Linear Integration](/platform/integrations/linear/) — Linear-specific setup diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/internal-error.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/internal-error.mdx index 5da758388..2dd683a7d 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/internal-error.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/internal-error.mdx @@ -56,5 +56,5 @@ If the error persists: ## Related -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent tasks work -* [Cloud Agents FAQs](/agent-platform/cloud-agents/faqs/) — Common questions about cloud agents +* [Cloud Agents Overview](/platform/) — How cloud agent tasks work +* [Cloud Agents FAQs](/platform/faqs/) — Common questions about cloud agents diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/not-authorized.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/not-authorized.mdx index edcde8587..5e7e1917a 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/not-authorized.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/not-authorized.mdx @@ -54,5 +54,5 @@ This error is returned when: ## Related -* [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/) — Permission model and identity +* [Access, Billing, and Identity](/platform/team-access-billing-and-identity/) — Permission model and identity * [Oz API & SDK](/reference/api-and-sdk/) — API authentication and authorization diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/operation-not-supported.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/operation-not-supported.mdx index 355924e45..8dae9b3c4 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/operation-not-supported.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/operation-not-supported.mdx @@ -54,6 +54,6 @@ This error is returned when: ## Related -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent tasks work -* [Self-hosting](/agent-platform/cloud-agents/self-hosting/) — Self-hosted agent configuration +* [Cloud Agents Overview](/platform/) — How cloud agent tasks work +* [Self-hosting](/platform/self-hosting/) — Self-hosted agent configuration * [Oz API & SDK](/reference/api-and-sdk/) — API reference for managing agent tasks diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-not-found.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-not-found.mdx index 058777d34..45cc276ab 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-not-found.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-not-found.mdx @@ -55,5 +55,5 @@ The `detail` field in the response will describe which resource was not found. ## Related -* [Environments](/agent-platform/cloud-agents/environments/) — Managing cloud agent environments -* [Managing Cloud Agents](/agent-platform/cloud-agents/managing-cloud-agents/) — Viewing and managing agent tasks +* [Environments](/platform/environments/) — Managing cloud agent environments +* [Managing Cloud Agents](/platform/managing-cloud-agents/) — Viewing and managing agent tasks diff --git a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-unavailable.mdx b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-unavailable.mdx index 482aa4b9b..69f5b63c3 100644 --- a/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-unavailable.mdx +++ b/src/content/docs/reference/api-and-sdk/troubleshooting/errors/resource-unavailable.mdx @@ -71,5 +71,5 @@ If the error persists after retries: ## Related -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) — How cloud agent execution works -* [Deployment Patterns](/agent-platform/cloud-agents/deployment-patterns/) — Execution models and infrastructure +* [Cloud Agents Overview](/platform/) — How cloud agent execution works +* [Deployment Patterns](/platform/deployment-patterns/) — Execution models and infrastructure diff --git a/src/content/docs/reference/cli/api-keys.mdx b/src/content/docs/reference/cli/api-keys.mdx index 08cc720a3..06d2b44ab 100644 --- a/src/content/docs/reference/cli/api-keys.mdx +++ b/src/content/docs/reference/cli/api-keys.mdx @@ -13,7 +13,7 @@ API keys let the Oz CLI and cloud agents authenticate without human interaction. Every API key is either a **personal API key** or an **agent API key**. * **Personal API keys** authenticate as you. Runs use your GitHub permissions, draw from your credit pool, and inherit your account's [skills](/agent-platform/capabilities/skills/). Use a personal key when the run should act on your behalf — for example, developer-triggered API automation, or the [Enterprise Analytics API](/enterprise/enterprise-features/analytics-api/), which only accepts personal keys. -* **Agent API keys** run as a [cloud agent](/agent-platform/cloud-agents/agents/) on your team. Use an agent key for scheduled jobs, integrations (Slack, Linear, GitHub Actions), SDK-triggered runs, and other automation that isn't tied to a specific user. Billing and GitHub permissions are scoped to the team rather than to you. +* **Agent API keys** run as a [cloud agent](/platform/agents/) on your team. Use an agent key for scheduled jobs, integrations (Slack, Linear, GitHub Actions), SDK-triggered runs, and other automation that isn't tied to a specific user. Billing and GitHub permissions are scoped to the team rather than to you. ## Creating an API key @@ -59,9 +59,9 @@ The key type determines who the run is attributed to, which credit pool is bille * Run as a cloud agent on your team. * On Build, Max, and Business plans, bill the team owner: the owner's plan-included credits, then the owner's add-on credits. With auto-reload on, usage can trigger a reload on the owner's pool, subject to the team-wide monthly spend cap. On Enterprise plans, use the team-scoped credit pool. -* Use the **Oz by Warp** GitHub App when [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) is configured. Without team GitHub authorization, agent keys are still useful for tasks that don't need to write to GitHub, such as analysis, monitoring, or triage. +* Use the **Oz by Warp** GitHub App when [team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization) is configured. Without team GitHub authorization, agent keys are still useful for tasks that don't need to write to GitHub, such as analysis, monitoring, or triage. -For the full credit waterfall, see [Access, billing, and identity permissions](/agent-platform/cloud-agents/team-access-billing-and-identity/) and [add-on credits](/support-and-community/plans-and-billing/add-on-credits/). +For the full credit waterfall, see [Access, billing, and identity permissions](/platform/team-access-billing-and-identity/) and [add-on credits](/support-and-community/plans-and-billing/add-on-credits/). ## Authenticating with API keys @@ -109,6 +109,6 @@ Deleted keys are immediately invalidated and cannot be recovered. Any services o * **Use personal keys for runs that should act as you.** When code changes should be attributed to your GitHub account, a personal key is the right choice. Use agent keys for automation that isn't tied to a specific user. * **Use environment variables.** Avoid passing API keys directly in commands where they may be logged or visible in shell history. * **Set appropriate expiration.** Use shorter expiration times for development and testing; consider longer durations for stable production workflows. -* **Configure team GitHub authorization for agents that write to GitHub.** Personal keys authenticate as you with your GitHub permissions. Agent keys authenticate via the [Oz by Warp GitHub App](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) when team GitHub authorization is configured in the Admin Panel. +* **Configure team GitHub authorization for agents that write to GitHub.** Personal keys authenticate as you with your GitHub permissions. Agent keys authenticate via the [Oz by Warp GitHub App](/platform/team-access-billing-and-identity/#team-github-authorization) when team GitHub authorization is configured in the Admin Panel. * **Rotate keys periodically.** Create new keys and retire old ones on a regular schedule to limit exposure from compromised credentials. * **Store securely.** Use secret managers (like 1Password CLI, HashiCorp Vault, or cloud provider secret services) rather than plain text files. diff --git a/src/content/docs/reference/cli/artifacts.mdx b/src/content/docs/reference/cli/artifacts.mdx index 4a8ada786..d8380416a 100644 --- a/src/content/docs/reference/cli/artifacts.mdx +++ b/src/content/docs/reference/cli/artifacts.mdx @@ -74,4 +74,4 @@ oz artifact download "$ARTIFACT_UID" --out ./latest-report.html ## Related * [Oz API & SDK](/reference/api-and-sdk/) - retrieve artifacts programmatically over HTTP. -* [Scheduled cloud agents](/agent-platform/cloud-agents/triggers/scheduled-agents/) - common producer of recurring artifacts that downstream tooling consumes. +* [Scheduled cloud agents](/platform/triggers/scheduled-agents/) - common producer of recurring artifacts that downstream tooling consumes. diff --git a/src/content/docs/reference/cli/federate.mdx b/src/content/docs/reference/cli/federate.mdx index c85124643..b1ec3e007 100644 --- a/src/content/docs/reference/cli/federate.mdx +++ b/src/content/docs/reference/cli/federate.mdx @@ -44,11 +44,11 @@ oz federate issue-token \ The subject claim is what your cloud provider's policy will match on, so pick the combination that gives you the IAM granularity you need. Supported components: -* **`principal`** - The acting principal, like `user:my-user-id` or `service_account:my-sa-id`. A `service_account:` principal corresponds to a [cloud agent](/agent-platform/cloud-agents/agents/) on your team. +* **`principal`** - The acting principal, like `user:my-user-id` or `service_account:my-sa-id`. A `service_account:` principal corresponds to a [cloud agent](/platform/agents/) on your team. * **`scoped_principal`** - The principal scoped to a team, like `principal:my-team-id/user:my-user-id`. * **`email`** - The principal's email, like `email:user@warp.dev`. * **`teams`** - The principal's team, like `teams:my-team-id`. -* **`environment`** - The [cloud environment](/agent-platform/cloud-agents/environments/) the run is using, like `environment:my-environment-id`. +* **`environment`** - The [cloud environment](/platform/environments/) the run is using, like `environment:my-environment-id`. * **`agent_name`** - The configured name of the run, like `agent_name:my-agent`. * **`skill_spec`** - The skill the run was launched from, like `skill_spec:warpdotdev/repo_path_to_skill`. * **`run_id`** - The run's unique ID, like `run_id:abc123`. @@ -94,5 +94,5 @@ A typical GCP flow: ## Related -* [Cloud environments](/agent-platform/cloud-agents/environments/) - configure the environment your agent runs in. -* [Secrets](/agent-platform/cloud-agents/secrets/) - alternative for credentials that can't be federated. +* [Cloud environments](/platform/environments/) - configure the environment your agent runs in. +* [Secrets](/platform/secrets/) - alternative for credentials that can't be federated. diff --git a/src/content/docs/reference/cli/index.mdx b/src/content/docs/reference/cli/index.mdx index 3c9f5a3b3..9aad722de 100644 --- a/src/content/docs/reference/cli/index.mdx +++ b/src/content/docs/reference/cli/index.mdx @@ -15,9 +15,9 @@ The Oz CLI is the command-line tool for running and managing Warp's cloud agents ## What is the Oz CLI? -The Oz CLI is the command-line tool that lets you run [Cloud Agents](/agent-platform/cloud-agents/overview/) from anywhere, including terminals, scripts, automated systems, or services. +The Oz CLI is the command-line tool that lets you run [Cloud Agents](/platform/) from anywhere, including terminals, scripts, automated systems, or services. -It's the standard runtime entry point that turns a **prompt** plus **configuration** into an **executable agent task** that runs on either a **Warp-hosted or [self-hosted](/agent-platform/cloud-agents/self-hosting/) runner**. +It's the standard runtime entry point that turns a **prompt** plus **configuration** into an **executable agent task** that runs on either a **Warp-hosted or [self-hosted](/platform/self-hosting/) runner**. With the Oz CLI, you can: @@ -158,7 +158,7 @@ Use `oz whoami` to print information about the currently authenticated principal oz whoami ``` -The output includes your user or service account ID, display name, email, and team (when available). When the CLI is authenticated as a service account principal, that principal is a [cloud agent](/agent-platform/cloud-agents/agents/) on your team. For machine-readable output, set `--output-format json` or `--output-format text`. +The output includes your user or service account ID, display name, email, and team (when available). When the CLI is authenticated as a service account principal, that principal is a [cloud agent](/platform/agents/) on your team. For machine-readable output, set `--output-format json` or `--output-format text`. ```sh # JSON output for scripts diff --git a/src/content/docs/reference/cli/integration-setup.mdx b/src/content/docs/reference/cli/integration-setup.mdx index 1e1b0cb8c..f63830750 100644 --- a/src/content/docs/reference/cli/integration-setup.mdx +++ b/src/content/docs/reference/cli/integration-setup.mdx @@ -20,7 +20,7 @@ Note: While cloud agents can be run individually via CLI without a team, integra ::: :::note -For a quickstart guide to Warp integrations, see the [Integrations overview](/agent-platform/cloud-agents/integrations/). +For a quickstart guide to Warp integrations, see the [Integrations overview](/platform/integrations/). ::: ## How integrations and environments work @@ -30,7 +30,7 @@ Warp integrations connect external tools, like Slack or Linear, to agents that r There are three main components to know: * **Triggers** provide the context that tells Warp _what_ to run. A trigger could be a Slack message where you tag @Oz, or a Linear issue or comment. -* [**Integrations**](/agent-platform/cloud-agents/integrations/) are what connect the trigger surface (Slack, Linear) to Warp. An integration links the trigger to your [Warp team](/knowledge-and-collaboration/teams/) and handles posting results to the original tool, for example, replying in Slack. +* [**Integrations**](/platform/integrations/) are what connect the trigger surface (Slack, Linear) to Warp. An integration links the trigger to your [Warp team](/knowledge-and-collaboration/teams/) and handles posting results to the original tool, for example, replying in Slack. * **Environments** define how and where agents run your code. When an agent is triggered, Warp uses the environment to spin up a container, clone repositories, and execute the agent's workflow. ``` @@ -112,7 +112,7 @@ The guided flow will: 3. Suggest setup commands based on your scripts and package managers 4. Create the environment through the CLI and return an environment ID -This produces a ready-to-use environment that can immediately be connected to [Slack](/agent-platform/cloud-agents/integrations/slack/) or [Linear](/agent-platform/cloud-agents/integrations/linear/). +This produces a ready-to-use environment that can immediately be connected to [Slack](/platform/integrations/slack/) or [Linear](/platform/integrations/linear/). ### Option 2: Create an environment with the CLI @@ -149,7 +149,7 @@ You can inspect existing environments with `oz environment list`. To delete an environment, use `oz environment delete <ID>`. Add `--force` to skip confirmation checks for environments used by integrations. -For more details about environment configuration, see the [Slack](/agent-platform/cloud-agents/integrations/slack/) and [Linear](/agent-platform/cloud-agents/integrations/linear/) articles. +For more details about environment configuration, see the [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) articles. #### Example environments @@ -190,10 +190,10 @@ For automated workflows that use an [agent API key](/reference/cli/api-keys/) (C This requires a Warp team admin to enable the GitHub organization in the Admin Panel (**Settings** > **Admin Panel** > **Platform**). Once configured, tasks initiated with an agent API key can clone repos and open pull requests using the GitHub App installation token. -For full setup instructions, see [Team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization). +For full setup instructions, see [Team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization). :::note -**Using API keys:** Personal API keys authenticate as you, so the agent runs with your GitHub permissions and code changes are attributed to your account. Agent API keys with [team GitHub authorization](/agent-platform/cloud-agents/team-access-billing-and-identity/#team-github-authorization) configured use the GitHub App token instead. +**Using API keys:** Personal API keys authenticate as you, so the agent runs with your GitHub permissions and code changes are attributed to your account. Agent API keys with [team GitHub authorization](/platform/team-access-billing-and-identity/#team-github-authorization) configured use the GitHub App token instead. ::: --- @@ -261,7 +261,7 @@ oz integration update slack \ * `--host <WORKER_ID>` — update the execution host. :::note -For more details, see the dedicated pages for [Slack](/agent-platform/cloud-agents/integrations/slack/) and [Linear](/agent-platform/cloud-agents/integrations/linear/) integrations. +For more details, see the dedicated pages for [Slack](/platform/integrations/slack/) and [Linear](/platform/integrations/linear/) integrations. ::: ## How are environments used at runtime? @@ -297,7 +297,7 @@ You now have everything needed to trigger agents from your team's tools. From he **Additional reading** -* [Cloud Agents Overview](/agent-platform/cloud-agents/overview/) -* [Oz Platform](/agent-platform/cloud-agents/platform/) -* [Slack](/agent-platform/cloud-agents/integrations/slack/), [Linear](/agent-platform/cloud-agents/integrations/linear/), and [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) integrations +* [Cloud Agents Overview](/platform/) +* [Oz Platform](/platform/overview/) +* [Slack](/platform/integrations/slack/), [Linear](/platform/integrations/linear/), and [GitHub Actions](/platform/integrations/github-actions/) integrations * [Troubleshooting](/reference/cli/troubleshooting/) diff --git a/src/content/docs/reference/cli/mcp-servers.mdx b/src/content/docs/reference/cli/mcp-servers.mdx index e130fc7c5..e78ab3e21 100644 --- a/src/content/docs/reference/cli/mcp-servers.mdx +++ b/src/content/docs/reference/cli/mcp-servers.mdx @@ -9,7 +9,7 @@ sidebar: MCP servers connect agents to external systems like GitHub, Linear, or Sentry. To use a [Model Context Protocol (MCP)](/agent-platform/capabilities/mcp/) server from the CLI, use the `--mcp` flag with `oz agent run` or `oz agent run-cloud`. -For help choosing between local, cloud, and shared MCP workflows, see [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/). For a conceptual overview of MCP with cloud agents — including configuration schema, full agent config examples, and limitations — see [MCP Servers](/agent-platform/cloud-agents/mcp/) in the Cloud Agents docs. +For help choosing between local, cloud, and shared MCP workflows, see [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/). For a conceptual overview of MCP with cloud agents — including configuration schema, full agent config examples, and limitations — see [MCP Servers](/platform/mcp/) in the Cloud Agents docs. --- @@ -102,14 +102,14 @@ $ oz agent run --mcp "904a8936-fa82-4571-b1d6-166c26197981" --prompt "use my MCP ``` :::note -For cloud agent workflows, use [Oz-managed secrets](/agent-platform/cloud-agents/secrets/) to store and inject credentials safely — secrets are stored in the cloud and referenced by name in your config. For local runs, a secrets manager CLI such as [`op`](https://developer.1password.com/docs/cli/get-started/), [`pass`](https://www.passwordstore.org/), or [`gcloud secrets versions access`](https://cloud.google.com/secret-manager/docs/create-secret-quickstart#secretmanager-quickstart-gcloud) can fetch secrets on remote hosts without exposing them in your shell history. +For cloud agent workflows, use [Oz-managed secrets](/platform/secrets/) to store and inject credentials safely — secrets are stored in the cloud and referenced by name in your config. For local runs, a secrets manager CLI such as [`op`](https://developer.1password.com/docs/cli/get-started/), [`pass`](https://www.passwordstore.org/), or [`gcloud secrets versions access`](https://cloud.google.com/secret-manager/docs/create-secret-quickstart#secretmanager-quickstart-gcloud) can fetch secrets on remote hosts without exposing them in your shell history. ::: --- ## Learn more -* [MCP Servers (cloud agents)](/agent-platform/cloud-agents/mcp/) — configuration schema, full agent config file examples, and cloud agent limitations +* [MCP Servers (cloud agents)](/platform/mcp/) — configuration schema, full agent config file examples, and cloud agent limitations * [Model Context Protocol (MCP)](/agent-platform/capabilities/mcp/) — configuring MCP servers in Warp for local agents * [Connect developer tools to agents with MCP workflows](/guides/external-tools/using-mcp-servers-with-warp/) — choose the setup path for local sessions, cloud runs, team sharing, and repeatable automation -* [Secrets](/agent-platform/cloud-agents/secrets/) — store credentials in Warp so agents can access them at run time without exposing them in config files +* [Secrets](/platform/secrets/) — store credentials in Warp so agents can access them at run time without exposing them in config files diff --git a/src/content/docs/reference/cli/quickstart.mdx b/src/content/docs/reference/cli/quickstart.mdx index dadb219da..3950c22ae 100644 --- a/src/content/docs/reference/cli/quickstart.mdx +++ b/src/content/docs/reference/cli/quickstart.mdx @@ -39,7 +39,7 @@ Interactive login works on both **local** and **remote** machines, and does not export WARP_API_KEY="wk-..." ``` -Create an API key in the [Oz web app](https://oz.warp.dev/settings). See [API Keys](/reference/cli/api-keys/) for guidance on personal vs. [agent keys](/agent-platform/cloud-agents/agents/) and on security best practices. +Create an API key in the [Oz web app](https://oz.warp.dev/settings). See [API Keys](/reference/cli/api-keys/) for guidance on personal vs. [agent keys](/platform/agents/) and on security best practices. ::: ## 3. Run an agent @@ -62,7 +62,7 @@ What happens: Cloud agents run in a remote environment with your repositories cloned and dependencies installed, making them useful for tasks that need full codebase access. -If you haven't already created an environment, run `/create-environment` in Warp or follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/). Then run the following command: +If you haven't already created an environment, run `/create-environment` in Warp or follow the [Cloud Agents Quickstart](/platform/quickstart/). Then run the following command: ```sh oz agent run-cloud --environment <ENV_ID> --prompt "Scan this repo for outdated dependencies" @@ -89,6 +89,6 @@ Once you've successfully set up and run your agent, explore other configurations * Connect agents to external systems using [MCP Servers](/reference/cli/mcp-servers/). * Authenticate with [API keys](/reference/cli/api-keys/) for automated environments or workflows. * Get up-to-date information about the Oz CLI using the [`oz help` command](/reference/cli/troubleshooting/#getting-help). -* Run agents in CI with the [GitHub Actions quickstart](/agent-platform/cloud-agents/integrations/quickstart-github-actions/). +* Run agents in CI with the [GitHub Actions quickstart](/platform/integrations/quickstart-github-actions/). Continue reading the [Oz CLI reference](/reference/cli/) to learn how to install the CLI on different platforms, authenticate in different environments, and configure agents for real-world workflows. diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index fb1466555..b2a475dd8 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -294,7 +294,7 @@ For lighter-weight routing through any OpenAI-compatible endpoint (OpenRouter, L ### What features are available during multi-harness orchestration beta? -Multi-harness orchestration is currently in beta and available to all users. You can use the [Warp Agent](/agent-platform/cloud-agents/harnesses/warp-agent/) alongside [Claude Code](/agent-platform/cloud-agents/harnesses/claude-code/) and [Codex](/agent-platform/cloud-agents/harnesses/codex/) in Oz cloud environments, and mix and match harnesses across workflows. +Multi-harness orchestration is currently in beta and available to all users. You can use the [Warp Agent](/platform/harnesses/warp-agent/) alongside [Claude Code](/platform/harnesses/claude-code/) and [Codex](/platform/harnesses/codex/) in Oz cloud environments, and mix and match harnesses across workflows. [Agent Memory](/agent-platform/agent-memory/) is currently in Research Preview. It lets preferences, project knowledge, and learnings from past sessions carry across harnesses and future agent runs. [Contact our sales team](https://www.warp.dev/contact-sales) to request access. diff --git a/src/content/docs/terminal/windows/configurable-toolbar.mdx b/src/content/docs/terminal/windows/configurable-toolbar.mdx index 892e5605d..8ce9e7141 100644 --- a/src/content/docs/terminal/windows/configurable-toolbar.mdx +++ b/src/content/docs/terminal/windows/configurable-toolbar.mdx @@ -26,7 +26,7 @@ The following header buttons can be rearranged or hidden: * **Tabs panel** - Toggles the [vertical tabs](/terminal/windows/vertical-tabs/) sidebar. * **Tools panel** - Toggles the panel that contains the project explorer, global search, [Warp Drive](/knowledge-and-collaboration/warp-drive/), and conversation history. -* **Agent management** - Toggles the agent management view for [cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/). +* **Agent management** - Toggles the agent management view for [cloud agents](/platform/managing-cloud-agents/). * **Code review** - Toggles the [Code Review](/code/code-review/) panel. * **Notifications mailbox** - Toggles the [agent notifications](/agent-platform/capabilities/agent-notifications/) mailbox. @@ -71,5 +71,5 @@ When multiple panels are open on the same side, they render in the order their b * [Vertical tabs](/terminal/windows/vertical-tabs/) - The sidebar toggled by the tabs panel button. * [Code Review panel](/code/code-review/) - The panel toggled by the code review button. * [Agent notifications](/agent-platform/capabilities/agent-notifications/) - The mailbox toggled by the notifications button. -* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - The view toggled by the agent management button. +* [Managing cloud agents](/platform/managing-cloud-agents/) - The view toggled by the agent management button. * [Warp Drive](/knowledge-and-collaboration/warp-drive/) - One of the views available in the tools panel. diff --git a/src/sidebar.ts b/src/sidebar.ts index 4cfca791f..0f6862ff4 100644 --- a/src/sidebar.ts +++ b/src/sidebar.ts @@ -325,105 +325,137 @@ export const sidebarTopics: StarlightSidebarTopicsUserConfig = [ ], }, { - label: 'Oz Cloud Agents & Orchestration', + label: 'Memory (Research Preview)', items: [ - { slug: 'agent-platform/cloud-agents/overview', label: 'Cloud agents overview' }, - { slug: 'agent-platform/cloud-agents/quickstart', label: 'Quickstart' }, - { slug: 'agent-platform/cloud-agents/platform', label: 'Oz platform' }, - { - label: 'Triggers', - collapsed: true, - items: [ - { slug: 'agent-platform/cloud-agents/triggers', label: 'Overview' }, - { slug: 'agent-platform/cloud-agents/triggers/scheduled-agents-quickstart', label: 'Quickstart' }, - { slug: 'agent-platform/cloud-agents/triggers/scheduled-agents', label: 'Scheduled agents' }, - ], - }, - { - label: 'Integrations', - collapsed: true, - items: [ - { slug: 'agent-platform/cloud-agents/integrations', label: 'Overview' }, - { slug: 'agent-platform/cloud-agents/integrations/quickstart', label: 'Quickstart' }, - 'agent-platform/cloud-agents/integrations/slack', - 'agent-platform/cloud-agents/integrations/linear', - { - label: 'GitHub Actions', - collapsed: true, - items: [ - { slug: 'agent-platform/cloud-agents/integrations/github-actions', label: 'Overview' }, - { slug: 'agent-platform/cloud-agents/integrations/quickstart-github-actions', label: 'Quickstart' }, - ], - }, - 'agent-platform/cloud-agents/integrations/azure-devops', - 'agent-platform/cloud-agents/integrations/bitbucket', - 'agent-platform/cloud-agents/integrations/gitlab', - { slug: 'agent-platform/cloud-agents/integrations/cloud-providers', label: 'AWS, GCP, and other cloud providers' }, - ], - }, - 'agent-platform/cloud-agents/environments', - { slug: 'agent-platform/cloud-agents/managing-cloud-agents', label: 'Managing cloud agents' }, - { - label: 'Orchestration', - collapsed: true, - items: [ - { slug: 'agent-platform/cloud-agents/orchestration', label: 'Multi-agent orchestration' }, - { slug: 'agent-platform/cloud-agents/orchestration/multi-agent-runs', label: 'Running orchestrated agents' }, - ], - }, - { slug: 'agent-platform/cloud-agents/agents', label: 'Agents' }, - { slug: 'agent-platform/cloud-agents/oz-web-app', label: 'Oz web app' }, - { slug: 'agent-platform/cloud-agents/skills-as-agents', label: 'Skills as agents' }, - { slug: 'agent-platform/cloud-agents/viewing-cloud-agent-runs', label: 'Viewing cloud agent runs' }, - { - label: 'Handoff', - collapsed: true, - items: [ - { slug: 'agent-platform/cloud-agents/handoff', label: 'Overview' }, - { slug: 'agent-platform/cloud-agents/handoff/local-to-cloud', label: 'Local to cloud' }, - { slug: 'agent-platform/cloud-agents/handoff/cloud-to-cloud', label: 'Cloud to cloud' }, - { slug: 'agent-platform/cloud-agents/handoff/snapshots', label: 'Snapshots' }, - ], - }, - 'agent-platform/cloud-agents/secrets', + { slug: 'agent-platform/agent-memory', label: 'Agent Memory' }, + ], + }, + ], + }, + { + label: 'Oz', + link: '/platform/', + icon: 'cloud-download', + items: [ + { slug: 'platform', label: 'Cloud agents overview' }, + { + label: 'Getting started', + collapsed: true, + items: [ + { slug: 'platform/quickstart', label: 'Quickstart' }, + { slug: 'platform/overview', label: 'Oz platform' }, + ], + }, + { + label: 'Triggers', + collapsed: true, + items: [ + { slug: 'platform/triggers', label: 'Overview' }, + { slug: 'platform/triggers/scheduled-agents-quickstart', label: 'Quickstart' }, + { slug: 'platform/triggers/scheduled-agents', label: 'Scheduled agents' }, + ], + }, + { + label: 'Integrations', + collapsed: true, + items: [ + { slug: 'platform/integrations', label: 'Overview' }, + { slug: 'platform/integrations/quickstart', label: 'Quickstart' }, + 'platform/integrations/slack', + 'platform/integrations/linear', { - label: 'Harnesses', + label: 'GitHub Actions', collapsed: true, items: [ - { slug: 'agent-platform/cloud-agents/harnesses', label: 'Overview' }, - { slug: 'agent-platform/cloud-agents/harnesses/warp-agent', label: 'Warp Agent' }, - { slug: 'agent-platform/cloud-agents/harnesses/claude-code', label: 'Claude Code' }, - { slug: 'agent-platform/cloud-agents/harnesses/codex', label: 'Codex' }, - { slug: 'agent-platform/cloud-agents/harnesses/authentication', label: 'Authentication' }, + { slug: 'platform/integrations/github-actions', label: 'Overview' }, + { slug: 'platform/integrations/quickstart-github-actions', label: 'Quickstart' }, ], }, - { slug: 'agent-platform/cloud-agents/mcp', label: 'MCP servers' }, - { slug: 'agent-platform/cloud-agents/deployment-patterns', label: 'Deployment patterns' }, - { slug: 'agent-platform/cloud-agents/warp-hosting', label: 'Warp-hosted agents' }, + 'platform/integrations/azure-devops', + 'platform/integrations/bitbucket', + 'platform/integrations/gitlab', + { slug: 'platform/integrations/cloud-providers', label: 'AWS, GCP, and other cloud providers' }, + ], + }, + { + label: 'Managing agents', + collapsed: true, + items: [ + 'platform/environments', + { slug: 'platform/managing-cloud-agents', label: 'Managing cloud agents' }, + { slug: 'platform/agents', label: 'Agents' }, + { slug: 'platform/viewing-cloud-agent-runs', label: 'Viewing cloud agent runs' }, + { slug: 'platform/oz-web-app', label: 'Oz web app' }, + ], + }, + { + label: 'Orchestration', + collapsed: true, + items: [ + { slug: 'platform/orchestration', label: 'Multi-agent orchestration' }, + { slug: 'platform/orchestration/multi-agent-runs', label: 'Running orchestrated agents' }, + ], + }, + { + label: 'Handoff', + collapsed: true, + items: [ + { slug: 'platform/handoff', label: 'Overview' }, + { slug: 'platform/handoff/local-to-cloud', label: 'Local to cloud' }, + { slug: 'platform/handoff/cloud-to-cloud', label: 'Cloud to cloud' }, + { slug: 'platform/handoff/snapshots', label: 'Snapshots' }, + ], + }, + { + label: 'Harnesses', + collapsed: true, + items: [ + { slug: 'platform/harnesses', label: 'Overview' }, + { slug: 'platform/harnesses/warp-agent', label: 'Warp Agent' }, + { slug: 'platform/harnesses/claude-code', label: 'Claude Code' }, + { slug: 'platform/harnesses/codex', label: 'Codex' }, + { slug: 'platform/harnesses/authentication', label: 'Authentication' }, + ], + }, + { + label: 'Extending agents', + collapsed: true, + items: [ + { slug: 'platform/skills-as-agents', label: 'Skills as agents' }, + { slug: 'platform/mcp', label: 'MCP servers' }, + 'platform/secrets', + ], + }, + { + label: 'Deployment & hosting', + collapsed: true, + items: [ + { slug: 'platform/deployment-patterns', label: 'Deployment patterns' }, + { slug: 'platform/warp-hosting', label: 'Warp-hosted agents' }, { label: 'Self-hosting', collapsed: true, items: [ - { slug: 'agent-platform/cloud-agents/self-hosting', label: 'Overview' }, - { slug: 'agent-platform/cloud-agents/self-hosting/quickstart', label: 'Quickstart' }, - { slug: 'agent-platform/cloud-agents/self-hosting/managed-docker', label: 'Managed: Docker' }, - { slug: 'agent-platform/cloud-agents/self-hosting/managed-kubernetes', label: 'Managed: Kubernetes' }, - { slug: 'agent-platform/cloud-agents/self-hosting/managed-direct', label: 'Managed: Direct' }, - { slug: 'agent-platform/cloud-agents/self-hosting/unmanaged', label: 'Unmanaged' }, - 'agent-platform/cloud-agents/self-hosting/monitoring', - { slug: 'agent-platform/cloud-agents/self-hosting/reference', label: 'Self-hosted worker reference' }, - 'agent-platform/cloud-agents/self-hosting/security-and-networking', - { slug: 'agent-platform/cloud-agents/self-hosting/troubleshooting', label: 'Troubleshooting' }, + { slug: 'platform/self-hosting', label: 'Overview' }, + { slug: 'platform/self-hosting/quickstart', label: 'Quickstart' }, + { slug: 'platform/self-hosting/managed-docker', label: 'Managed: Docker' }, + { slug: 'platform/self-hosting/managed-kubernetes', label: 'Managed: Kubernetes' }, + { slug: 'platform/self-hosting/managed-direct', label: 'Managed: Direct' }, + { slug: 'platform/self-hosting/unmanaged', label: 'Unmanaged' }, + 'platform/self-hosting/monitoring', + { slug: 'platform/self-hosting/reference', label: 'Self-hosted worker reference' }, + 'platform/self-hosting/security-and-networking', + { slug: 'platform/self-hosting/troubleshooting', label: 'Troubleshooting' }, ], }, - { slug: 'agent-platform/cloud-agents/team-access-billing-and-identity', label: 'Access, billing, and identity' }, - { slug: 'agent-platform/cloud-agents/faqs', label: 'Cloud agent FAQs' }, ], }, { - label: 'Memory (Research Preview)', + label: 'Access & support', + collapsed: true, items: [ - { slug: 'agent-platform/agent-memory', label: 'Agent Memory' }, + { slug: 'platform/team-access-billing-and-identity', label: 'Access, billing, and identity' }, + { slug: 'platform/faqs', label: 'Cloud agent FAQs' }, ], }, ], diff --git a/src/styles/warp-components.css b/src/styles/warp-components.css index ff81c8240..0e15a39ce 100644 --- a/src/styles/warp-components.css +++ b/src/styles/warp-components.css @@ -472,6 +472,21 @@ header.header { transition: background-color 0.2s ease; } +/* Reserve header height for a wrapped second row of topic tabs on crowded + mid-width viewports. The desktop topic nav (WarpTopicNav.astro) wraps + instead of clipping; the header is a fixed-height bar whose height + (`--sl-nav-height`) also drives the sidebar and main-content offsets + (see Starlight PageFrame), so bumping the variable across the wrap-prone + range keeps a second row from overlapping the page content below. The + desktop nav shows at >=50rem and per-item icons drop at <=80rem; above + 80rem the tabs fit on one row, and below 50rem the mobile drawer takes + over (this nav is hidden). */ +@media (min-width: 50rem) and (max-width: 80rem) { + :root { + --sl-nav-height: 5rem; + } +} + /* -------------------------------------------------------------------------- 6. Topic tab hover — full-row highlight instead of just icon fill These rules style the plugin-rendered topic list (`<ul.starlight-sidebar-topics>`). diff --git a/vercel.json b/vercel.json index df0df793b..deb9e20d1 100644 --- a/vercel.json +++ b/vercel.json @@ -207,7 +207,7 @@ }, { "source": "/agent-platform/agent-mode/ambient-agents-session-sharing", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { @@ -332,7 +332,7 @@ }, { "source": "/agent-platform/agent-platform/ambient-agents/ambient-agents-overview", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { @@ -352,12 +352,12 @@ }, { "source": "/agent-platform/agent-platform/cloud-agents/cloud-agents-platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { "source": "/agent-platform/agent-platform/cloud-agents/warp-platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -382,12 +382,12 @@ }, { "source": "/agent-platform/agent-platform/integrations/github-actions/readme", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/agent-platform/agent-platform/integrations/integrations-overview", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { @@ -492,12 +492,12 @@ }, { "source": "/agent-platform/agent-platform/using-agents/managing-agents", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { "source": "/agent-platform/agent-platform/using-agents/managing-agents#in-app-agent-notifications", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -682,7 +682,7 @@ }, { "source": "/agent-platform/agents/using-agents/managing-agents", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -747,27 +747,27 @@ }, { "source": "/agent-platform/ambient-agents", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/agent-secrets", - "destination": "/agent-platform/cloud-agents/secrets/", + "destination": "/platform/secrets/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/ambient-agents-overview", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/managing-ambient-agents", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/managing-ambient-agents/scheduled-agents", - "destination": "/agent-platform/cloud-agents/triggers/scheduled-agents/", + "destination": "/platform/triggers/scheduled-agents/", "statusCode": 308 }, { @@ -777,62 +777,62 @@ }, { "source": "/agent-platform/cloud-agents/cloud-agent-secrets", - "destination": "/agent-platform/cloud-agents/secrets/", + "destination": "/platform/secrets/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-faqs", - "destination": "/agent-platform/cloud-agents/faqs/", + "destination": "/platform/faqs/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-overview", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-session-sharing", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference", - "destination": "/agent-platform/cloud-agents/self-hosting/reference/", + "destination": "/platform/self-hosting/reference/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/direct-backend", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-direct/", + "destination": "/platform/self-hosting/managed-direct/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/docker-connectivity", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-docker/", + "destination": "/platform/self-hosting/managed-docker/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/helm-chart", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-kubernetes/", + "destination": "/platform/self-hosting/managed-kubernetes/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/kubernetes-backend", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-kubernetes/", + "destination": "/platform/self-hosting/managed-kubernetes/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/private-docker-registries", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-docker/", + "destination": "/platform/self-hosting/managed-docker/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/warp-platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -1137,47 +1137,47 @@ }, { "source": "/agent-platform/integrations", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/integrations-overview", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/integrations/github-actions", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/agent-platform/integrations/github-actions/demo-issue-triage-bot", - "destination": "/agent-platform/cloud-agents/integrations/quickstart-github-actions/", + "destination": "/platform/integrations/quickstart-github-actions/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/integrations/demo-issue-triage-bot", - "destination": "/agent-platform/cloud-agents/integrations/quickstart-github-actions/", + "destination": "/platform/integrations/quickstart-github-actions/", "statusCode": 308 }, { "source": "/agent-platform/integrations/integrations-overview", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/integrations/integrations-overview/team-access-billing-and-identity-permissions", - "destination": "/agent-platform/cloud-agents/team-access-billing-and-identity/", + "destination": "/platform/team-access-billing-and-identity/", "statusCode": 308 }, { "source": "/agent-platform/integrations/linear", - "destination": "/agent-platform/cloud-agents/integrations/linear/", + "destination": "/platform/integrations/linear/", "statusCode": 308 }, { "source": "/agent-platform/integrations/slack", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -1197,7 +1197,7 @@ }, { "source": "/agent-platform/knowledge-and-collaboration/session-sharing/ambient-agents-session-sharing", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { @@ -1222,7 +1222,7 @@ }, { "source": "/agent-platform/local-agents/ambient-agents-session-sharing", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { @@ -1252,32 +1252,32 @@ }, { "source": "/agent-platform/platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { "source": "/agent-platform/platform/deployment-patterns", - "destination": "/agent-platform/cloud-agents/deployment-patterns/", + "destination": "/platform/deployment-patterns/", "statusCode": 308 }, { "source": "/agent-platform/platform/environments", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/agent-platform/platform/integrations/integrations-overview", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/platform/team-access-billing-and-identity-permissions", - "destination": "/agent-platform/cloud-agents/team-access-billing-and-identity/", + "destination": "/platform/team-access-billing-and-identity/", "statusCode": 308 }, { "source": "/agent-platform/platform/warp-platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -1337,7 +1337,7 @@ }, { "source": "/agent-platform/using-agents/managing-agents", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -1492,7 +1492,7 @@ }, { "source": "/agent-platform/warp-platform", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -3892,7 +3892,7 @@ }, { "source": "/university/warp-runtime/building-a-slackbot", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -4022,7 +4022,7 @@ }, { "source": "/agent-platform/cloud-agents/integrations/github-actions/quickstart-github-actions", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { @@ -4137,7 +4137,7 @@ }, { "source": "/guides/build-an-app-in-warp/building-a-slackbot", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -4362,7 +4362,7 @@ }, { "source": "/agents/using-agents/managing-agents", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -4372,12 +4372,12 @@ }, { "source": "/ambient-agents/ambient-agents-overview", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/ambient-agents/managing-ambient-agents", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -4597,7 +4597,7 @@ }, { "source": "/agent-platform/agent-mode/ambient-agents-session-sharing/", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { @@ -4707,7 +4707,7 @@ }, { "source": "/agent-platform/agent-platform/ambient-agents/ambient-agents-overview/", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { @@ -4727,12 +4727,12 @@ }, { "source": "/agent-platform/agent-platform/cloud-agents/cloud-agents-platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { "source": "/agent-platform/agent-platform/cloud-agents/warp-platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -4752,12 +4752,12 @@ }, { "source": "/agent-platform/agent-platform/integrations/github-actions/readme/", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/agent-platform/agent-platform/integrations/integrations-overview/", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { @@ -4832,7 +4832,7 @@ }, { "source": "/agent-platform/agent-platform/using-agents/managing-agents/", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -5002,7 +5002,7 @@ }, { "source": "/agent-platform/agents/using-agents/managing-agents/", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -5067,27 +5067,27 @@ }, { "source": "/agent-platform/ambient-agents/", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/agent-secrets/", - "destination": "/agent-platform/cloud-agents/secrets/", + "destination": "/platform/secrets/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/ambient-agents-overview/", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/managing-ambient-agents/", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { "source": "/agent-platform/ambient-agents/managing-ambient-agents/scheduled-agents/", - "destination": "/agent-platform/cloud-agents/triggers/scheduled-agents/", + "destination": "/platform/triggers/scheduled-agents/", "statusCode": 308 }, { @@ -5097,32 +5097,32 @@ }, { "source": "/agent-platform/cloud-agents/cloud-agent-secrets/", - "destination": "/agent-platform/cloud-agents/secrets/", + "destination": "/platform/secrets/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-faqs/", - "destination": "/agent-platform/cloud-agents/faqs/", + "destination": "/platform/faqs/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-overview/", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/cloud-agents-session-sharing/", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/warp-platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -5422,47 +5422,47 @@ }, { "source": "/agent-platform/integrations/", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/integrations-overview/", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/integrations/github-actions/", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/agent-platform/integrations/github-actions/demo-issue-triage-bot/", - "destination": "/agent-platform/cloud-agents/integrations/quickstart-github-actions/", + "destination": "/platform/integrations/quickstart-github-actions/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/integrations/demo-issue-triage-bot/", - "destination": "/agent-platform/cloud-agents/integrations/quickstart-github-actions/", + "destination": "/platform/integrations/quickstart-github-actions/", "statusCode": 308 }, { "source": "/agent-platform/integrations/integrations-overview/", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/integrations/integrations-overview/team-access-billing-and-identity-permissions/", - "destination": "/agent-platform/cloud-agents/team-access-billing-and-identity/", + "destination": "/platform/team-access-billing-and-identity/", "statusCode": 308 }, { "source": "/agent-platform/integrations/linear/", - "destination": "/agent-platform/cloud-agents/integrations/linear/", + "destination": "/platform/integrations/linear/", "statusCode": 308 }, { "source": "/agent-platform/integrations/slack/", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -5482,7 +5482,7 @@ }, { "source": "/agent-platform/knowledge-and-collaboration/session-sharing/ambient-agents-session-sharing/", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { @@ -5507,7 +5507,7 @@ }, { "source": "/agent-platform/local-agents/ambient-agents-session-sharing/", - "destination": "/agent-platform/cloud-agents/viewing-cloud-agent-runs/", + "destination": "/platform/viewing-cloud-agent-runs/", "statusCode": 308 }, { @@ -5527,32 +5527,32 @@ }, { "source": "/agent-platform/platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { "source": "/agent-platform/platform/deployment-patterns/", - "destination": "/agent-platform/cloud-agents/deployment-patterns/", + "destination": "/platform/deployment-patterns/", "statusCode": 308 }, { "source": "/agent-platform/platform/environments/", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/agent-platform/platform/integrations/integrations-overview/", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/agent-platform/platform/team-access-billing-and-identity-permissions/", - "destination": "/agent-platform/cloud-agents/team-access-billing-and-identity/", + "destination": "/platform/team-access-billing-and-identity/", "statusCode": 308 }, { "source": "/agent-platform/platform/warp-platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -5612,7 +5612,7 @@ }, { "source": "/agent-platform/using-agents/managing-agents/", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -5632,7 +5632,7 @@ }, { "source": "/agent-platform/warp-platform/", - "destination": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", "statusCode": 308 }, { @@ -7687,7 +7687,7 @@ }, { "source": "/agent-platform/cloud-agents/integrations/github-actions/quickstart-github-actions/", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { @@ -7802,7 +7802,7 @@ }, { "source": "/guides/build-an-app-in-warp/building-a-slackbot/", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -8022,7 +8022,7 @@ }, { "source": "/agents/using-agents/managing-agents/", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -8032,12 +8032,12 @@ }, { "source": "/ambient-agents/ambient-agents-overview/", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { "source": "/ambient-agents/managing-ambient-agents/", - "destination": "/agent-platform/cloud-agents/managing-cloud-agents/", + "destination": "/platform/managing-cloud-agents/", "statusCode": 308 }, { @@ -8132,32 +8132,32 @@ }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/", - "destination": "/agent-platform/cloud-agents/self-hosting/reference/", + "destination": "/platform/self-hosting/reference/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/direct-backend/", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-direct/", + "destination": "/platform/self-hosting/managed-direct/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/docker-connectivity/", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-docker/", + "destination": "/platform/self-hosting/managed-docker/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/helm-chart/", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-kubernetes/", + "destination": "/platform/self-hosting/managed-kubernetes/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/kubernetes-backend/", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-kubernetes/", + "destination": "/platform/self-hosting/managed-kubernetes/", "statusCode": 308 }, { "source": "/agent-platform/cloud-agents/managed-worker-reference/private-docker-registries/", - "destination": "/agent-platform/cloud-agents/self-hosting/managed-docker/", + "destination": "/platform/self-hosting/managed-docker/", "statusCode": 308 }, { @@ -8212,7 +8212,7 @@ }, { "source": "/platform/environments", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { @@ -8302,7 +8302,7 @@ }, { "source": "/integrations/integrations-overview", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { @@ -8377,12 +8377,12 @@ }, { "source": "/ambient-agents/agent-secrets", - "destination": "/agent-platform/cloud-agents/secrets/", + "destination": "/platform/secrets/", "statusCode": 308 }, { "source": "/integrations/slack", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -8402,7 +8402,7 @@ }, { "source": "/integrations/github-actions", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { @@ -8442,12 +8442,12 @@ }, { "source": "/integrations/linear", - "destination": "/agent-platform/cloud-agents/integrations/linear/", + "destination": "/platform/integrations/linear/", "statusCode": 308 }, { "source": "/platform/cli/integrations-and-environments", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { @@ -8472,7 +8472,7 @@ }, { "source": "/ambient-agents/mcp-servers-for-agents", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { @@ -8517,7 +8517,7 @@ }, { "source": "/platform/deployment-patterns", - "destination": "/agent-platform/cloud-agents/deployment-patterns/", + "destination": "/platform/deployment-patterns/", "statusCode": 308 }, { @@ -8567,7 +8567,7 @@ }, { "source": "/agent-platform/cloud-agents/self-hosting/managed-worker-reference", - "destination": "/agent-platform/cloud-agents/self-hosting/", + "destination": "/platform/self-hosting/", "statusCode": 308 }, { @@ -8597,7 +8597,7 @@ }, { "source": "/integrations/github-actions/demo-issue-triage-bot", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { @@ -8792,7 +8792,7 @@ }, { "source": "/agent-platform/cloud-agents-and-orchestration/team-access-billing-and-identity", - "destination": "/agent-platform/cloud-agents/team-access-billing-and-identity/", + "destination": "/platform/team-access-billing-and-identity/", "statusCode": 308 }, { @@ -9272,87 +9272,87 @@ }, { "source": "/integrations/github-actions#id-1.-responding-to-comments-with-mentions", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/integrations/github-actions#id-2.-automated-pull-request-review", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/integrations/github-actions#id-3.-automatically-fix-issues", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/integrations/github-actions#quickstart", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/integrations/github-actions#requirements", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/integrations/github-actions#what-the-github-actions-integration-does", - "destination": "/agent-platform/cloud-agents/integrations/github-actions/", + "destination": "/platform/integrations/github-actions/", "statusCode": 308 }, { "source": "/integrations/integrations-and-plugins", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/integrations/linear#how-to-configure-the-integration", - "destination": "/agent-platform/cloud-agents/integrations/linear/", + "destination": "/platform/integrations/linear/", "statusCode": 308 }, { "source": "/integrations/linear#requirements", - "destination": "/agent-platform/cloud-agents/integrations/linear/", + "destination": "/platform/integrations/linear/", "statusCode": 308 }, { "source": "/integrations/linear#using-warp-inside-linear", - "destination": "/agent-platform/cloud-agents/integrations/linear/", + "destination": "/platform/integrations/linear/", "statusCode": 308 }, { "source": "/integrations/slack#joining-the-live-remote-session", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { "source": "/integrations/slack#monitoring-agent-progress", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { "source": "/integrations/slack#overview", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { "source": "/integrations/slack#pull-requests-and-output", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { "source": "/integrations/slack#requirements", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { "source": "/integrations/slack#triggering-an-agent", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { "source": "/integrations/slack#using-warp-inside-slack", - "destination": "/agent-platform/cloud-agents/integrations/slack/", + "destination": "/platform/integrations/slack/", "statusCode": 308 }, { @@ -9477,67 +9477,67 @@ }, { "source": "/platform/cli/integrations-and-environments#how-integrations-and-environments-work", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/platform/cli/integrations-and-environments#option-1-guided-environment-setup-recommended", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/platform/cli/integrations-and-environments#option-2-create-an-environment-with-the-cli", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/platform/cli/integrations-and-environments#step-1-creating-an-environment", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/platform/cli/integrations-and-environments#step-2-authorizing-github", - "destination": "/agent-platform/cloud-agents/integrations/", + "destination": "/platform/integrations/", "statusCode": 308 }, { "source": "/platform/environments#about-environments", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#create-an-environment-with-guided-setup-recommended", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#hosts-and-environments", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#how-environments-fit-into-the-warp-platform", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#key-features", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#what-happens-at-runtime", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#when-to-use-environments", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { "source": "/platform/environments#where-to-configure-environments", - "destination": "/agent-platform/cloud-agents/environments/", + "destination": "/platform/environments/", "statusCode": 308 }, { @@ -9637,7 +9637,7 @@ }, { "source": "/oz", - "destination": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", "statusCode": 308 }, { @@ -9864,6 +9864,46 @@ "source": "/help/licenses/", "destination": "/support-and-community/community/open-source-licenses/", "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/overview", + "destination": "/platform/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/overview/", + "destination": "/platform/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/platform", + "destination": "/platform/overview/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/platform/", + "destination": "/platform/overview/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents", + "destination": "/platform/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/", + "destination": "/platform/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/:path*/", + "destination": "/platform/:path*/", + "statusCode": 308 + }, + { + "source": "/agent-platform/cloud-agents/:path*", + "destination": "/platform/:path*/", + "statusCode": 308 } ] }