Independent Codex Verification with FalseGreen

01 · Authenticate FalseGreen

Install once, then log in.

cargo install falsegreen
falsegreen login --token YOUR_FALSEGREEN_KEY

The client manages 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 client write the MCP configuration.

falsegreen install codex

After the client 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 AI coding agent and acceptance separate.

1. Create the Job (falsegreen_create_job) with the goal, the acceptance criteria, and — for pull-request work — the change request. The client freezes the source, contract, and criteria; none of them can change mid-verification.
2. Let Codex implement against the frozen assignment.
3. Start verification (falsegreen_verify_job) and wait for the attempt to complete.
4. If the result is Failed, fix the work and continue the repair repair (falsegreen_repair_job) — same Job, fresh attempt, capped at the attempt budget.
5. Read the result (falsegreen_get_report): the report carries the verdict, the scope, and the evidence.

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.