Free · local · no account

One harness to
rule them all

Cockpit puts Claude Code and Codex side by side in one window. See what every session is doing, answer the ones waiting on you, start new ones, and keep hundreds organized, without a wall of terminal tabs. No account, nothing uploaded, and it's free.

See how it works

Your keys, your machine · nothing leaves your Mac

Cockpit's board: every Claude Code and Codex session as a card, grouped by when it was last touched, with red badges on the ones waiting for a reply.

The idea

Not another agent. The one place for the ones you already run.

A harness is the tool wrapped around the model, Claude Code or Codex. Run a few and you're soon drowning in terminal tabs, unable to tell which one finished and which is quietly waiting on you. Cockpit reads the transcripts those tools already write to disk and lays them out in one window. It sits above your harnesses, it doesn't replace them, and it changes nothing about how you run them.

Attention

See what's waiting. Answer in one screen.

The hard part was never the coding, it's telling which session finished and which is sitting on a permission prompt you never saw. Attention is one table of the sessions that need you, from either tool, each with a reply box.

  • Claude Code and Codex in one list
  • A red badge the moment a session needs you
  • Reply, approve a permission, or stop a run with ⌘.
Cockpit's Attention view: a table of the sessions waiting on you, from Claude Code and Codex, each with a reply box.

Start work

Start a session without opening a terminal.

Hit +, pick a directory, type a first instruction, and choose Claude Code or Codex. The card lands on the board and you talk to it there, no new tab to lose track of.

  • Start Claude Code or Codex from the app
  • Recent directories one click away
  • Paste images straight in with ⌘V
Starting a new session in Cockpit: pick a directory, write a first instruction, and choose Claude Code or Codex.

Every session

Open one and read the whole story.

A summary and a "where we are" at the top, then the transcript, readably. The files the agent wrote become tabs, each with a version timeline you can diff and restore from. Select a passage, say what's wrong, and send it back.

  • A summary, not a wall of logs
  • Files as tabs, every write kept and versioned
  • Add your own document viewers as drop-in plugins
An open session in Cockpit: transcript, a summary up top, and the agent's files as tabs with a version timeline.

At scale

Keep hundreds of them in order.

Drag a card into a category; rename, recolour, and add sub-categories from its own icon. Pin the flows you keep coming back to. Weeks later the thread is right where you left it, searchable, not lost in a closed terminal.

  • Categories with colours, icons, and sub-categories
  • Pin the recurring flows
  • Search across every session, past and present
Cockpit's Categories view: sessions filed into colour-coded categories with sub-categories.

Documents · new in 0.1.2

Work with what the agent wrote, don't just read it.

Comment for targeted changes

Select any passage in a file, say what's wrong, and it goes straight back to the session that wrote it, one note or a whole batch as a single message. No copy-pasting diffs into a terminal.

Full version history

Every write the agent makes is kept. Each file has a timeline you can read backwards, diff, and Restore from, for when an update breaks something that was working.

Viewers, including .docx

Markdown, CSV, images and more render as documents, not raw text. Add a viewer for a new type as a drop-in plugin that lives outside the app, so an update never removes it.

Nothing leaves your Mac.

No account, no telemetry, no cloud. The only thing that goes out is a prompt to the model you picked, with your own API key, kept in a local file on your machine. Cockpit reads your sessions; it never sends them anywhere.

Get every session in one window.

It's free, it's local, and it opens with a double-click. Grab the app, or read the guide first.

macOS · Apple silicon and Intel

Free because you bring your own API keys: you pay the model provider directly, and there's no server for us to run or data for us to sell.

Get in touch

Questions, press, or early access?

Send a note and it lands straight in our inbox. Or email support@aidash.dev.