A round vault door swung open onto an emerald-lit control room with a holographic globe
Vault Labs · Program mode

Two AIs build. They check each other. You hold the key.

Give it a brief. Plain code turns it into stages and small pieces of work. On every piece, one AI builds and the other reviews until it passes. You open the gates between stages and see only the requests that are actually risky.

You Bags · plain code Claude Codex
The chain of command

No AI is in charge

The controller is plain code, not an AI. It starts every session, enforces every limit and keeps the record. Each stage gets a fresh orchestrator, and a second model from a different company checks its big decisions.

You give the brief and hold the key. Bags, plain code, runs every step. Each stage has a Codex orchestrator whose big decisions a Claude auditor checks. Every work item runs as one loop between a Claude builder and a Codex reviewer. YOU · THE KEYThe brief, the stage gates, the big callsEverything else runs without you. BAGS · PLAIN CODE, NO AIStarts every step and enforces every rulebudgets · hash-locked gates · file fingerprints · alerts to your phone STAGE ORCHESTRATOR · CODEXPlans the stage, runs it item by itemNext item, retry with a better spec, or ask you. AUDITOR · CLAUDEChecks every big decision firstStage plans, retries, skips and final reports. WORK ITEMS · ONE LOOP EACHSmall, testable pieces of the stage ITEM 1 ITEM 2 ITEM 3 … BUILDER · CLAUDEPlans, then builds REVIEWER · CODEXReviews, then inspects You hold the key; Bags (plain code) runs every step; a Codex orchestrator per stage, checked by a Claude auditor; work items run as loops between a Claude builder and a Codex reviewer. YOU · THE KEYBrief, gates, big callsEverything else runs alone. BAGS · PLAIN CODERuns every stepEnforces every rule. ORCHESTRATOR · CODEXPlans and runs the stageOne item at a time. checked by AUDITOR · CLAUDEChecks big decisionsPlans, retries, reports. WORK ITEMSOne loop eachSmall, testable pieces. BUILDER · CLAUDEPlans, then builds build ⇄ review REVIEWER · CODEXReviews, then inspects
The loop

Every piece of work turns the dial

The builder never grades its own work. A model from another company reviews the plan before anything changes and inspects the real changes after. Disagreement sends it back around, up to a set number of rounds.

The loop as a vault dial: 1 Claude writes a plan, 2 Codex reviews it (and can send it back), 3 Bags locks that exact plan, 4 Claude builds, 5 Codex inspects the real changes (and can send them back for a fix), 6 the result goes to the orchestrator. ONE WORK ITEM THE LOOP build · review · repeat REVISE FIX 01PLANClaude The builder writes a plan.It changes nothing yet. 02REVIEWCodex The other model checks theplan against the real code. 03LOCKBags The gate approves thatexact plan, by its hash. 04BUILDClaude The builder builds andtests what the plan says. 05INSPECTCodex The other model readsthe real diff and tests it. 06DONEBags The result goes back tothe stage orchestrator. The loop dial: plan (Claude), review (Codex), lock (Bags), build (Claude), inspect (Codex), done (Bags), with revise and fix paths back. ONE ITEMLOOP 01PLANClaude 02REVIEWCodex 03LOCKBags 04BUILDClaude 05INSPECTCodex 06DONEBags
  1. 01Plan Claude
    The builder writes a plan. It changes nothing yet.
  2. 02Review Codex
    The other model checks the plan against the real code.
  3. 03Lock Bags
    The gate approves that exact plan, by its hash.
  4. 04Build Claude
    The builder builds and tests what the plan says.
  5. 05Inspect Codex
    The other model reads the real diff and tests it.
  6. 06Done Bags
    The result goes back to the stage orchestrator.
  7. ↺Revise / Fix
    Disagreement sends the plan or the changes back around, up to a set number of rounds.

Roles can swap (Codex builds, Claude reviews), and a loop can run audit-only: one model finds problems, the other confirms them, and nothing in the project changes.

The program

Four stages, four doors

A program runs in stages. Each ends with a report, checked by the auditor first, and a door only you can open. Choose how close you stay: approve every plan, only each stage, or just the last door.

Four stages: Scope, Build plan, Build, Review. Each ends at a gate only you can open. I SCOPE What exactly gets built YOUR KEY II BUILD PLAN The work, item by item YOUR KEY III BUILD Loops do the work YOUR KEY IV REVIEW Audit what was built YOUR KEY Four stages, each ending at a gate only you can open: Scope, Build plan, Build, Review. I SCOPE What exactlygets built YOUR KEY II BUILD PLAN The work, itemby item YOUR KEY III BUILD Loops dothe work YOUR KEY IV REVIEW Audit whatwas built YOUR KEY
Approvals

Who answers the knock

The AIs ask before they run anything. Three layers answer in order, so the stream of requests narrows to the few that need a human.

Who answers a request: the rules answer most of them instantly, the judge answers what stays inside the project, and only serious risks reach you. 1 · THE RULESBags, plain code Reads, tests and builds: allowed instantly 2 · THE JUDGEClaude, no tools Stays inside the project? Allowed, with a reason 3 · YOUCard + phone alert Serious risks only The rules answer most requests, the judge answers what stays inside the project, and only serious risks reach you. 1 · THE RULESBags, plain code Reads, tests, builds:allowed instantly 2 · THE JUDGEClaude, no tools Inside the project?Allowed, with a reason 3 · YOUCard + phone alert Serious risksonly
files outside the projectsecrets · keys · .envnetwork · uploadsdeleting outsidegit pushpackage installssystem settingscode the judge can't read

Some commands are blocked outright, and no one can approve them.

The locks

Built so it can't fool you

HASH-LOCKED GATES

You approve the exact text

An approval names the plan or report you read. Change one word and it no longer counts.

FINGERPRINTS

Nothing changes behind your back

The whole project is fingerprinted around every step. An unexpected change stops the program and calls you.

FAIL-CLOSED

When unsure, it asks

Anything the rules or the judge can't see in full goes to you, never to a guess.

BUDGETS

Bounded by design

Limits on loops per program and rounds per loop. Hit one and the program pauses for you.

FRESH CONTEXT

Never runs on a full head

At 70% of its memory an orchestrator writes a handoff, and a fresh one takes over. Nothing is squeezed.

SELF-CLEANING

Your chat list stays yours

Its own chats are labelled and, where the app allows, archive themselves a day after a good finish. Yours are never touched.

The Vault Labs floor: a giant vault door, a holographic globe and engineers at work
Inside the vault

A whole AI team. One key.

Brief it once, then step back. Two AIs from two companies build and check each other's work, plain code holds the rules, and you're called in only for the decisions that are yours.

VAULT LABSINSIDE THE VAULT