CONSOLE / MISSIONV0.6.5 / ON MAIN

Mission control for Claude Code.

Evidence before done.

A Claude Code plugin that shows the work as it really is: the milestones Claude reported, the agents the host observed, the checks that actually ran. A task reads DONE only when the evidence is in.

claude plugin marketplace add echelong/cobalt-cockpit

Then claude plugin install cobalt-cockpit@cobalt-cockpit, restart Claude Code and type /cockpit.

SIMULATED DEMO

01/13 STANDBY

Waiting for a prompt

000%IDLE
session start · no task recorded · HUD IDLE
OPUSSTANDBY· no subagent observed
IDLEno taskIDLE 0%
CODE ·TEST ·TYPE ·BUILD ·SECURITY ·GIT · · main model OPUS

STANDBY No task, no progress. The HUD shows nothing it has not observed.

Scripted from the repository’s own demo scenario and computed by a port of Cockpit’s completion, flow and readiness rules. How the demos work

VERSION
0.6.5
from .claude-plugin/plugin.json
DEFAULT MODE
OBSERVE
orchestration: false
OPTIONS
43
declared in the manifest
COMMANDS
26
documented in the README
NETWORK
NONE OF ITS OWN
see Safety and trust
LAST COMMIT
2026-10-16
main @ 2dbeaf1

01 / DOCTRINE

Five rules the plugin holds itself to.

Each one is a property of the code, stated in its documentation, with the page that says so.

  1. Observe by default.

    Installed as it ships, Cockpit watches the work Claude Code already does. It enforces no model routing, no subagent budget, no Fable block and no authentication rule until you switch one on. Two command guards are on from the start: it asks before genuinely destructive commands and keeps AI attribution out of commits.

    Where it says so
  2. Enforce by opt-in.

    orchestration: true enforces the Opus, Sonnet and Haiku policy, pool budgets and task ownership. blockFable, subscriptionOnly, cobaltStrict, the Stop guard and owner alerts are separate switches, each off until you choose it.

    Where it says so
  3. Evidence before DONE.

    A completed turn does not complete a task. DONE needs every milestone complete and every required gate passed or marked not applicable; for a coding task above the LIGHT level, a goal check with evidence for each acceptance criterion.

    Where it says so
  4. Never an approval.

    Cockpit takes no part in Claude Code’s permission check. Its guards run before it and can only refuse a call or ask you about it. Your permission rules still decide everything it lets through.

    Where it says so
  5. Local, with one exception you choose.

    No fetch, no model call, no MCP call of its own. The one program it starts that can reach a network is the decision router in JEV mode, and only in a session where you selected it.

    Where it says so

03 / BOUNDARIES

What it will not do.

Cockpit supplements Claude Code. It does not replace its permissions, its model controls or your judgement, and its guards are heuristics, not a sandbox.

Read the trust model
  • Approve a tool call

    There is no hook on the permission check. A guard refuses or asks; it never allows.

    Source
  • Call a model from the dashboard

    The HUD, Mission Control and the Ledger are drawn from what was observed. The dashboard makes no model calls.

    Source
  • Store hidden reasoning

    Tool calls, paths, agent events, usage, Git state and verification are observed. Hidden reasoning is never stored.

    Source
  • Call a claim verified

    Gates record observed exit status and reported evidence, and say which is which. That is a hold on progress, not a proof of correctness.

    Source

04 / START

Two commands, a restart, /cockpit.

claude plugin marketplace add echelong/cobalt-cockpit
claude plugin install cobalt-cockpit@cobalt-cockpit
/cockpitIn Claude Code, after a restart. It observes: models, budgets and ownership are not enforced until you configure them.
SITE HUDSOURCE / 2dbeaf1 · mainVERSION / 0.6.5 (manifest on main)SYNC / via GitHub APIHow this page stays current

Suggested

  • PAGEInstall

    Two commands, then /cockpit

  • PAGECommands

    Every documented command

  • PAGEConfiguration

    Every option and its default

  • PAGEDiscovery, decisions and goal check

    What DONE requires

  • PAGESafety and trust

    What Cockpit observes, stores and never approves