AO Session Actions
Stops, resumes, merges, reviews, and schedules actions on Agent Orchestrator sessions.
Install
npx skills add OrchestratorInc/agent-orchestrator --skill ao-actions -g -a claude-code -y- Repository
- OrchestratorInc/agent-orchestrator14k
- Category
- DevOps
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Lightabout 994 tokens
- Runs scripts
- No, instructions only
What it does
Direct actions on one AO session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's browser, send a session's files, keep a host awake, and recurring AO automations. Use for "stop <session>", "merge <PR>", "review <session>'s PR", "show me what <session> built", "keep the Mac awake tonight", "every night, ...".
Follow the ao-rules skill. Find the session first (ao-rules "AO hosts": <host>/<session id>). Run each action on the owner host from its via computer. "Yes" means the user's yes for that exact action in this chat.
| Ask | Do | Yes needed | Hosts |
|---|---|---|---|
| Stop what it's doing now | aoapi POST "sessions/<id>/conversation/interrupt" | No | All |
| End the session | aoapi POST "sessions/<id>/kill" '{}' | Yes | All |
| Resume an exited agent | aoapi POST "sessions/<id>/resume-agent" '{}' | No | All |
| Restore an ended session | aoapi POST "sessions/<id>/restore" '{}' (an ended orchestrator can't come back while its project has another live one) | Yes | All |
| Merge a PR | see "Merge" | Yes, per PR | All |
| Start AO's reviewer on a session's PR | ao review trigger <id> | Yes | Local |
| Screenshot a session's browser | see "Screenshot" | No | Local |
| A session's files | see "Files" | No | Local |
| Keep the host awake | see "Keep awake" | Yes | Local |
| Recurring agent work | see "Automations" | Yes | Local |
| Start one worker directly | aoapi POST sessions '<json>' with projectId, displayName, prompt | Yes | All |
For an action marked Local on a remote host, ask that host's orchestrator to do it (ao-orchestrator).
Start a worker directly only when the project has no orchestrator and the user doesn't want one (ao-rules "orchestrator first").
