DOCUMENTATION / Agents

Integrations

Agents' own hooks and plugins: exact session resume, and exact state where the hooks see everything.

Two kinds

Kind	Agents	What it adds
session	Claude Code, Codex, Copilot CLI, Cursor Agent, Devin CLI, Droid, Qoder CLI, Qwen Code, Grok CLI, Antigravity CLI, Hermes Agent	The agent reports its session id, so a restart resumes that exact conversation. State stays on screen detection — these agents' hooks miss some transitions (interrupts, permission answers).
state + session	Kimi Code, MastraCode, OpenCode, Kilo Code, Pi, OMP	The hooks or plugin see every transition, so while they report they decide the pane's state. A dialog visibly waiting on you still wins.

Install

modisa integration status          # installed, update available, available, not found
modisa integration install all     # everything recommended for the agents on this machine
modisa integration install codex   # or one
modisa integration uninstall codex # takes out only modisa's entries

Or Ctrl+B s → integrations. Each one goes into the agent's own config, in its own format, next to your settings; an agent's config directory has to exist (run it once). Installs happen where the server runs, which is where the agents are.

Report from your own tools

modisa report --source my-tool --agent my-agent --state working
modisa report --source my-tool --state blocked --seq 42   # stale seqs are ignored
modisa report --source my-tool --session-id abc123        # resume this session after a restart
modisa report --source my-tool --release                  # hand the pane back to screen detection

Run it inside a pane (it reads MODISA_PANE_ID) or name the pane first. Reports without --source don't change state.