Skip to main content

​
Claude Code

Claude Code is an AI agent that takes consequential actions — running shell commands, editing files, opening PRs. The fact0-claude-code plugin makes those actions visible: it hooks every Claude Code lifecycle event (prompts, tool calls, permission decisions, subagents, session start/end), maps it to the Fact0 audit/telemetry schema, and ships it to Fact0. Each coding session becomes a hash-chained, queryable, governance-ready fact log — with zero per-session configuration.
  • Audit trail for AI-written code — who (agent vs. human vs. system) did what, when, against which resource, with what outcome.
  • Execution telemetry — each session maps to a Fact0 execution; turns and tool calls become spans with causality, including subagent nesting.
  • Governance — block dangerous tool calls before they run, and prove the decision afterward.

​
Install

Inside Claude Code:
Then set your API key once:
Every session on the machine now auto-logs. Run /fact0-status inside Claude Code to confirm capture is active.

​
What gets captured

Actor identity is audit-grade: agent for Claude itself, human for the developer (OS user by default, or FACT0_CC_ACTOR_ID / FACT0_CC_ACTOR_EMAIL), system for permission events.

​
Privacy model

Redaction happens on your machine before anything is sent, at one of three levels set by FACT0_CC_CAPTURE_MODE: The metadata default is what makes the Coding Agents dashboard view readable (Edit api/handler.go, Bash go test ./...) without shipping file contents. Use hash for locked-down environments.

​
Delivery guarantees

Hooks never block or slow the session, and a network blip does not lose events. When a send fails, the collector persists the payload to a local dead-letter queue and redelivers it automatically on a later hook invocation — oldest first, with original event timestamps preserved in the hash chain. Letters that fail 20 deliveries are kept for inspection but never retried. fact0-cc status reports the pending count. Executions self-heal too: if a session has no execution (the session-start call failed, or the plugin was installed mid-session), the next hook lazily starts one and telemetry resumes — no session ever permanently loses its trace.

​
Governance (block & prove)

Enforcement is off by default. Enable built-in safety rules (rm -rf, curl | sh, secret writes) and/or your own policy file:
Policy rules are {match, tool, action, reason} — a regex tested against the tool input. A matching deny blocks the tool call before it runs, and every decision (allow or deny) is recorded as a POLICY_EVALUATION span in the tamper-evident chain. Governance fails open: a bad policy file can never wedge a session — the failure is recorded instead. Verify the chain at any time:

​
Configuration

​
Agentless mode

For CI or locked-down hosts where shipping a binary isn’t possible, the plugin can POST events straight from Claude Code to POST /v1/integrations/claude-code using HTTP hooks. Note that raw payloads leave the machine before local redaction in this mode — prefer the default binary collector for secret-bearing environments.