Browse documentation

Agent compatibility

Which agents AutoDevOps records, and how.

One matrix, read from the same roster the homepage uses. A row says what the CLI writes for that harness, which capture path carries its sessions, and what proof backs the claim. Nothing here is a storage adapter: agents emit, AutoDevOps ingests.

Supported today

3 harnesses with a shipped hook pack or connector

Capture model

Signed events at hook time, from a CLI stream, or from a trace file

Proof ceiling

Fixture-backed; live customer walkthroughs pending

Compatibility matrix

Identifier is the value the CLI accepts, or the trace format id when the harness is recognised from a file. Lifecycle hooks and MCP registration name the files verifier install writes at project scope. Enforced PreToolUse is a customer-cloud CLI capability; the public npm CLI installs telemetry only.

AgentIdentifierCapture pathLifecycle hooksMCP registrationEnforced PreToolUseEvidence
Claude CodeSupported today`claude-code`Hook pack · Lite hook connector · MCP emission tools`.claude/settings.json``.mcp.json`Customer-cloud CLIHook payload and hook pack tests plus a normalized compatibility fixture; live customer walkthrough pending.
CodexSupported today`codex`Hook pack · MCP emission tools`.codex/hooks.json``.codex/config.toml`Customer-cloud CLIHook pack tests; no normalized compatibility fixture yet; live customer walkthrough pending.
CursorSupported today`cursor`Hook pack · CLI stream · MCP emission tools`.cursor/hooks.json``.cursor/mcp.json`Customer-cloud CLIHook pack tests and a Cursor Agent stream-json fixture; live customer walkthrough pending. IDE chat history and edit-stream capture remain roadmap.
PiTrace import`session_trace.pi.v1 … v3`Session trace file———Spec-bound parser with conformance fixtures for pi session format v1–v3; customer-cloud CLI only; live walkthrough pending.
OpenCodeVia SDK—SDK connector———No AutoDevOps pack, parser, or fixture. OpenCode loads plugins from `.opencode/plugins/` (project) and `~/.config/opencode/plugins/`; its session store is not in vendor docs.
Antigravity / Gemini CLIVia SDK—SDK connector———No AutoDevOps pack, parser, or fixture. Two products: Antigravity reads workspace hooks from `.agents/hooks.json` (PreToolUse, PostToolUse); Gemini CLI reads hooks from `.gemini/settings.json` with BeforeTool-style events.
Factory AI DroidVia SDK—SDK connector———No AutoDevOps pack, parser, or fixture. Droid reads hooks from `.factory/hooks.json` (project) or `~/.factory/hooks.json` with a settings.json fallback, passes hooks a `transcript_path` to the session JSONL, and loads skills from `.factory/skills/`.
Copilot CLIRoadmap`copilot`None shipped———The installer adds skills only and claims no hook or MCP support. Copilot CLI itself reads hooks from `.github/hooks/*.json`, so the gap is on the AutoDevOps side. A static normalized fixture exercises the event contract and the compatibility manifest records an explicit no-live-claim.

What each status requires

“Supported today” requires a shipped hook pack or connector plus a normalized agent_activity.v1 fixture or test in this repository. “Trace import” requires a spec-bound parser for the harness’s own session file. “Via SDK” rows carry no artifact here at all: they are in the matrix because the public site names them, and their evidence column says so. “Roadmap” means named, not implemented. Every other harness sits in the second table on this page. No row claims a live customer-cloud walkthrough; those receipts are still pending for every harness.

Capture paths

The matrix's capture column points at one of these. Distribution says which build carries the command, so the public npm package is never credited with a customer-cloud command.

