Skip to content

docs: add AEO cross-links for agents and orchestration #183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
rachaelrenk wants to merge 2 commits into from
Closed

docs: add AEO cross-links for agents and orchestration #183

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9781c68
docs: add AEO cross-links for agents and orchestration
rachaelrenk Jun 5, 2026
efae6f2
Merge branch 'main' into docs/aeo-crosslinks-agents-orchestration-2
rachaelrenk Jun 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/content/docs/agent-platform/capabilities/planning.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,3 +113,4 @@ As the agent executes your plan, you'll review code changes and may want to scal

* **[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.
* **[Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)** - When `/plan` detects that a task benefits from parallel work, it proposes an orchestration config that spawns child agents to divide the work.
Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Clarify that /plan proposes orchestration for approval before child agents launch.

Suggested change
* **[Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)** - When `/plan` detects that a task benefits from parallel work, it proposes an orchestration config that spawns child agents to divide the work.
* **[Multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)** - When a `/plan` task benefits from parallel work, the agent can propose an orchestration config for you to approve before child agents divide the work.

2 changes: 1 addition & 1 deletion src/content/docs/agent-platform/cloud-agents/environments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Components in the execution flow:
2. **Task** – Warp creates a tracked task for the run
3. **Environment** – The task uses an environment to define execution context
4. **Host** – The environment runs on a host (Warp-hosted or self-hosted infrastructure).
5. **Agent execution** – The workflow runs in the prepared environment
5. **Agent execution** – The workflow runs in the prepared environment. In [orchestrated runs](/agent-platform/cloud-agents/orchestration/), each child agent gets its own environment so that parallel agents are isolated from each other.
Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [IMPORTANT] This contradicts the orchestration docs' Cloud → cloud-local mode, where children run inside the parent's cloud environment instead of getting separate environments.

Suggested change
5. **Agent execution** – The workflow runs in the prepared environment. In [orchestrated runs](/agent-platform/cloud-agents/orchestration/), each child agent gets its own environment so that parallel agents are isolated from each other.
5. **Agent execution** – The workflow runs in the prepared environment. In [orchestrated cloud runs](/agent-platform/cloud-agents/orchestration/), child agents can run in separate environments for isolation or inside the parent's cloud environment when they need shared state.

6. **Outputs** – The run produces PRs, messages, reports, or transcripts

:::note
Expand Down
1 change: 1 addition & 0 deletions src/content/docs/agent-platform/cloud-agents/harnesses/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ 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/).
* **Skills and Rules** — Saved [Skills](/agent-platform/capabilities/skills/) and [Rules](/agent-platform/capabilities/rules/) apply across harnesses.
* **Orchestration** — A parent agent running one harness can spawn child agents that run a [different harness](/agent-platform/cloud-agents/orchestration/#where-parent-and-child-agents-can-run).
* **Observability** — Every run produces a transcript and shareable session in the [Oz dashboard](/agent-platform/cloud-agents/managing-cloud-agents/).

## Billing
Expand Down
2 changes: 1 addition & 1 deletion src/content/docs/agent-platform/getting-started/agents-in-warp.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ The same agent capabilities that power interactive conversations in Warp also ru

* React to events from Slack, Linear, or GitHub
* Run on schedules for recurring tasks like dependency updates
* Execute in parallel across repos or tasks
* Execute in parallel across repos or tasks using [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/)
* Produce tracked, auditable, shareable runs

Cloud agents are ideal for work that doesn't need your immediate attention—PR reviews, issue triage, routine maintenance, and integration-driven workflows.
Expand Down
Loading