cowork-deck

Free · Open source · macOS and Linux

Run many Claude Code sessions at once.

cowork-deck is a desktop app for running Claude Code sessions in parallel. Every session gets a tile with a real terminal in it, and the window answers one question at a glance: which of these needs me?

MIT licensed No account, key or subscription ~100 MB resident Runs your own claude

Five Claude Code sessions as tiles in one cowork-deck window — one working, one waiting for a decision, one finished, one stopped on an error, one idle — beside a panel holding workspaces and their sessions as one tree.
Five sessions, five states, one glance. The two readings in the top bar count the only two things that want a person. Every account, repository and path on screen is invented fixture data, shot with the project's own screenshot harness.

How to read a deck

Hue belongs to state, and to nothing else.

Green, amber and red mean working, waiting and broken. They are never spent on decoration — which is why there is not one coloured button on this page. A dozen sessions read in one sweep of the left edge.

Retry the refund webhook on a 410

ctx 83.7k working

* Resetting the backoff on restart…(21s · ↑ 2.1k tokens)

Review the diff

ctx 41.2k needs input

Do you want to proceed?❯ 1. Yes  2. No, tell Claude what to do

Nightly dependency sweep

ctx 118.4k done

Fourteen packages moved, the suiteis green, and #161 is open.

#128 · fix-flaky-timer

ctx 9.9k error

error: linker `cc` not found[process exited with code 101]

1 waiting for a decision 1 stopped on an error

The problem

A window full of terminals does not tell you which one is stuck.

01

Tabs hide state

A tab strip shows names, not states. The session that has been parked on a permission prompt for eleven minutes looks exactly like the one that is working.

02

tmux does not know what an agent is

A multiplexer splits panes. It has no idea that one of them finished a turn, that another is blocked on a decision, or what any of them has cost so far.

03

One account at a time

gh auth switch is global. Two projects on two GitHub accounts means switching, remembering to switch back, and eventually pushing as the wrong person.

Half a minute of the real thing

The deck never leaves the window.

A session finishes its turn and its rail changes live. One tile zooms near-full while the rest fall into a filmstrip. A workspace's board lists its repository's issues; a pull request unfolds into its diff.

Getting started

Three steps, and none of them is an account.

  1. Install Claude Code and log in as you normally would. cowork-deck runs the claude already on your machine.
  2. Download the app — a .dmg for macOS, an AppImage, .deb or .rpm for Linux. Windows means building from source for now.
  3. Point a workspace at a project folder. The first session starts there. Everything else — accounts, boards, scenarios — is optional and off until you turn it on.
The full installation guide, including the Gatekeeper note

Before you download

Three questions worth answering first.

Do I need an API key or a subscription to use cowork-deck?

No. cowork-deck runs the Claude Code you already have installed, on your own machine, under your own plan. It adds no account, no server and no cost of its own.

How many Claude Code sessions can run at the same time?

As many as your machine and your plan allow. The app itself uses around 100 MB of memory; each session is an ordinary claude process in a PTY, costing what it would cost in a terminal.

Is cowork-deck free and open source?

Yes. It is MIT-licensed and the whole application is in a public GitHub repository, including the screenshot harness the images on this site were shot with.

Every other question

Nothing to sign up for

Point it at a folder and start the first session.