Skip to content
codeArbitercodeArbiter

Governed autonomy for serious repositories

Hard gates for agentic coding.

One repository-owned governance layer for Claude Code, Codex, and Pi. Tests, reviews, security checks, decisions, and project context survive the host you use.

You decide. codeArbiter enforces.

Protect a repositoryWatch a verified hook replay
Claude CodeCodexPi preview

Direct hook evidence

A broad stage meets the shipped guard

Shipped H-03 hook
Verified direct hook invocation · Jul 30, 2026b2cf1a875a6e source digest
Read the exact invocation result

Attempted tool call git add -A

BLOCKED [H-03]: 'git add -A' / 'git add .' / 'git add --all' / 'git add -u' are prohibited. Stage files explicitly (commit-gate skill).

Exit 2 · command not executed · no staged files

Audit side effect The block appended an H-03 event to .codearbiter/gate-events.log.

Capture source plugins/ca/hooks/pre-bash.py at SHA-256 b2cf1a875a6ec0aa4c36e59bfdc2c9f64a81a70dcc901a5bbc46465b087e4873.

Evidence boundary This directly invoked the shipped hook with the host payload shape. It does not prove a host discovered or registered that hook.

The exact stderr and audit effect from a direct invocation of plugins/ca/hooks/pre-bash.py, rendered as a faithful replay. The denied staging command never ran. This evidence verifies the shipped guard itself, not host discovery or registration; the quickstart’s doctor probe verifies that end-to-end path.

Measured, not hand-typed

The shipped payload is the source of truth.

From first install to confident operation

A curriculum, not a pile of pages.

Follow one progressive route, perform a small exercise at each stage, and finish with a power-user capstone you can prove from repository state.

01

Foundation

Choose a host, install it, opt in, and verify a real block.

02

Daily operation

Pick the right lane for features, fixes, dependencies, and decisions.

03

Governed autonomy

Approve the target, inspect SMARTS calls, and keep the audit trail.

04

Power user

Trace hooks, tune scope, diagnose drift, and cut releases.

Start the complete learning path

What changes when codeArbiter is active

Autonomy with evidence attached.

Every guarantee is backed by a mechanism you can inspect.

Stops at the tool boundary

Host enforcement adapters run before shell and write calls. A blocking verdict prevents the call; it does not depend on the model remembering a prompt.

Inspect enforcement

State belongs to the repository

Specs, plans, decisions, tasks, questions, and audit records live in .codearbiter/. Change hosts without creating parallel memory.

Explore the state store

Bypasses leave a trail

Overrides, autonomous decisions, and checkpoint findings are durable artifacts. Audit a range from source records instead of reconstructing it later.

See the audit model

How work moves

Ask for the outcome. Keep the proof.

codeArbiter routes intent into the lane that owns it, scales the gates to the risk, and leaves a resumable record on disk.

Understand gated lanes
  1. 1

    State the work

    Feature, fix, sprint, dependency, decision, review, or release.

  2. 2

    Clear the lane

    Specs, tests, reviewers, and security checks appear only when the change needs them.

  3. 3

    Ship through a PR

    Commit evidence and review state travel with the branch. The default branch is never a direct write.

Start from the job, not the machinery

A clear entry point for the work in front of you.

/ca:feature

Build a capability

Turn an idea into an approved spec, test-first implementation, and reviewed PR.

/ca:fix

Repair a defect

Start from a reproduction, prove the regression, and make the smallest verified fix.

/ca:sprint

Run autonomously

Approve the target once, then let SMARTS-scored decisions drive the plan to a PR.

/ca:add-dep

Change the supply chain

Review license, provenance, and known vulnerabilities before installation.

/ca:adr

Record a decision

Capture a numbered, user-attributed decision with its governed paths and supersession chain.

40 commands

Find the exact route

Search the source-backed command, skill, agent, and hook-gate reference.

Choose your host

One policy core. Native entry points.

The project state is shared; command spelling and host capabilities are documented honestly.

Claude Code

stable
/ca:feature

Marketplace install, native plugin agents, hook trust flow, and optional rich statusline.

Install for Claude Code

Codex

stable
$ca-feature

The same enforcement decisions and state through Codex-native skills and hook verdicts.

Install for Codex

Pi

preview
/ca-feature

Git-installed Feature Forge preview with project trust, a rich footer, and supervised child dispatch.

Install the Pi preview

Need the exact differences? Read the compatibility matrix and the dated Claude Code + Codex verification record.

Fit before friction

Built for work that has to remain explainable.

codeArbiter adds deliberate process. That pays off when the repository outlives the current session, more than one person or host touches it, or a security and delivery claim needs evidence.

Use it when

  • agents implement meaningful product work;
  • decisions and bypasses need attribution;
  • tests and reviews must be real stops;
  • the same project moves between supported hosts.

Skip it when

  • the code is a disposable one-hour experiment;
  • any process friction is unacceptable;
  • the repository cannot carry a checked-in state directory.

Open source · AGPL-3.0-only · local enforcement

Protect a repository in five minutes.

Install for one host, opt the repository in, then run the live doctor probe.

Install codeArbiterRun the quickstart

No telemetry service is required for enforcement. Disable one repository or uninstall completely with the state implications documented.