Every question, permission and plan from all your sessions lands in one queue, with only the context it needs. One key each. You decide; you don't reread.
2-minute install · no account · runs on the Claude plan you already have · macOS, Windows, Linux
Grey and calm until something needs you.
The real app, no sound. Play the full 45-second film with its score ▶
In a terminal you rebuild the context for every decision. In Cockpit it arrives with the question, and the safe answer is one key.
Which table? Which database? Scroll up and find out, in one of eight tabs.


Production, CASCADE, high risk. Press D, and Claude comes back with a safer plan.
Reading is the tiring part. A terminal makes you rebuild the context for every decision. Cockpit brings it with the question and leaves everything else out.
“The difference I didn't expect was how much less tired I was. Each decision arrives with only the context it needs, so I'm not rebuilding it from scrollback every time.”
Bohdan Kostko, who built Cockpit
My own numbers: 25 days in terminals vs the first 4 days in Cockpit. A small sample, and most of that week went into building Cockpit itself. Measured from session file timestamps; no content was read.
Four moments where Cockpit saves you the reading.
Questions, permissions and plan approvals from every session, oldest first. Press 1–3 to pick, A to allow, D to deny. The session carries on by itself.

Claude says "drop the old invoices table." The card shows the rest: it's production, and it's CASCADE. Press D, and Claude comes back with a safer plan instead of a restore from backup.


Press ⌘⇧U on any session for a one-page catch-up: where it is, what it decided without asking, and which claims the log doesn't back up. "All 211 tests pass" with no test in the log is flagged before you open a PR.

Ask Claude to plan before it codes and you get a one-page map: goal, scope, design, risks and open questions, each drawn the way it reads best. Mark it up, send every note at once, then hit Build from doc.

Change mapEvery session's plan with live progress, and the files it touched grouped by folder. Auth and migrations are flagged.
TimelineWhat every session did, what it does next, and who will need you in the next 15 minutes.
PR review, one finding at a timeRiskiest snippets first; one key turns a finding into a review comment. Address mode turns reviewer threads into fixes.Cockpit drives the Claude Code you already use, through Anthropic's official Agent SDK, signed in as you. Your skills, hooks and settings all keep working.
You need Claude Code, signed in. Don't have it yet?
Prefer a normal download? Pick yours below.
xattr -dr com.apple.quarantine /Applications/Cockpit.app once.Yes. Cockpit is MIT licensed. Your sessions use your existing Claude plan (Pro, Max, Team or API), exactly as they do in a terminal.
Yes. Cockpit runs your real Claude Code with your real setup. Workspaces keep memory and history separate per client while sharing your skills and settings.
The full transcript is one key away (⌘R), and every approval shows the exact command before it runs.
They help you run agents in parallel. Cockpit is about deciding: one queue across every session, one key per answer, risky commands and unbacked claims flagged before you act. It runs locally on your own Claude Code, with no account and no cloud.
Each session gets its own checkout so edits never collide, while it uses your normal machine, tools and Claude setup. Like any fresh clone, a worktree may need its dependencies installed; ask the session, or note it in your project's CLAUDE.md. Prefer your own checkout? Turn worktrees off when you start a session. Review and Address always run in your existing clone.
No. Cockpit is an independent open-source project built on Anthropic's public Agent SDK. "Claude" and "Claude Code" are trademarks of Anthropic.
Please do: git clone https://github.com/getcockpit/cockpit && ./scripts/dev.sh. See CONTRIBUTING.md.
Free, open source, and running in two minutes.