Non-coverage contract

What HOL Guard does not claim to cover

Guard coverage is harness-, version-, and event-specific. This page makes fail-open behavior and observable blind spots first-class public facts instead of allowing “supported” to imply universal protection.

See the full stable and alpha coverage table.

Global coverage boundaries

Category non-claims

  • traditional endpoint antivirus
  • universal model-level prompt-injection filter
  • replacement for SCA or dependency scanning
  • support for every action in every harness

Channel limitations

  • stable: Coverage is harness- and event-specific.
  • stable: Scanning and runtime interception are separate controls.
  • stable: Guard does not claim universal model-level prompt filtering.
  • alpha: Alpha capabilities must be labeled alpha on public pages.
  • alpha: Coverage is harness- and event-specific.
  • alpha: Guard does not claim universal model-level prompt filtering.

Fail-open, crash, timeout, and blind-spot facts

These facts are derived from the same commit-pinned support contract used by the coverage table.

ChannelHarnessFail behaviorKnown boundaryEvidence
stableCodexsurface specificInline edits without a tool call are outside the contract.source commit
stableClaude Codesurface specificBackground sessions without an active terminal may not surface hook events.source commit
stableOpenCodesurface specificPrompt and direct file operations are not universally visible.source commit
stableGitHub Copilot CLIsurface specificVS Code extension-host MCP interception is not claimed.source commit
stableCursorsurface specificBuilt-in terminal commands outside an agent session can bypass Guard.source commit
stableGemini CLIsurface specificPrompt submission and direct file operations are not universally observable.source commit
stableHermessurface specificEarly-access coverage depends on Hermes version.source commit
stableOpenClawsurface specificShell and prompt events are not currently observable through the contract.source commit
stableAntigravitysurface specificShell actions are not currently observable through the Antigravity hook surface.source commit
stableKimi Codefail openThe pinned support contract marks this adapter fail-open; a hook failure must not be described as fail-closed protection.source commit
stableKimi Codefail openHook crashes or timeouts fail open.source commit
stableGrok Buildfail openThe pinned support contract marks this adapter fail-open; a hook failure must not be described as fail-closed protection.source commit
stableGrok Buildfail openHook crashes or timeouts fail open.source commit
stablePisurface specificPackage install and update flows occur outside the runtime extension bridge.source commit
stableOh My Pisurface specificPackage install and update flows occur outside the runtime extension bridge.source commit
stableZCodefail openThe pinned support contract marks this adapter fail-open; a hook failure must not be described as fail-closed protection.source commit
stableZCodefail openInline edits without a tool call are outside the contract.source commit
alphaCodexsurface specificInline edits without a tool call are outside the contract.source commit
alphaClaude Codesurface specificBackground sessions without an active terminal may not surface hook events.source commit
alphaOpenCodesurface specificPrompt and direct file operations are not universally visible.source commit
alphaGitHub Copilot CLIsurface specificVS Code extension-host MCP interception is not claimed.source commit
alphaCursorsurface specificBuilt-in terminal commands outside an agent session can bypass Guard.source commit
alphaClinesurface specificPostToolUse native hooks are observation-only; full output mediation requires the managed plugin transport.source commit
alphaGemini CLIsurface specificPrompt submission and direct file operations are not universally observable.source commit
alphaHermessurface specificEarly-access coverage depends on Hermes version.source commit
alphaOpenClawsurface specificShell and prompt events are not currently observable through the contract.source commit
alphaAntigravitysurface specificShell actions are not currently observable through the Antigravity hook surface.source commit
alphaKimi Codefail openThe pinned support contract marks this adapter fail-open; a hook failure must not be described as fail-closed protection.source commit
alphaKimi Codefail openHook crashes or timeouts fail open.source commit
alphaGrok Buildfail openThe pinned support contract marks this adapter fail-open; a hook failure must not be described as fail-closed protection.source commit
alphaGrok Buildfail openHook crashes or timeouts fail open.source commit
alphaPisurface specificPackage install and update flows occur outside the runtime extension bridge.source commit
alphaOh My Pisurface specificPackage install and update flows occur outside the runtime extension bridge.source commit
alphaZCodefail openThe pinned support contract marks this adapter fail-open; a hook failure must not be described as fail-closed protection.source commit
alphaZCodefail openInline edits without a tool call are outside the contract.source commit

How to interpret a gap

A partial or unsupported surface means the public evidence does not justify describing that action as protected. It does not mean the harness is unsafe, and it does not mean another control cannot cover the gap. Coverage changes must update the commit-pinned support manifest before this page or comparison content can claim the new behavior.