PathCommandDistributionWhat it records
Hook packverifier hook pack install --provider claude-code,cursor,codexPublic npm CLI in telemetry mode; the customer-cloud CLI adds --mode enforce.Signed lifecycle records mapped by event: SessionStart to session.started, UserPromptSubmit to prompt.submitted, PreToolUse to tool.started, PostToolUse to tool.completed or tool.failed, Stop to turn.finished or turn.failed, SessionEnd to session.finished; only unrecognized hook events fall back to hook.completed / hook.failed. Enforced PreToolUse adds hook.blocked decisions and portal approval requests.
Lite hook connectorverifier hook claude-code <event>Customer-cloud CLI.Session, tool, and prompt activity from Claude Code hook JSON on stdin. Fails open when portal variables are absent so the developer is never blocked by telemetry.
CLI streamcursor-agent --print --output-format stream-json … | verifier connector cursor ingest --input -Public npm CLI.Session, prompt, tool, and result events with bounded summaries and SHA-256 hashes. Raw prompts and tool output are never emitted.
Session trace fileverifier connector session-trace ingest --input <session.jsonl>Customer-cloud CLI.STS-Format (session_trace.sts.v1) and pi session format v1–v3 files, with the format detected from the file header. Prompt text, assistant text, and tool results never leave the file: they become lengths and SHA-256 digests. Retained metadata: working directory and repository, model and provider, usage and cost, tool and file names, bounded command previews, and session names. Captured sessions export back to STS with autodevops-session-trace convert.
MCP emission toolsverifier install # registers the AutoDevOps MCP server for the harnessRegistered by the public installer for Claude Code, Cursor, and Codex; the @autodevops/verifier-mcp package is pending public publication.Signed session and tool events emitted by the agent through MCP tools, plus autodevops_attach_intent and autodevops_emit_intent_note for Intent Fidelity.
SDK connectorcreateAgentActivityConnector({ source: { kind: "custom_connector", … } })JS/TS helper in @autodevops/verifier-portal-client; focused Python, Go, and Kotlin builders with signed ingest and fail-closed approval polling.Whatever lifecycle, tool, model, and approval events the harness can see, with redaction, idempotency, and provenance applied before posting.

Why the matrix has no storage-format column

Some tracing tools read each agent’s native session store (JSONL files, SQLite databases) after the fact. AutoDevOps does not. Hook packs and connectors emit signed events while the session runs, the Cursor path reads the CLI’s own output stream, and the session-trace path reads a file you hand to the CLI. Pi is the one native-format exception: its session-trace parser reads Pi’s own session JSONL, but only the file you pass in, never by scanning the store. The signed raw event is stored unchanged in your cloud. The table of other harnesses below does record where each vendor says sessions live, because that decides whether a trace-file path is even possible.

Install for a supported harness

Preview first. The plan lists every file the installer would touch; nothing is written until you confirm.

bash
verifier harness plan --harness claude-code cursor codex   # preview, no writes
verifier install --harness claude-code cursor codex        # skills + hooks + MCP registration
verifier harness doctor                                    # verify the install receipt
  • Skills are copied to .agents/skills for every harness; Claude Code gets relative links under .claude/skills.
  • Hook files are merged into existing JSON. The installer stops before any write when a selected file contains invalid JSON.
  • Claude Code user-scope MCP registration needs the native claude mcp add --scope user command; the installer only writes project-scope .mcp.json.
  • Copilot receives skills only. The installer prints a warning instead of claiming hook or MCP support.

Import a session trace

Pi writes its session JSONL in a format the session-trace connector validates against a published spec. Any harness that can write STS-Format gets the same path.

bash
# customer-cloud CLI
# pi writes ~/.pi/agent/sessions/<cwd-derived folder>/<timestamp>_<session-id>.jsonl
verifier connector session-trace ingest --input ~/.pi/agent/sessions/--home-alice-app--/<timestamp>_<session-id>.jsonl --dry-run
verifier connector session-trace ingest --input trace.sts.jsonl
  • Format is detected from the first line: a numeric version means pi session format, a harness string means STS-Format.
  • Prompt text, assistant text, and tool results never leave the file; they become lengths and SHA-256 digests. Working directory, repository, model and provider, usage and cost, tool and file names, bounded command previews, and session names are retained as metadata.
  • Pi compactions, branches, and model changes surface as session.compacted, session.branched, and session.model_changed so context loss is visible in the ledger.
  • The format spec is normative and carries a closed issue-code registry; a mapping change that breaks agent_activity.v1 conformance is a spec violation, not a tolerated drift.

Harnesses not in the matrix

Coding agents buyers ask about that have no pack, parser, or fixture in the AutoDevOps repository and are not named on the public site. Every cell comes from the vendor's own documentation; where the vendor documents nothing, the cell says so rather than repeating a third-party write-up. A harness earns a Supported today or Trace import row only when the repository carries code for it.

