Native agent clients
Devctl supports 25 optional native CLI adapters alongside Claude and Codex. Each adapter implements launch and resume, with typed interfaces for installation, account configuration, health and capabilities. All optional adapters are marked partial: the checks below cover source, fixtures and commands that run without credentials. Antigravity 1.4.0 also completed Google sign-in and opened its authenticated interactive console in a managed Linux container. Authenticated native restore and end-to-end task/event delivery remain unverified. These checks made no paid generation requests.
Capability and verification matrix
implemented-tested means the existing integration has passing regression coverage. implemented-unverified means an implementation has no execution evidence. partial means useful implemented capabilities coexist with explicit gaps. unsupported means the action is refused; CLI availability alone does not imply integration coverage. Most external adapters have unavailable usage/billing/subscription accounting; Antigravity separately exposes verified native shared-group quotas. Native event coverage below means implemented sanitizer/installer fixtures, not authenticated delivery verification.
| Client | Status | Executable | Installation | Exact native resume | Identity / lifecycle | Executable proof on 2026-10-12 |
|---|---|---|---|---|---|---|
| Claude Code | implemented-tested (retained) |
claude |
Existing managed native installer | Existing UUID resume | Existing hooks, native children and official usage | Existing regression suite; not reauthenticated here |
| Codex | implemented-tested (retained) |
codex |
Existing managed native installer | Existing UUID resume | Existing native observation/hooks and official usage | Existing regression suite; not reauthenticated here |
| OpenCode | partial |
opencode |
npm | opencode --session ID |
ID + selected events | Executed 1.19.0 |
| Gemini CLI | partial |
gemini |
npm | gemini --resume ID |
ID + selected events | Executed 0.63.0 |
| GitHub Copilot CLI | partial |
copilot |
npm | copilot --resume ID |
ID + selected events | Executed 1.0.95 |
| Cursor Agent | partial |
cursor-agent |
binary | cursor-agent --resume ID |
ID + selected events | Source + fixtures; executable unverified |
| Qwen Code | partial |
qwen |
npm | qwen --resume ID |
ID + selected events | Executed 0.25.1 |
| Kimi Code | partial |
kimi |
npm | kimi --session ID |
ID + selected events | Executed 2.1.1 |
| Kilo Code | partial |
kilo |
npm | kilo --session ID |
ID + selected events | Executed 7.8.8 |
| Pi | partial |
pi |
npm | pi --session ID |
ID + selected events | Executed 1.1.0 |
| OMP | partial |
omp |
binary | omp --resume ID |
ID + selected events | Source + fixtures; executable unverified |
| Mastra Code | partial |
mastracode |
npm | mastracode --thread ID |
ID + selected events | Help executed; package 0.46.0 |
| Factory Droid | partial |
droid |
binary | droid --resume ID |
ID only | Source + fixtures; executable unverified |
| Devin CLI | partial |
devin |
binary | devin --resume ID |
ID only | Source + fixtures; executable unverified |
| Qoder CLI | partial |
qoder |
binary | qoder --resume ID |
ID only | Source + fixtures; executable unverified |
| Hermes Agent | partial |
hermes |
binary | hermes --resume ID |
Manual exact ID | Source + fixtures; executable unverified |
| Letta Code | partial |
letta |
npm | letta --conversation ID |
Manual exact ID | Executed 0.34.11 |
| Grok CLI | partial |
grok |
binary | grok --resume ID |
ID only | Source + fixtures; executable unverified |
| Antigravity CLI | partial |
agy |
managed binary | agy --conversation ID |
ID + working/idle/error + current model | Linux arm64 1.4.0 install/version/help, live managed Google sign-in and authenticated console + fixtures |
| Amp | partial |
amp |
binary | amp threads continue ID |
Manual exact ID | Source + fixtures; executable unverified |
| Kiro CLI | partial |
kiro-cli |
binary | kiro-cli chat --resume-id ID |
Manual exact ID | Source + fixtures; executable unverified |
| Cline | partial |
cline |
npm | cline --tui --id ID |
Manual exact ID | Executed 3.0.70 |
| Maki | partial |
maki |
binary | maki --resume ID |
Manual exact ID | Source + fixtures; executable unverified |
| Command Code | partial |
command-code |
npm | command-code --session ID |
ID + selected events | Executed 1.79.2 |
| Crush | partial |
crush |
npm | crush --session ID |
Manual exact ID | Executed 0.98.1 |
| Muse Code | partial |
muse |
binary | muse resume ID |
Manual exact ID | Source + fixtures; executable unverified |
| Prime Agent | partial |
prime-agent |
binary | prime-agent --resume ID |
Manual exact ID | Source + fixtures; executable unverified |
Executable probe evidence records the actual binary/package versions, help flags and unexecuted checks. Twelve clients passed real native --version and --help. Mastra Code help ran, but its --version falls into headless mode and fails without a prompt in a non-TTY; the adapter uses installed package metadata instead. Twelve clients were not installed in the isolated verification prefix. Authenticated task execution and native resume remain unverified across the optional clients; Antigravity sign-in and its authenticated console have been observed. The original probes ran on macOS arm64; Antigravity additionally passed an isolated Linux arm64 container install/version/help check. Other platforms and authenticated task execution remain unverified.
Architecture and packages
The existing Provider/session/runtime abstraction now accepts a bounded safe provider identifier. Installed registry entries authorize launch; an unknown or removed ID cannot construct a new process. The shipped ID list is metadata, not a schema allowlist. Adding an independent future agent-cli package does not require editing contracts, switches, TUI or web code. The existing optional provider-package loader discovers @devctl/provider-agent-* modules from the runtime/controller optional dependencies. DEVCTL_AGENT_PROVIDER_PACKAGES selects operator-trusted packages; empty disables the family. Builtin Claude/Codex behavior stays in its existing implementation.
The shared @devctl/agent-cli-kit validates versioned descriptors, creates argv, checks versions and produces optional hook/plugin assets. Runtime, contracts, controller and UI consumers are TypeScript; package modules use the existing workspace ESM package convention and complete .d.mts declarations. Profiles describe compatible native protocols independently of provider IDs. A package can provide standalone reporter/plugin/installer assets for another protocol; a custom installer must export installAgentIntegration, removeAgentIntegration and agentIntegrationHealth, accept the same owned-account payload, and return bounded health metadata. Packages execute trusted operator code; browser/Project input cannot select arbitrary modules or executables.
All agents run in existing devctl-managed Project containers and their existing account UID, PTY and tmux pane. No new per-container daemon or host-global agent install is introduced. Reattaching an existing pane remains possible when its optional package is removed; starting a new process requires that package. Removing a package preserves accounts, live panes and history. Provider package installation describes control-plane linking/restarts without restarting Projects.
Explicit setup and network grants
The shared TUI/web provider picker uses the registry, and Accounts exposes native executable/version/integration health and supported actions. Clients normally require explicit installation. Antigravity opts into verified immutable native installation and managed hooks on a new launch; its native console performs the user’s official login. Authentication state is unknown until upstream proves it; unrelated credentials are never copied into another provider. No generic API token is treated as a subscription.
devctl agent clients lists the catalog. Use devctl account client ACCOUNT WORKSPACE health, install-cli, install-integration or remove-integration for explicit actions. The install-cli action supports declared npm clients and Antigravity’s SHA512-verified binary release manifests using immutable managed installation/cache; other binary/manual/uv installers remain explicit official container setup. Optional clients are version-probed only during an explicit health/install action or a new launch; inventory does not scan all registered CLIs across all containers. A newer adapter package does not automatically replace a running native CLI. Unknown/unparseable versions report unknown health and prevent a new launch; they do not substitute a shell. Some installers require Node >=22.19 or Bun and native libc dependencies.
Existing Project Internet restrictions remain in force. Required Claude/Codex and verified Antigravity Google sign-in/model hosts are included separately from editable infrastructure (see Internet access). Other clients and optional endpoints need explicit Project grants for their real model, OAuth/login, update and package destinations. CLI installation does not grant unrestricted runtime egress. Account-specific native endpoints/configuration remain in that account's persisted provider home.
Integration installation/removal is account-owned, idempotent and serialized across concurrent sessions; Antigravity installs its supported hooks during new launch, and Accounts also exposes explicit install/remove actions. Config writes are atomic, preserve unrelated hooks/plugins/preferences and file modes, refuse symlink or foreign-owned paths, and use hashed ownership markers. Modified managed assets or incompatible JSON/TOML/named-hook blocks report conflicts. Package updates remove previous owned event/profile entries; relocating an integration requires an explicit remove before installing its new location. Hook-disable settings report unhealthy configuration. Native event payload prompts, tool arguments, paths and credential/error bodies are discarded before writing private bounded state. Host readers whitelist metadata and fence native IDs by provider, account UID, session and process generation; controller updates also require the exact live process and monotonic observation time.
Reattach, native resume, restart and observation
Reattach connects to the existing PTY/tmux process. Native resume creates a new official CLI process using the exact persisted conversation/thread/session ID, account and cwd. An explicit process restart first stops the selected process and uses native resume; without a known native identity it is unavailable. A devctl session ID is never passed as a new client's native ID. devctl session new --resume ID can supply an exact externally known ID. Native history changes are persisted with account and observation time, bounded to 64 previous identities. Arbitrary transcript scans and unimplemented list-output parsers are not called native discovery.
Sixteen adapters install supported native identity/event hooks or plugins. Factory Droid, Devin, Qoder and Grok only observe a session identity; they do not claim working/idle/permission coverage. The other nine currently need an explicitly supplied native identity. OpenCode/Kilo only associate the selected local root session with the pane; shared remote servers and OpenCode V2 require another integration. Pi/OMP events observe turns and session changes but do not certify approval/cancellation states. Reliable events retain native provenance; process inventory independently proves running/exited. Missing, stale or unrecognized semantic evidence becomes unknown, never a guessed idle/error from terminal text. Existing notification preferences, transition deduplication and process accounting are retained.
External native tool permission decisions remain in the client terminal. Antigravity explicitly opts into the existing managed instructions/Skills/docs/MCP snapshot path through a session-local native configuration overlay; approved MCP requests still use the existing session authorization and approvals. Its bounded structured context handoff uses official --prompt-interactive, and native hooks can observe current model. Other clients retain their declared capabilities. Claude/Codex-specific subagent routing, model-capacity retries, native transcript migration, cross-account continuation, composer/slash-command injection and autonomous run behavior remain guarded unless separately supported. Actual measured CPU/RAM/process inventory remains available; external per-session token counts and billing costs remain unavailable rather than estimated. Antigravity separately supports verified read-only account quota groups, described below.
Claude goal observation follows the exact live native branch, including goals installed before the current process started. Large debug records no longer limit discovery to an 8 MiB tail: the reader scans under a fixed time/byte bound and keeps at most 64 small, account/generation-specific branch checkpoints. Unchanged files refresh the observation without rereading history; appended records must link to the verified checkpoint. Truncation, replacement, edits, missing parents and compaction boundaries invalidate unsupported evidence. Prompt text, unrelated branches and model explanations never become goals.
Validation and repeatable upstream checks
The kit and upstream fixtures check all 25 interactive/headless/resume argument forms, exact opaque IDs, unknown capabilities, shell quoting, compatible future package IDs, native event redaction, malformed payloads, version formats, concurrent installation, ownership/symlinks, atomic configuration preservation, health and reversible uninstall. Runtime tests execute the actual standalone installer against an isolated account through the Docker transport fixture and check generation/UID identity fences. Controller/TUI/CLI regression tests cover generic registry selection, authorization, native identity switches, lifecycle replay and capability-aware restart. Existing Claude/Codex regressions run alongside them. Verification completed with workspace build/typecheck and lint, 67 kit/adapter fixtures, 43 focused runtime/contracts/host checks, controller regression coverage (131 plus 10 native API fixtures), 40 TUI tests and 84 CLI tests. The earlier complete runtime suite passed 405 tests with four opt-in Docker cases skipped. Test groups overlap and are not a single combined total. Three pre-existing subprocess fixtures exceeded deadlines during concurrent builds and passed unchanged when rerun serially.
Credential-free upstream checks are opt-in: node packages/agent-cli-kit/verify-upstream.mjs --clients=gemini,pi --install-npm. The harness uses an isolated prefix/HOME/environment, public package installation and version/help only. Binary/manual clients can use --existing=/path/to/isolated/prefix; they are never installed through a guessed universal installer. Authenticated session/resume/events need a separately provisioned disposable Project/account and are excluded from standard CI and this verification. Upstream research (source access required) distinguishes observed published metadata from executed versions.
Per-client commands and limitations
OpenCode (`opencode`)
Install in the Project container: npm install -g opencode-ai. Upstream platforms: linux, darwin, win32.
New interactive argv: opencode. One-shot argv: opencode run PROMPT --format json. Exact resume argv: opencode --session ID. Version check: opencode --version.
Account paths: ~/.config/opencode, ~/.local/share/opencode, ~/.local/state/opencode, ~/.cache/opencode. Managed native integration: .config/opencode/plugins/devctl-agent.js (opencode-plugin, profile opencode). Events: local root session/status/permission/question events.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 1.19.0. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used. OpenCode V1 server plugin events are scoped to a locally launched CLI server. Shared remote server and OpenCode V2 pane selection require a different TUI plugin and remain unsupported.
Gemini CLI (`gemini`)
Install in the Project container: npm install -g @google/gemini-cli. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=20.
New interactive argv: gemini. One-shot argv: gemini --prompt PROMPT --output-format stream-json. Exact resume argv: gemini --resume ID. Version check: gemini --version.
Account paths: ~/.gemini. Managed native integration: .gemini/settings.json (gemini-json, profile gemini). Events: SessionStart, BeforeAgent, AfterAgent, BeforeTool, AfterTool, SessionEnd.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 0.63.0. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used.
GitHub Copilot CLI (`copilot`)
Install in the Project container: npm install -g @github/copilot. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.
New interactive argv: copilot. One-shot argv: copilot --prompt PROMPT. Exact resume argv: copilot --resume ID. Version check: copilot --version.
Account paths: ~/.copilot. Managed native integration: .copilot/settings.json (copilot-json, profile copilot). Events: SessionStart, UserPromptSubmit, PreToolUse, PermissionRequest, Stop, ErrorOccurred, SessionEnd.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 1.0.95. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used.
Cursor Agent (`cursor`)
Install in the Project container: curl https://cursor.com/install -fsS | bash. Upstream platforms: linux, darwin.
New interactive argv: cursor-agent. One-shot argv: cursor-agent --print PROMPT --output-format stream-json. Exact resume argv: cursor-agent --resume ID. Version check: cursor-agent --version.
Account paths: ~/.cursor. Managed native integration: .cursor/hooks.json (cursor-json, profile cursor). Events: sessionStart, beforeSubmitPrompt, stop, sessionEnd.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used. The ambiguous generic executable agent is not auto-detected as Cursor; install the cursor-agent alias.
Qwen Code (`qwen`)
Install in the Project container: npm install -g @qwen-code/qwen-code. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=20.
New interactive argv: qwen. One-shot argv: qwen --prompt PROMPT --output-format stream-json. Exact resume argv: qwen --resume ID. Version check: qwen --version.
Account paths: ~/.qwen. Managed native integration: .qwen/settings.json (claude-json, profile claude-compatible). Events: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PermissionRequest, Stop, SessionEnd.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 0.25.1. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used.
Kimi Code (`kimi`)
Install in the Project container: npm install -g @moonshot-ai/kimi-code. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.19.
New interactive argv: kimi. One-shot argv: kimi -p PROMPT. Exact resume argv: kimi --session ID. Version check: kimi --version.
Account paths: ~/.kimi-code. Managed native integration: .kimi-code/config.toml (toml-hooks, profile kimi). Events: SessionStart, TurnStarted, PreToolUse, PostToolUse, PermissionRequest, PermissionResult, Stop, StopFailure, Interrupt, SessionEnd.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 2.1.1. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used. This adapter targets the current Node.js kimi-code client and ~/.kimi-code; the legacy Python kimi-cli ~/.kimi configuration is not migrated by devctl.
Kilo Code (`kilo`)
Install in the Project container: npm install -g @kilocode/cli. Upstream platforms: linux, darwin, win32.
New interactive argv: kilo. One-shot argv: kilo run PROMPT --format json. Exact resume argv: kilo --session ID. Version check: kilo --version.
Account paths: ~/.config/kilo, ~/.local/share/kilo, ~/.local/state/kilo, ~/.cache/kilo. Managed native integration: .config/kilo/plugin/devctl-agent.js (opencode-plugin, profile kilo; minimum 7.0.0). Events: local root session/status/permission/question events.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 7.8.8. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Live authenticated execution is opt-in and has not been run in this checkout. Process inventory reports running/exited; without a supported native event the semantic state is unknown. Subscription balance and billing are unavailable; provider-native authentication and UI are used. Kilo >=7 uses a default module descriptor with a server factory, matching current upstream documentation. Plugin telemetry is scoped to a locally launched server; sharing a remote OpenCode-compatible server is unsupported.
Pi (`pi`)
Install in the Project container: npm install -g @earendil-works/pi-coding-agent. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.19.0.
New interactive argv: pi. One-shot argv: pi --print PROMPT --mode json. Exact resume argv: pi --session ID. Version check: pi --version.
Account paths: ~/.pi. Managed native integration: .pi/agent/extensions/devctl-agent.ts (pi-extension, profile pi). Events: session_start, agent_start, agent_end, session_shutdown.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 1.1.0. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Current package is @earendil-works/pi-coding-agent; old @mariozechner package examples may differ. --resume opens a picker; exact restore uses --session. Permission/cancellation lifecycle and JSONL usage parsing are unverified.
OMP (`omp`)
Install in the Project container: curl -fsSL https://omp.sh/install | sh. Upstream platforms: linux, darwin, win32.
New interactive argv: omp. One-shot argv: omp --print PROMPT --mode json. Exact resume argv: omp --resume ID. Version check: omp --version.
Account paths: ~/.omp. Managed native integration: .omp/agent/hooks/pre/devctl-agent.ts (pi-extension, profile omp). Events: session_start, session_switch, agent_start, agent_end, session_shutdown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Bun package installation requires Bun >=1.3.14; native binaries use the installer. Hook factories must be under hooks/pre or hooks/post, not directly under hooks. Alpine musl binaries require libstdc++ and libgcc.
Mastra Code (`mastracode`)
Install in the Project container: npm install -g mastracode. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.19.0.
New interactive argv: mastracode. One-shot argv: mastracode --prompt PROMPT --output jsonl. Exact resume argv: mastracode --thread ID. Version check: mastracode --version with declared npm-package metadata fallback for mastracode.
Account paths: ~/.mastracode. Managed native integration: .mastracode/hooks.json (mastra-json, profile mastracode). Events: SessionStart, AgentStart, AgentEnd, PermissionRequest, PermissionResult, Interrupt, SessionEnd.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed installed package version: 0.46.0; native --version failed non-TTY. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Hooks JSON uses top-level event arrays of type/command entries; it is not Claude settings JSON. Native thread listing and CLI config environment overrides were not verified. Version is read from the installed mastracode package metadata because this release has no working non-TTY --version mode.
Factory Droid (`droid`)
Install in the Project container: curl -fsSL https://app.factory.ai/cli | sh. Upstream platforms: linux, darwin, win32.
New interactive argv: droid. One-shot argv: droid exec PROMPT --output-format stream-json. Exact resume argv: droid --resume ID. Version check: droid --version.
Account paths: ~/.factory. Managed native integration: .factory/hooks.json (claude-json, profile claude-compatible). Events: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Notification, Stop, SessionEnd.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Current hooks.json is canonical; settings.json hook entries are fallback only when hooks.json is absent. Interactive -r means resume, but exec -r means reasoning effort; exec native resume is -s. Hooks do not establish reliable state after every canceled permission or interrupt.
Devin CLI (`devin`)
Install in the Project container: curl -fsSL https://cli.devin.ai/install.sh | bash. Upstream platforms: linux, darwin, win32.
New interactive argv: devin. One-shot argv: devin --print PROMPT. Exact resume argv: devin --resume ID. Version check: devin --version.
Account paths: ~/.config/devin. Managed native integration: .config/devin/config.json (claude-json, profile claude-compatible). Events: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PermissionRequest, Stop, SessionEnd.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Headless runs require an already trusted workspace or the documented explicit trust option. Unix account path is .config/devin; Windows uses Roaming AppData/devin. An official config-home environment override and exact latest binary version were not verified.
Qoder CLI (`qoder`)
Install in the Project container: curl -fsSL https://qoder.com/install | bash. Upstream platforms: linux, darwin, win32.
New interactive argv: qoder. One-shot argv: qoder --print PROMPT --output-format stream-json. Exact resume argv: qoder --resume ID. Version check: qoder --version.
Account paths: ~/.qoder. Managed native integration: .qoder/settings.json (claude-json, profile claude-compatible). Events: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, PermissionRequest, Stop, SessionEnd.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Windows ARM64 is explicitly unsupported by upstream. Both qoder and qodercli binaries exist in the legacy npm package; current docs use qoder. --no-session-persistence disables native restore; permission/cancel lifecycle remains unverified.
Hermes Agent (`hermes`)
Install in the Project container: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash. Upstream platforms: linux, darwin, win32.
New interactive argv: hermes. One-shot argv: hermes chat --oneshot --query PROMPT --format stream-json. Exact resume argv: hermes --resume ID. Version check: hermes --version.
Account paths: ~/.hermes. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Current --query seeds interactive chat on a TTY; --oneshot is required for consistent exit. Hermes-specific Python plugins and HOOK.yaml are not installed by the kit. Session-list text is exposed; structured session identity parsing is not implemented.
Letta Code (`letta`)
Install in the Project container: npm install -g @letta-ai/letta-code. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.19.0.
New interactive argv: letta. One-shot argv: letta -p PROMPT --output-format stream-json. Exact resume argv: letta --conversation ID. Version check: letta --version.
Account paths: ~/.letta. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 0.34.11. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Native restore requires a conversation ID; an agent ID alone is not a conversation. Default conversation restore can require --conversation default --agent ID; the single-ID adapter does not represent it. Agent/conversation state can live remotely; local config is not a complete session backup. Hooks docs currently redirect to deprecated reference; automatic hook installation is omitted.
Grok CLI (`grok`)
Install in the Project container: curl -fsSL https://x.ai/cli/install.sh | bash. Upstream platforms: linux, darwin, win32.
New interactive argv: grok. One-shot argv: grok --single PROMPT --output-format streaming-messages-json. Exact resume argv: grok --resume ID. Version check: grok --version.
Account paths: ~/.grok. Managed native integration: .grok/hooks/devctl.json (claude-json, profile claude-compatible). Events: SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Notification, Stop, SessionEnd.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Targets official xai-org/grok-build, not community grok-cli packages. --session-id creates a new session and does not resume an existing conversation. Grok output formats are streaming-json/streaming-messages-json, not stream-json. Permission/cancel reporting requires Grok-specific Notification/StopCancelled semantics not fully implemented here.
Antigravity CLI (`antigravity`)
Create an antigravity account, then choose Accounts → login, or run ./devctl account login ACCOUNT HOST. The existing login terminal launches official agy inside a running managed Project container. A new Antigravity process automatically installs the official native binary and managed hooks if needed; Client controls → Shift+I also installs it explicitly in the selected container. No host agent CLI is installed.
The official Unix installer resolves a platform manifest and SHA512-protected GCS archive. devctrl uses that same manifest, permits only its declared download prefix, verifies SHA512 before transfer and again in the container, then extracts and probes as an unprivileged installer. Versions live at /opt/devctl/agent-cli/antigravity/VERSION/bin/agy; selecting a new version retains older executable bytes for active sessions. Linux x64/arm64 glibc and musl are supported by upstream release manifests; only Linux arm64 1.4.0 was executed in this check.
The user signs in through the official Google browser URL and pastes the authorization code into the console. SSH_CONNECTION selects the official remote flow and BROWSER=false avoids a container-local browser. Native ~/.gemini/antigravity-cli authentication/history/settings are linked to the existing provider/account store (/run/devctl/accounts/antigravity/ACCOUNT/.gemini/antigravity-cli), independently of Gemini accounts, and survive later session homes and container replacement. Global config defaults are copied into each session’s local ~/.gemini/config overlay; concurrent sessions keep distinct MCP sockets and managed runtime rules. Existing canonical native files are retained when migrating an older whole-.gemini link. Native changes to the session overlay remain session-scoped. No authentication is fabricated from hook/settings files. There is no official auth-status CLI command. The optional adapter verifies its account-owned native OAuth token using Google's official read-only userinfo endpoint through the current network route; no second CLI, paid model request, token refresh or credential copying is involved. Accounts shows the verified Google identity independently of the Project. API-key mode and transport/scope failures remain unverified, and a refreshable expired token is never treated as a confirmed logout. /logout is the native sign-out action.
New interactive argv: agy. Explicit initial structured context: agy --prompt-interactive PROMPT. One-shot argv: agy --print PROMPT --output-format stream-json. Exact native resume: agy --conversation ID; devctrl never substitutes --continue, whose fallback can create a new conversation. Version check: agy --version.
Managed hooks are installed in account .gemini/config/hooks.json and copied into each session overlay as the devctl-agent-antigravity block, preserving unrelated hooks. Authorized managed MCP servers use the documented .gemini/config/mcp_config.json; an always_on rule in .gemini/config/rules/devctl-runtime.md directs the agent to the live runtime guide and session instructions. Native user rules/MCP entries are preserved, and conflicts in managed entries are reported before replacing user configuration. SessionStart observes the native conversationId; PreInvocation reports working; Stop uses fullyIdle and terminationReason to distinguish waiting, background work and failure. Current model is observed from the safe modelName field without inferring reasoning effort. Permission/cancellation transitions, detailed per-session token/context telemetry, subagent telemetry and billing remain unavailable. Accounts reads native shared model-group quota percentages and reset times through the separate read-only collector described below. Native updater mutation is disabled so devctrl controls immutable executable selection. Release tracking uses the adapter’s official native manifest and upstream Markdown changelog; updates remain opt-in through the existing toolchain workflow. Native /goal telemetry currently covers only Claude/Codex; Antigravity’s goal remains unknown rather than inferred from prompts or handoff summaries.
Approved devctrl permissions use the shared durable delivery queue and a package-owned Antigravity notification protocol. Rules are written in place before notification. Native working/compaction/question states and user drafts defer input until a verified idle composer; no Escape, cancellation or process restart is used. The sender pastes the exact notice, sends Enter separately, then requires a matching native USER_INPUT record in the same account/conversation after a saved transcript byte anchor. A successful paste alone never counts as delivery. Receipts bind the provider PID, process start, generation and notification digest; retries do not submit twice. This is notification of an operator grant, separate from observing Antigravity's own permission dialogs, which remains unavailable. Host-agent restart restores authorized MCP broker listeners for installed managed-configuration adapters, retaining their original opaque socket paths and frozen snapshots.
Verification on 2026-10-16: real official Linux arm64 1.4.0 native install, SHA512 verification, availability/version/help, and integration installation were checked without credentials in disposable containers. Unit tests cover account-store reuse/isolation, exact resume, interactive/headless argv, hook privacy/state handling, artifact rejection and old-version preservation. Google OAuth sign-in, authenticated console, full-tool-permission process flags and the read-only quota command were subsequently verified with 1.4.0. Notification fixtures use the observed 1.4.0 native transcript schema, including busy/compact/question deferral, Unicode prompt whitespace, drafts, separate Enter, historical/model-text rejection and crash/retry deduplication. Native conversation restore and complete end-to-end lifecycle delivery remain separately unverified.
Primary sources: installation/authentication, official installer, headless, resume/cache, hooks, release notes, rules, MCP.
Amp (`amp`)
Install in the Project container: curl -fsSL https://ampcode.com/install.sh | bash. Upstream platforms: linux, darwin, win32.
New interactive argv: amp. One-shot argv: amp --execute PROMPT --stream-json. Exact resume argv: amp threads continue ID. Version check: amp --version.
Account paths: ~/.config/amp. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Native thread IDs use T- prefixes; no standalone machine-readable history command was verified. No compatible native lifecycle installer is implemented. Native version strings may not match the shared semver parser. Only verified configuration paths are backed up; complete native thread storage paths were not established.
Primary sources: 1, 2, 3, 4, 5.
Kiro CLI (`kiro`)
Install in the Project container: curl -fsSL https://cli.kiro.dev/install | bash. Upstream platforms: linux, darwin, win32.
New interactive argv: kiro-cli chat. One-shot argv: kiro-cli chat --no-interactive PROMPT. Exact resume argv: kiro-cli chat --resume-id ID. Version check: kiro-cli --version.
Account paths: ~/.kiro. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Linux needs glibc >=2.34 or a musl build; native Windows requires Windows 11 PowerShell. --resume is latest; exact restore requires --resume-id. Interactive --sessions dashboard is not a verified JSON discovery command. Native agent/workspace hook formats are not installed; stream-json headless needs V2/V3.
Cline (`cline`)
Install in the Project container: npm install -g cline. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.
New interactive argv: cline --tui. One-shot argv: cline --json PROMPT. Exact resume argv: cline --tui --id ID. Version check: cline --version.
Account paths: ~/.cline. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 3.0.70. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Current -p means plan; --oneshot examples belong to older CLI interfaces. Native script hook format is not supported by an existing kit installer. Headless JSON event identity and usage parsers are not implemented.
Maki (`maki`)
Install in the Project container: curl -fsSL https://maki.sh/install.sh | sh. Upstream platforms: linux, darwin, win32.
New interactive argv: maki. One-shot argv: maki --print PROMPT --output-format stream-json. Exact resume argv: maki --resume ID. Version check: maki --version.
Account paths: ~/.config/maki, ~/.local/share/maki, ~/.local/state/maki, ~/.local/logs/maki, ~/.cache/maki, ~/.maki. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. A positional prompt still opens the TUI; --print must be explicit. Legacy .maki directory takes precedence until native migration. Native Lua autocmds/slots have no kit installer. --version probe and exact published binary version were not executed or independently verified.
Command Code (`command-code`)
Install in the Project container: npm install -g command-code. Upstream platforms: linux, darwin, win32. Runtime: Node.js >=22.
New interactive argv: command-code. One-shot argv: command-code --print PROMPT --output-format json. Exact resume argv: command-code --session ID. Version check: command-code --version.
Account paths: ~/.commandcode. Managed native integration: .commandcode/settings.json (claude-json, profile claude-compatible). Events: SessionStart, PreToolUse, PostToolUse, Stop.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 1.79.2. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Use command-code everywhere; cmd is the native Windows shell, so the Windows alias is cmdc. Shell hooks expose only SessionStart/PreToolUse/PostToolUse/Stop; wider lifecycle requires native mods. Print json output is newline-delimited AgentEvent frames plus final result, not one JSON object.
Primary sources: 1, 2, 3, 4, 5.
Crush (`crush`)
Install in the Project container: npm install -g @charmland/crush. Upstream platforms: linux, darwin, win32.
New interactive argv: crush. One-shot argv: crush run PROMPT. Exact resume argv: crush --session ID. Version check: crush --version.
Account paths: ~/.config/crush, ~/.local/share/crush. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Version/help only; native authentication and conversation resume were not executed. Observed native version: 0.98.1. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Current config uses crushrc files; earlier JSON config examples may differ. Project .crush state is inside workspace and must be preserved separately from account HOME. Native client/server session APIs have no kit transport or lifecycle installer.
Muse Code (`muse`)
Install in the Project container: curl -fsSL https://dev.meta.ai/install.sh | sh. Upstream platforms: linux, darwin, win32.
New interactive argv: muse. One-shot argv: muse exec PROMPT --json. Exact resume argv: muse resume ID. Version check: muse --version.
Account paths: ~/.config/muse, ~/.local/share/muse. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Headless restore uses exec --session-id; muse resume starts the interactive UI. --no-session-log disables retained-session restore. Native named hooks and muse serve protocol are not implemented by this adapter. Native session messaging is unavailable on Windows; workspace mismatch requires explicit native permission.
Prime Agent (`prime`)
Install in the Project container: curl -fsSL https://app.primeintellect.ai/prime-agent/install.sh | sh. Upstream platforms: linux, darwin, win32.
New interactive argv: prime-agent. One-shot argv: prime-agent --print PROMPT. Exact resume argv: prime-agent --resume ID. Version check: prime-agent --version.
Account paths: ~/.prime/agent. No managed native integration is installed; native identity must be supplied explicitly and semantic state remains unknown.
Verification: Not installed in the isolated verification prefix; only official source/docs and adapter fixtures verified. Billing, token usage and subscription balance are unavailable in this adapter.
Limitations: Source and documentation verified on 2026-10-12; authenticated interaction, native conversation restore, and end-to-end event delivery were not executed. Daemon-backed work can keep running after terminal detachment; disconnect does not prove idle/exited. agents is an interactive roster; no standalone JSON history format or kit hook installer is verified. Current documented Windows installer is x64; native latest version was not verified.
Antigravity account quotas
Accounts displays Antigravity's shared model-group quota buckets, including each native bucket's remaining percentage and reset time. Gemini, Claude/GPT and separately limited models can have different weekly or five-hour windows; they are not the allowances of a separate Claude or Codex account. One depleted group does not mark the entire Google account exhausted.
The package-owned collector uses the official read-only
agy --print /usage --output-format json command, available since 1.1.11.
It checks the installed version before invoking the slash command, then requires
a successful usage command envelope with zero turns, zero tokens and no new
conversation. Older or unrecognized versions are not queried. This path was
verified with the real 1.4.0 CLI without a generation request.
The collector runs as the account UID in a disposable private HOME and working directory. While a coding session is active, it copies only a still-valid access token and required native cache metadata. Hooks, MCP, project settings, API keys, overage preferences and conversation history are excluded.
An account with no active sessions remains eligible for background checks even if its retained workspace is stopped or its former container has been removed. The execution host creates a bounded account-only helper from its own management image, with no repository, workspace or Docker socket mount. Its private gateway allows required provider endpoints and honors the account's configured proxy/VPN. The original workspace and frozen session stay stopped. The trusted Antigravity binary cache retains only its selected version. Helper and gateway have a five-minute process deadline and are removed after success or failure; a later check reaps interrupted helpers before reuse.
Only this idle account path may pass a copied native refresh token to the
official zero-turn /usage command when its access token expires. It validates
the zero-turn response and renewed token, then atomically saves renewed native
authorization only if the canonical file still matches the original bytes.
Concurrent sign-in changes, pinned provider stores and transport failures retain
the existing authorization. No custom OAuth flow or model request is used.
The host refreshes every five minutes even when no console is open; Accounts also supports manual refresh on updated hosts. Errors retain the previous observation, which becomes stale after 15 minutes. The UI may show a last-known bucket until its official reset, explicitly marked as historical; it is never current quota evidence for launch or fallback. Missing values remain unknown, and passed reset times are not reused. Per-session token/cost accounting is still unavailable for Antigravity.
The read-only account observer runs as the exact account UID in an owned container. It refuses foreign/symlink credential files and emits only verified identity plus status. HTTP 403, missing scopes, proxy failures and expired tokens with a native refresh token retain the previous authorization rather than reporting logout. Native sign-in stays in the server's canonical private account store and can be reused by later sessions; a Project name is not an account name. User-defined display names remain optional overrides.
Sources: native authentication, native model quotas, official read-only JSON command release, Google OAuth2 userinfo discovery.
Opt-in native verification after deployment:
DEVCTL_TEST_LIVE_ANTIGRAVITY=1 \
DEVCTL_LIVE_ANTIGRAVITY_HOST=remote-server \
DEVCTL_LIVE_ANTIGRAVITY_WORKSPACE=workspace-id \
DEVCTL_LIVE_ANTIGRAVITY_ACCOUNT=google-account \
node --test packages/agent-cli-kit/antigravity-usage.live.test.mjs
This requires an already signed-in account with a valid access token; it does not log in, refresh credentials, generate an answer or restart a session. It is skipped in normal CI.
Antigravity tool permissions and networking
New managed Antigravity interactive/headless launches pass the upstream
--dangerously-skip-permissions flag, verified against native 1.4.0 --help and
official CLI documentation.
The terminal sandbox is not requested. This allows native tools inside the
managed environment; it does not remove devctrl network, filesystem, credential
or resource boundaries. Existing native processes keep their original arguments.
The Google profile-picture hostname *.googleusercontent.com is included in
required connectivity because the official CLI uses it during OAuth eligibility.
Account model preferences
Accounts → Models discovers the installed Claude/Codex/Antigravity model catalog. Native default is unpinned and version-dependent; explicit session settings win. Antigravity has an optional ordered shared-quota fallback chain. Its server-side continuation requires a verified native idle quota error, fresh exact quota evidence and an empty detached composer; agy1.2.6+ performs one native model-and-prompt continuation. Unsupported agent catalogs and unknown quota remain explicit.