FalseGreen docs · Codex

Independent Codex Verification with FalseGreen

Frozen requirements in. Independent result out.

Connect Codex to FalseGreen and keep the coding agent separate from the final software-acceptance decision.

FalseGreen gives the coding agent a workflow for planning, freezing acceptance, implementation, independent verification, and durable evidence. The coding agent proposes and builds; the bounded acceptance result comes from FalseGreen.

01 · Authenticate FalseGreen

Install once, then log in.

cargo install falsegreen
falsegreen login --token YOUR_FALSEGREEN_KEY

The shim handles authentication, session credentials, and MCP configuration. The FalseGreen key does not belong in the editor configuration. Follow the install guide setup notes for local session behavior and logout.

02 · Install the Codex integration

Let the shim write the MCP configuration.

falsegreen install codex

After the shim writes the MCP configuration, reload Codex and ask it to list its available MCP tools before starting a long-running task.

03 · Run the Job workflow

Keep the coding agent and acceptance separate.

  1. Create the Job task and describe the consequential engineering outcome.
  2. Use the planning tools to revise and validate the plan.
  3. Freeze the plan and contract before the coding agent builds.
  4. Let Codex implement against the assignment.
  5. Run completion verification and retrieve the verification artifacts for the resulting run.

A completion message or passing self-test is builder-side evidence, not independent acceptance. Use the server-issued FalseGreen result as the authority.

04 · Preserve the result

Use the server-issued report as the authority.

FalseGreen artifacts can include the verdict, report ID, report URL, verified source identity, and server-generated pull-request summary. A result can be Accepted, Failed, or Insufficient Evidence, with scope and limitations attached to the evidence.

Back to install guideRead public proofSee FalseGreen JobGet support