automation
Manage durable recurring session automations through the daemon API.
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
$ npx -y skills add OrchestratorInc/agent-orchestrator --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/sendContext preview
What this command does when you run it.
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
ao send [flags]
| Flag | Meaning | Default / Required | |---|---|---| | `--message string` | Message body | Required unless `--recover-only` | | `--session string` | Session id | Required | | `--steer` | Add guidance to the active Chat turn, or start a normal turn when idle | Optional | | `--client-message-id string` | Stable delivery handle for steering and safe retries | Generated automatically with `--steer` | | `--recover-only` | Recover the outcome for an existing delivery handle without resending | Requires `--steer` and `--client-message-id` |
`--steer` uses one atomic daemon operation. If the session has an active Chat turn, the message is added to that turn. If the session is idle, the message starts a normal Chat turn. The state cannot change between those decisions and leave the message queued as a separate correction.
Every steering request has a client message id. Supply one explicitly when a caller must retain the handle across retries:
ao send --session mer-3 --steer --client-message-id correction-42 --message "Focus only on the backend."
If the command reports an uncertain outcome or a transport failure, preserve the delivery handle printed in the error. Recover the existing result without contacting the provider again:
ao send --session mer-3 --steer --recover-only --client-message-id correction-42
Do not invent a new client message id after an uncertain result. Reusing the original id lets the daemon return the durable steering receipt or normal turn without delivering the message twice. Recovery confirms the recorded delivery outcome, not that the agent acted on the guidance.
# Send a correction to a running session ao send --session mer-3 --message "Focus only on the backend; ignore frontend files."
# Give the agent new instructions mid-task ao send --session mer-3 --message "The issue is in session_manager.go line 142, not in the CLI. Investigate there."
# Steer the active Chat turn, or start a normal turn if it is idle ao send --session mer-3 --steer --message "Use the daemon DTO as the source of truth."
Run and supervise teams of coding agents from planning to merge. Any harness (Claude code, codex, +25 more). Desktop, web, mobile, and cloud agents.
Manage durable recurring session automations through the daemon API.
Inspect and control the current AO session's target-isolated browser. The desktop app must be…
Create and inspect reusable Cues for a local AO project. Both orchestrators and workers can…
Run local AO health checks. Use this to diagnose setup problems or verify the environment is…
Import reads the legacy Agent Orchestrator flat-file store (`~/.agent-orchestrator`)…
Manage orchestrator sessions.