Inspectrum

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/inspectrumclaude 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).

Set up Inspectrum's Codex plan gate. Use normal approvals only — do notswitch 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 orcredentials, or publish packages. Report back: Node version, codexinstall 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

Set up Inspectrum so I can review my plans with Claude. Use normalapprovals 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"]
4. Run `codex mcp add inspectrum -- npx -y inspectrum@latest`5. Run `npx -y inspectrum@latest doctor` and show me the output.6. 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 orcredentials, or publish packages. Report back: Node version, claudeinstall status, doctor verdict, and whether login was needed.

Tuning

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

inspectrum doctor prints the resolved values. High effort gives the deepest reviews but can take minutes per plan — drop to effort = "medium" in [reviewers.codex] if the gate feels slow.

[defaults]reviewers = ["codex", "gemini"]   # called in paralleljudge     = "codex"               # consolidates when >= 2 reviewersfocus     = "all"                 # correctness | completeness | risk | clarity | all
[plan_gate]                       # ExitPlanMode hook behaviorenabled          = truemax_rounds       = 2              # denials before the plan passes throughreason_max_chars = 3000           # budget for findings fed back to Claude# reviewers      = ["codex"]      # gate-specific override of defaults.reviewers
[reviewers.codex]effort          = "high"          # passed as -c model_reasoning_effort=hightimeout_seconds = 300             # per-reviewer override of limits.timeout_seconds# model         = "gpt-5.6-sol"   # passed as -m; omit to inherit ~/.codex/config.toml
[reviewers.gemini]type   = "cli"binary = "gemini"model  = "gemini-2.5-pro"
[reviewers.muse]type   = "cli"binary = "muse"                   # muse exec, prompt passed via --prompt-file# model  = "..."                  # omit to inherit muse's own default# effort = "high"                 # passed as --reasoning-effort
[reviewers.opencode]type   = "cli"binary = "opencode"               # opencode run, prompt on stdin# model  = "google/gemini-2.5-flash"   # -m, provider/model form# effort = "high"                 # passed as --variant
[reviewers.agy]type   = "cli"binary = "agy"                    # schema-constrained structured output# model  = "..."                  # passed as --model# effort = "high"                 # --effort; only some models accept it
[reviewers.grok]type   = "cli"binary = "grok"                   # confined to a read-only tool allow-list# model  = "grok-4.6-build"       # passed as -m# effort = "high"                 # passed as --effort
[reviewers.local]type     = "http"backend  = "ollama"endpoint = "http://localhost:11434"model    = "qwen2.5:0.5b"
[limits]report_max_chars = 8000           # caps the stored reporttimeout_seconds  = 300            # default reviewer wallclock

# Register the MCP server without the plugin:claude mcp add --transport stdio --scope user inspectrum -- npx -y inspectrum@latest   # Claude Codecodex mcp add inspectrum -- npx -y inspectrum@latest                                   # Codex
# The automatic plan gate must use the plugin's pinned fail-open shim; do not# register plan-gate through a mutable npm tag.
# Verify everything:npx -y inspectrum@latest doctor

FAQ

Does this slow me down? Only when it should. An approve verdict adds one review pass (seconds to a couple of minutes depending on effort); a bounced plan was a plan you wanted bounced. Within a session, an unchanged plan is cached and not re-reviewed.

What if Codex is down / logged out / not installed? The gate fails open with a visible warning and your plan proceeds untouched. An operational error never blocks your work — that's an architecture invariant, not a best effort.

Can it approve a plan behind my back? No. The gate can only delay the approval dialog (while Claude revises) — it can never click it. You see and approve every plan that ships.

Do I need API keys? Not for subscription-backed Codex or Claude CLI logins. Reviews consume the allowance of the existing subscription. API keys are supported for headless/CI setups and are billed by their provider.

My prompt/plan is sensitive — where does it go? To the reviewer(s) you configured, and to a local session log under ~/.inspectrum/sessions/ (0700). Nothing else. Use ollama for a fully local, zero-egress reviewer.

Troubleshooting

sh: inspectrum: command not found / claude mcp list shows ✗ Failed to connect — but only when your current directory is the Inspectrum repo itself. npx inspectrum@<version> resolves the spec against the local package when cwd is inside a package named inspectrum whose version matches, and a package's own bin is never self-linked into its node_modules/.bin. The published package is fine. Fixes: run from any other directory, or install the real binary once and register that instead:

npm install -g inspectrumclaude mcp add --transport stdio --scope user inspectrum -- inspectrum

Gate feels slow? Set effort = "medium" in [reviewers.codex] (see Tuning). Something else? npx -y inspectrum@latest doctor diagnoses install, login, and model resolution in one shot — open an issue with its output.