Working with agents
The five adapters
How Sirio launches Claude Code, Codex, OpenCode, Pi and Oh-My-Pi, and what it writes for each.
Each supported CLI has an adapter that knows how to launch it, how to resume a session, and whether it can report its own state through hooks.
| Agent | Native hooks | How Sirio learns its state |
|---|---|---|
| Claude Code | Yes | Lifecycle hooks call sirioctl notify |
| Codex | Yes | Launched with a -c notify=[…] override that calls sirioctl notify |
| Oh-My-Pi | Yes | A worktree-local hook file, generated on launch |
| OpenCode | No | Terminal title and foreground process |
| Pi | No | Terminal title (π - <cwd>) |
What gets written where
An adapter’s prepare step writes inside the worktree: a .claude/settings.local.json, a hook file or a command-line override. Your user-global configuration stays untouched. Removing the worktree removes everything Sirio added.
ACP chat
Agents that speak the Agent Client Protocol can also run in a chat tab instead of a terminal. The Settings → Agents page lists what is installed, what the registry offers, and updates them in place.