Inspectrum

Inspectrum

Independent review before a risky agent change becomes hard to undo.

Claude plans it. GPT reviews it. You approve it.

---

A plausible plan can commit an agent to a migration, authentication change, payment flow, compatibility break, or deployment that is expensive to undo.

Inspectrum is an independent pre-flight check before that decision. Its first automatic integration runs when Claude Code exits plan mode: Codex (GPT) reviews the plan before the approval dialog reaches you, findings can send the plan back for revision, and you keep final approval. If the reviewer cannot run, the plan passes through with a visible warning instead of being silently reported as reviewed.

Here, independent means a reviewer distinct from the author model, invoked separately. It does not mean their errors are statistically independent. Inspectrum makes the checkpoint repeatable and its failures visible; a net reliability gain and a defensible moat are not yet proven. The post-0.2.2 strategy defines the evidence gates and keeps code review, pull-request review, and pair programming out of scope.

When a skill is enough

For an occasional second opinion, a rule can tell one agent to call another and compare the replies. That is a reasonable lightweight option.

Inspectrum is for the repeatable checkpoint. In Claude Code, the plugin runs at the plan-to-execution boundary without relying on a remembered prompt, caps revision loops, and fails open on operational errors. Other local MCP hosts can call the same review_plan contract on demand. Both paths keep findings attributed, return a common verdict shape, preserve human control, and write local evidence for successful reviews.

Recreating those guarantees with a skill means maintaining the orchestration, output validation, health checks, failure policy, and session record yourself.

Public availability as of 1 August 2026: npm 0.2.3, the GitHub release, and the repository's Claude and Codex plugins are aligned on 0.2.3. Glama is public. The MCP Registry may still show 0.2.2; it was not republished in this pass. Inspectrum was not in the public Claude Community catalog, while PulseMCP blocked the one-time recheck with HTTP 403, so no current PulseMCP listing claim is made.

The public 0.2.3 activation evidence records exact commands, timings, one useful finding, one null result, one visible fail-open case, and the limits of the measurement.

Quick start

You need Node 20+, Claude Code, and Codex CLI >= 0.99.0 authenticated with a ChatGPT subscription (no API key):

claude plugin marketplace add yannmenec/inspectrum

claude plugin install inspectrum@inspectrum

That's the whole install. Next time you finish a plan in plan mode:

⏺ ExitPlanMode

⎿ inspectrum×codex: REVISE (round 1/2) # abridged — real output Majors: # adds a full-report path

• [codex] Migration drops the unique index before backfilling — concurrent writes can insert duplicates. Fix: backfill first, drop the index last. Revise the plan to address these findings, then finish the plan again.

⏺ ExitPlanMode ⎿ inspectrum: codex approved the plan (session 2026-07-12…). ┌ Ready to code? ──────────────── │ Here is Claude's plan… ← your normal approval dialog

No prompt to remember, no button, zero tokens spent on triggering. The gate is a deterministic hook — it fires on every plan, whether your session runs Fable, Sonnet, or Haiku. Two commands give you the automatic gate; the on-demand /inspectrum:review command needs one extra line (registering the MCP server — shown in the assisted setup below).

Prefer the agent to install and check everything for you? Paste this into Claude Code.

Set up Inspectrum's Codex plan gate. Use normal approvals only — do not

switch to Bypass Permissions or Full Access.

Steps:

1. Run node --version. If < 20, stop and tell me to install Node 20+ from https://nodejs.org first.
2. Run codex --version. If it is missing or older than 0.99.0, run npm install -g @openai/codex@latest and verify again.
3. Run claude plugin marketplace add yannmenec/inspectrum, then claude plugin install inspectrum@inspectrum.
4. Run claude mcp add --transport stdio --scope user inspectrum -- npx -y inspectrum@latest (this powers the on-demand /inspectrum:review command).
5. Run npx -y inspectrum@latest doctor and show me the output, including the resolved codex model/effort lines.
6. Run codex login status.

