Supported Agents

Agent	Live status	Session resume	Fork to new pane	Hook (precise events)
Claude Code	✓	✓	✓	✓
GitHub Copilot CLI	✓	✓	no	✓
Codex	✓	✓	✓	✓
opencode	✓	✓	no	✓
Kimi Code CLI	✓	✓	no	✓
Grok Build	✓	✓	✓	✓
Pi	✓	✓	✓	no
Cursor	✓	resume command	no	no
Gemini	✓	no	no	no
Aider	✓	no	no	no
Amp	✓	no	no	no
Droid	✓	no	no	no
Qwen	✓	no	no	no
Kiro	✓	no	no	no

• Live status (blocked/working/done/idle) needs no setup. artuditu identifies the agent from the processes running in the pane, then reads the pane’s screen to tell what state it is in.
• Session resume discovers the agent’s latest session from its own on-disk store, keyed by the pane’s folder, and runs the agent’s resume command on restore.
• Fork to New Pane branches the running session into a new pane beside it, preserving the original’s full context under a new session id while the original keeps running. It needs an agent with a native fork command, so today that is Claude (claude --resume <id> --fork-session), Grok (grok --resume <id> --fork-session), Codex (codex fork <id>), and Pi (pi --fork <id>). Right-click the pane and choose Fork to New Pane, or press Ctrl+Space f. The action only appears for agents that can fork.
• Hook, via artu integration install <agent>, makes the agent report its exact session id and lifecycle events. Removal is surgical: artu integration uninstall <agent> touches only artuditu’s own entry. Kimi keeps its hooks in ~/.kimi-code/config.toml, the same file as your API keys, so artuditu edits it in place and leaves your keys, comments, and own hooks untouched. Grok Build reads hooks from ~/.grok/hooks/*.json, so artuditu just adds its own artuditu.json there and never touches your ~/.grok/config.toml.

Missing your agent? You can add it yourself without waiting for a release: drop an [identity] block in ~/.artuditu/manifests/<agent>.toml and artuditu will recognize it, as described in Custom detection rules. If you would like it built in, open an issue or a PR.

Agent Skill availability

Agent detection is built into Artuditu and does not require an Agent Skill. The optional bundled skill teaches a coding agent how to control Artuditu itself. Print the release-matched instructions for one conversation with artu skill show, or install them persistently with artu skill enable.

artu skill enable always writes the bundled SKILL.md index and references to the shared ~/.agents/skills/artuditu/ destination. It also installs additional native adapters when their hosts are detected.

The shared ~/.agents/skills/artuditu/ destination is understood by Codex, GitHub Copilot CLI, Gemini CLI, Pi, Cursor, Amp, Droid, and fx. Artuditu uses dedicated native destinations for Claude Code, OpenCode, Kimi Code CLI, Grok Build, Qwen Code, and Kiro. Aider does not expose a native Agent Skills installation directory, so use artu skill show when an Aider conversation needs the instructions.

artu skill status reports the bundled release separately from its managed filesystem installations. Codex marketplace plugins are managed by Codex and are not visible to this command.