update README: orchestration modes#6
Conversation
|
|
||
| ## MCP Server Tools and Orchestration Modes | ||
|
|
||
| CAO provides a local HTTP server that processes orchestration requests. CLI agents can interact with this server through MCP tools to coordinate multi-agent workflows. |
There was a problem hiding this comment.
NIT: We can add a note here to explicitly allowlist MCP tools for orchestration, its not clear from examples.
| ← send_message("E2E tests passed") ← Tester 3 | ||
| ``` | ||
|
|
||
| **3. Send Message** - Communicate with an existing agent |
There was a problem hiding this comment.
Do you want to note that SendMsg by default is handled by subagents through the use of MCP. (So need to explicitly add this in subagent prompt unless you need intermediate/continuous message transfer).
There was a problem hiding this comment.
send_message is a tool that can be used by both orchestrators and subagents. The key difference is that the receiver agent must already be running and the sender agent must know the receiver's terminal_id
gokulanv
left a comment
There was a problem hiding this comment.
Change looks good to merge. Nit doc comments, which I can also address later.
|
Also just noticed that there are 5 commits in PR. You might want to squash them into one. |
Yes, the default merge for this repo is Squash merge. |
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.