• If it prints "Logged in", tell me: "✅ Setup complete. Your next plan-mode plan gets a Codex review automatically." Done.
• Otherwise (not logged in), pop open a Terminal window with codex already running by executing: osascript -e 'tell application "Terminal" to do script "codex"' Then tell me: "A Terminal window opened with codex running. Inside that window, click 'Sign in with ChatGPT', complete the login in my browser, then close the Terminal window. Inspectrum is then ready."

Do NOT use sudo, edit shell profiles, push git changes, read .env or credentials, or publish packages. Report back: Node version, codex install status, doctor verdict, and whether login was needed.

How it works

you ──▶ Claude Code ──▶ plan ready ──▶ ExitPlanMode

│ inspectrum plan-gate (hook) │ Codex reviews the plan (read-only sandbox, your ChatGPT sub) │ ┌─────────────────────┴──────────────────────┐ APPROVE ✅ REVISE / REJECT ❌ │ │ your approval dialog findings go back to Claude, appears as usual it revises, gate runs again (max 2 rounds)

Built to be boring and safe:

• Fails open. Codex not installed, logged out, timed out, network down — the plan proceeds with a visible warning. Operational errors don't block your work; the gate degrades, it doesn't brick.
• Never auto-approves. A green review still lands on *your* approval dialog. The gate can delay it (while Claude revises) but can never click it — you keep the final call.
• No wasted reviews. Within a session, an unchanged plan is hash-cached and not re-reviewed; only real revisions spend a round.
• Read-only reviewer. Codex runs in a pinned read-only sandbox (codex exec -s read-only --ephemeral), and sandbox-weakening flags in your config are stripped. The reviewer reads; it doesn't write.
• Kill switch. [plan_gate] enabled = false in ~/.inspectrum/config.toml, or disable the plugin per project.

Why a separate reviewer?

• Plans are leverage. A flaw caught before execution can be cheaper to fix than the same flaw found after a difficult-to-reverse change.
• Separation makes the check inspectable. The author and reviewer run independently, and findings remain attributed.
• Cross-provider value is a hypothesis. Claude and GPT can raise different objections, but Inspectrum has not yet proved that this produces a net reliability gain after false positives, triage, cost, and latency.
• Use an existing subscription. No separate API bill when using your ChatGPT subscription; reviews consume your existing Codex subscription allowance. API-key backends are billed by their provider.

What's in the box

Works with

Codex app / CLI setup — use Claude as your reviewer

Paste this into the Codex app or CLI:

Set up Inspectrum so I can review my plans with Claude. Use normal

approvals only.

Steps:

1. Run node --version. If < 20, stop and tell me to install Node 20+ from https://nodejs.org first.
2. Run claude --version. If "command not found", run npm install -g @anthropic-ai/claude-code and verify again.
3. If ~/.inspectrum/config.toml does not exist, create it with:

[defaults] reviewers = ["claude"]

1. Run codex mcp add inspectrum -- npx -y inspectrum@latest
2. Run npx -y inspectrum@latest doctor and show me the output.
3. Pop open a Terminal window with claude already running so I can confirm or complete login, by executing: osascript -e 'tell application "Terminal" to do script "claude"' Then tell me:

• "If claude shows its chat prompt, you're already logged in — close the Terminal window. Inspectrum is ready."
• "If claude shows /login or opens a browser, complete the sign-in with your Claude account, then close the Terminal window. Inspectrum is then ready." (The ⚠ claude line in the doctor stays even after login because claude doesn't expose a status command we can detect — harmless.)

Do NOT use sudo, edit shell profiles, push git changes, read .env or credentials, or publish packages. Report back: Node version, claude install status, doctor verdict, and whether login was needed.

Needs a Claude Pro/Max subscription — no API key.

Tuning

Which model reviews, at which effort? On the Codex side, precedence is:

| reasoning effort | [reviewers.codex] effort | model_reasoning_effort