Zero config · restores, never blocks

A seatbelt between your agent and your repo.

Start your agent inside the cage. Changes to CI configs, .env files and git hooks are put back while it runs, and pushes of them are refused.

What do you want to install?

Run the agent you already use inside the cage. It restores CI configs, .env files and git hooks/config while the session runs. No setup, no manifest. Needs Node 24+.


            
            npx @jeger-ai/opengantry-cage -- claude

Missions, gantry verify, MCP and hooks, with the cage included as gantry cage. curl and PowerShell bootstrap Node 24 if it is missing.


            
            npm install -g @jeger-ai/opengantry

How a cage session goes

  1. 01 · snapshot

    Before the agent starts

    Protected files are held in memory: CI workflows, .env files, .git/config, git hooks and anything in .cage.yaml. No manifest needed.

  2. 02 · restore

    While it works

    About once a second, cage puts back any change to a protected file. Lockfile changes are listed and kept.

  3. 03 · refuse

    When it tries to push

    A git push from inside the session is refused when the outgoing commits touch protected paths, and the agent sees why.

  4. 04 · halt

    When it keeps fighting

    An agent that rewrites the same protected file after three restores is stopped, along with everything it spawned. Exit 4.

  5. 05 · report

    When you quit

    One summary of everything restored and refused. Exit 3 if anything was touched; otherwise the agent's own exit code.

What it doesn't do: it restores rather than blocks, leaves git history as it is, and doesn't see reads, network calls or writes outside the protected paths. .cage.yaml adds your own paths and can only add protection; what it protects.

Step up to missions.

Scope on every write: allowed paths, forbidden paths and your gate command, committed to Git. Verify fails closed with machine-readable findings.

Your first mission 
  1. 
            
            gantry legislate "ship ingest retry" --msn MSN-0042
          
  2. 
            
            eval "$(gantry runtime env)"
          
  3. 
            
            gantry verify --json

For teams opt-in, on git refs

Org policy floor

A signed ORG-POLICY.yaml that can only tighten local law. Today only config_floor is enforced.

Compliance ledger

A digest-only chain on refs/gxt/ledger, exportable as a SOC 2 pack.

Cross-repo gates

depends_on is proved from a fetched ledger ref; a release waits until its dependency is verified.

Cage. Legislate. Verify.

Get started Read the docs