Skip to content

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

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 1 commit into from
+3 −3
Closed

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions src/content/docs/agent-platform/cloud-agents/faqs.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ To learn more about how secrets work in practice, see [Cloud Agent Secrets](/age

The cloud agents platform is intentionally flexible. As the developer, you decide how agents should branch, coordinate, and resolve conflicts.

Interactive agents can plan work and spawn subagents to parallelize tasks. Cloud agents provide the building blocks for running and coordinating multiple concurrent agents, rather than enforcing a fixed workflow.
Interactive agents can plan work and spawn subagents to parallelize tasks. Cloud agents provide the building blocks for [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/), running and coordinating multiple concurrent agents, rather than enforcing a fixed workflow.

### Why focus on orchestration primitives instead of immediately adopting new agent standards?

Expand Down Expand Up @@ -168,7 +168,7 @@ Agents are strongest when they can continuously validate progress (tests, lint,

Yes. A common cloud agent workflow:

- When a ticket/issue is created (via integration trigger), a cloud agent gathers context (recent changes, logs/metrics links, ownership).
- When a ticket/issue is created (via an [integration trigger](/agent-platform/cloud-agents/integrations/)), a cloud agent gathers context (recent changes, logs/metrics links, ownership).
- Proposes labels/priority and likely causes.
- Drafts next steps or a response.
- Asks clarifying questions back to the reporter when needed.
Expand All @@ -182,7 +182,7 @@ Yes. Scheduled dependency bumps are a classic cloud agent use case:
- Resolve simple conflicts.
- Attach a risk summary (optional).

This is usually implemented as a scheduled **cloud agent** producing recurring **runs**.
This is usually implemented as a [scheduled cloud agent](/agent-platform/cloud-agents/triggers/scheduled-agents/) producing recurring **runs**.

### Can cloud agents keep docs up to date?

Expand Down
Loading