HarnessUpstream hooks or pluginsSession store (vendor docs)AutoDevOps path today
AmpExperimental plugin API in .amp/plugins/ (project) or ~/.config/amp/plugins/ with amp.on(...) event handlers; loads only with PLUGINS=all and only in the binary-installed CLI.Not in vendor docs.SDK connector called from a plugin event handler, or the MCP tools.
ClineExecutable scripts in .clinerules/hooks/ that read JSON on stdin; events include TaskStart and PreToolUse, which can cancel the call. macOS and Linux only.One folder per task under the editor global storage directory with api_conversation_history.json and ui_messages.json.A hook script can call verifier hook lifecycle cline <event>; the stdin shape differs from Claude Code and Cursor, so the event mapping is unproven.
Windsurf.devin/hooks.json at the workspace root, with .windsurf/hooks.json as the legacy location; JSON on stdin; the pre hooks (pre_user_prompt, pre_read_code, pre_write_code, pre_run_command, pre_mcp_tool_use) block with exit code 2.post_cascade_response_with_transcript writes ~/.windsurf/transcripts/<trajectory_id>.jsonl, capped at 100 files.A hook command can call the lifecycle emitter; the transcript JSONL would need its own parser.
Kimi Code[[hooks]] tables in ~/.kimi-code/config.toml with event, command, optional matcher and timeout; PreToolUse is documented.~/.kimi-code/sessions/<workDirKey>/<sessionId>/ with state.json and agents/*/wire.jsonl.A hook command can call the lifecycle emitter; wire.jsonl would need its own parser.
Oh My PiPi-style TypeScript extensions under ~/.omp/agent/extensions.~/.omp/agent/sessions/<encoded-cwd>/<timestamp>_<sessionId>.jsonl, version 3, but each file opens with a fixed 256-byte title slot and the header carries fields Pi does not.Not readable by the Pi parser as is: the session-trace spec requires the session header on line one. Needs a fixture and a parser change.
Hermes AgentPython plugins in ~/.hermes/plugins/ registering pre_llm_call, post_llm_call, on_session_start, and on_session_end.SQLite at ~/.hermes/state.db holding full message history.Python SDK helper called from a plugin hook.
OpenClawGateway hooks for lifecycle events plus plugin hooks such as before_tool_call, after_tool_call, before_agent_start, and agent_end.SQLite at ~/.openclaw/agents/<agentId>/agent/openclaw-agent.sqlite; JSONL transcripts are legacy inputs and archives.SDK connector from a plugin hook.
Grok BuildJSON files in ~/.grok/hooks/*.json (personal) and <project>/.grok/hooks/*.json; project hooks run only after /hooks-trust or --trust; PreToolUse is the one blocking event and reads event JSON on stdin.grok sessions lists, searches, and deletes; grok export writes Markdown; the on-disk format is not in the vendor docs reached.A hook command can call the lifecycle emitter; the stdin shape is unproven, so no fixture yet.
fxNo hook system documented; skills and MCP servers are.~/.fx/sessions/<session-id>/ with session.json, background/, subagent/, and logs/.The MCP tools, or the SDK connector.
DeepSeek HarnessNo hook system; everything is a Cordis plugin, including the session log and the agent loop.An append-only session event log plugin; the file format is not documented.SDK connector from a plugin.
  • Prime Agent and the OpenCode2 beta are not listed: no vendor documentation of a hook or session surface was found.
  • Harnesses that write STS-Format or Pi-format session files import through the session-trace connector without new code. Oh My Pi does not qualify: its files diverge from Pi version 3.
  • Harnesses with shell-command hooks can call verifier hook lifecycle <provider> <event>. The command accepts any provider name, but the hook pack compiler writes configuration only for Claude Code, Cursor, and Codex, and no fixture proves the stdin mapping for another harness.
  • Harnesses that load MCP servers can emit signed events through the AutoDevOps MCP tools once the server is registered in their MCP configuration.
  • Plugin-only harnesses use the SDK connector contract from inside a plugin; Python, Go, and Kotlin helpers exist beside the JS/TS one.

Contribute a row

A new row needs three things: a normalized agent_activity.v1 fixture in packages/verifier/test/fixtures/connector-compatibility/, a manifest entry that states what the fixture proves and what it does not, and a roster entry in app/lib/agent-harnesses.ts. The roster test fails the build if a row names a hook file the CLI does not write.