AI coding agent harness compatibility

Support varies by adapter and event surface. HOL Guard provides native enforcement for harnesses with native approval, browser fallback, and auto-resume (codex, claude-code, copilot, pi). Other harnesses are protected through wrapper or overlay mode with advisory detection. See the limitations for each adapter below.

Legend: support status vocabulary
Native enforcement
Guard hooks into the native approval flow, provides a browser fallback, and can auto-resume after a crash or restart.
Managed hook or proxy
Guard intercepts actions through a native hook or proxy but cannot automatically resume the session after an interruption.
Wrapper or overlay
Guard wraps or overlays the tool and provides a browser fallback, but does not hook into the native approval flow.
Detect or advisory only
Guard observes and advises but does not enforce. Manual review is required for actions Guard cannot block natively.
HOL Guard compatibility matrix for 13 supported AI coding agent harnesses
ToolAliasesStatusIntegration modeNative approvalBrowser fallbackTerminal fallbackAuto-resumeEvent surfacesBlind spotsGuideConstraints
CodexcodexNative enforcementNative hookYesYesYesYesshell · prompt · mcp_tool · file_read · tool_resultInline file edits applied directly by the model without a tool call are not visible to Guard.Guide →~/.codex/config.toml
Claude Codeclaude-code · claudeNative enforcementNative hookYesYesYesYesshell · prompt · mcp_tool · file_read · tool_resultBackground agent sessions that run without an active terminal do not surface hook events to Guard.Guide →~/.claude/settings.json, ~/.claude/settings.local.json
OpenCodeopencodeWrapper or overlayWrapper overlayNoYesYesNoshell · mcp_toolPrompt content is not currently surfaced through hooks. File read/write events bypass Guard unless OpenCode permission rules block them.Guide →~/.config/opencode/config.json
GitHub Copilot CLIcopilotNative enforcementNative hookYesYesYesYesshell · promptMCP tool calls routed through the VS Code extension are not visible to the CLI-level Guard hook.Guide →~/.config/gh/hosts.yml
CursorcursorWrapper or overlayWrapper overlayNoYesYesNoshell · mcp_tool · file_readShell commands issued through Cursor's built-in terminal bypass Guard unless the terminal runs inside an agent session. Prompt submission is not surfaced through native Cursor hooks.Guide →~/.cursor/mcp.json, ~/.cursor/hooks.json, .cursor/hooks.json
Gemini CLIgeminiWrapper or overlayWrapper overlayNoYesYesNoshell · mcp_toolPrompt submission events and file read/write operations are not currently observable through the Gemini hook surface.Guide →~/.gemini/settings.json
HermeshermesWrapper or overlayWrapper overlayNoYesYesNoshell · mcp_tool · promptHermes is an early-access harness; some event surface coverage depends on the Hermes version installed.Guide →
OpenClawopenclawWrapper or overlayWrapper overlayNoYesNoNomcp_toolShell commands and prompt events are not currently observable. Guard only intercepts MCP tool calls via the proxy layer.Guide →~/.openclaw/config.json
AntigravityantigravityWrapper or overlayWrapper overlayNoYesNoNomcp_tool · promptShell commands are not currently observable through the Antigravity hook surface. Guard intercepts extensions and MCP registrations via scan at launch time.Guide →~/.config/antigravity/user/settings.json, ~/.gemini/antigravity/mcp_config.json, ~/.antigravity/extensions/extensions.json
Kimi Codekimi · kimi-code · kimi-cliWrapper or overlayWrapper overlayNoYesYesNoshell · promptTool output post-processing and inline edits applied without a tool call are not visible to Guard. Hooks run in parallel and fail open on crash or timeout.Guide →~/.kimi-code/config.toml
Grok Buildgrok · grok-build · grok-build-cli · xai-grokWrapper or overlayWrapper overlayNoYesYesNoshell · prompt · mcp_tool · file_readGrok hooks fail open on crash or timeout. --always-approve and bypassPermissions weaken prompt policy but PreToolUse hooks still run when installed.Guide →~/.grok/config.toml, ~/.grok/managed_config.toml, ~/.grok/hooks/
Pi / Oh My Pipi · pi-agent · pi-coding-agent · omp · oh-my-piNative enforcementNative hookYesYesYesYesshell · prompt · mcp_tool · file_read · tool_resultPi package install and update flows happen outside the runtime extension bridge, so Guard observes the configured package surfaces plus the prompt and tool events forwarded by the managed extension.Guide →~/.pi/agent/settings.json, .pi/settings.json, ~/.pi/agent/extensions/*.ts, .pi/extensions/*.ts, ~/.omp/agent/settings.json, .omp/settings.json, ~/.omp/agent/extensions/*.ts, .omp/extensions/*.ts
Z Codezcode · zai · z-code · zai-zcodeWrapper or overlayWrapper overlayNoYesYesNoshell · prompt · mcp_tool · file_readInline edits applied directly by the model without a tool call are not visible to Guard, and background sessions that run without an active terminal do not surface hook events.Guide →~/.zcode/cli/config.json, ~/.zcode/cli/plugins/

Planned

Planned

Goose is on the roadmap but no Guard adapter ships yet. Once Goose stabilizes its hook surface, Guard will provide MCP tool interception and shell event observation. No install command is available today.

Explicitly not supported

  • Not supported

    VS Code Copilot extension (GUI mode): Guard hooks the Copilot CLI, not the VS Code extension panel. MCP tool calls routed through the extension are not visible to the CLI-level hook. See the Copilot harness guide for the CLI-only integration path.

  • Not supported

    Goose: No Guard adapter ships yet. Goose is listed as planned above.