Free · Open source · macOS and Linux

Run many Claude Code sessions at once.

cowork-deck is a desktop app that gives every session a tile with a real terminal in it, and answers one question at a glance: which of these needs me?

Download Source on GitHub

working waiting on you stopped on an error

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 bar down the left edge of each tile is its state, so a dozen sessions read in one sweep instead of a dozen labels. The two readings in the top bar count the only two things that want a person.

The problem

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

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.

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.

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.

Recorded against the project's screenshot harness, so every account, repository and path on screen is invented fixture data.

What it does

Six things a terminal cannot do for you.

Many sessions, one window

A dozen agents running at once, and one glance that says which of them needs you.

A GitHub account per project

Work and personal, side by side, without `gh auth switch` and without either one leaking into the other.

A board that starts sessions

Cards in your repo, or the repository’s issues. Either way, ▶ turns one into a running session.

Issues and pull requests

Issues open as documents. Pull requests carry their checks, their verdict and their diff.

Saved prompts, on a schedule

A prompt under a name, launched in one press — or hourly, daily, weekly, unattended.

The same setup everywhere

Your workspaces and scenarios follow you to the next machine, through a repository nobody else owns.

Getting started

Three steps, and none of them is an account.

Install Claude Code and log in as you normally would. cowork-deck runs the claude already on your machine.
Download the app — a .dmg for macOS, an AppImage, .deb or .rpm for Linux. Windows means building from source for now.
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.

Installation guide

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 →