- Run and direct many coding agents at once, across harnesses, models and machines.
- Carry work from a conversation or an issue to a merged pull request.
- See what every agent is doing and what it changed.
Get started
Try Overdeck without installing anything. This starts Overdeck and opens the dashboard in your browser:overdeck and pan commands, run the install script. It needs Node.js 22.16 or later, installs with npm into ~/.local, and does not use sudo:
pan is the short name for overdeck. Both run the same CLI. Next, follow the Quickstart to add a project and start your first agent.
What Overdeck does
Conversations with your code
Start a conversation with an agent in any project and steer it while it works. Each turn shows the files it changed, and the diffs, files and commits sit beside the chat. See Conversations and the file explorer.The issue pipeline
pan start <issue> plans the issue, makes an isolated workspace for it, and starts a work agent. Review agents check the work. The pull request merges when it is approved and its checks are green: you click Merge, or auto-merge does it for you. Issues come from GitHub, Linear, Rally or Jira, and code can live on GitHub or GitLab. See the issue pipeline, Planning, the review convoy, merge batches, auto-merge and issue trackers.
Order books and the Flywheel (early)
The Flywheel is a loop that runs in one conversation. It picks the next issue from your order books and backlog, starts work on it, watches the pull request until it lands, and parks what it cannot decide for you. The Flywheel is early. See the Flywheel, order books and the Flywheel vision.Harnesses and models
Agents run on the coding-agent CLI you choose: Claude Code, Codex, Pi, OpenCode, Kimi Code, Grok Build and others. You pick the model for each role in the pipeline. See harnesses and model presets.Overdeck Anywhere
Every machine runs its own Overdeck. Link your machines to see all of their conversations in one list, move a conversation to another machine, and answer agents from your phone. overdeck.ai accounts are invite-only for now. See Overdeck Anywhere.Seeing the work
Needs you collects every question, plan and permission prompt that waits on you. The Board shows every issue by its state. Each conversation and issue shows its cost at API rates, so the cost on a subscription plan can differ. See Command Deck. For every view, see Dashboard views.Skills, memory and rules
pan sync gives every supported harness the bundled skills, and you can turn each skill on or off per project, issue or conversation. Project memory keeps curated facts in your repo, and context layers deliver your rules to each agent when it starts. See skills, memory and context layers.
For the full list, see the features page on overdeck.ai and the CLI reference.
A short history
Overdeck started in January 2026 as Panopticon. The name came from the Panopticon in Doctor Who, the great hall of the Capitol on Gallifrey where the Time Lords gather. The command waspan and the npm package was panopticon-cli.
In April 2026 the zero-install launcher shipped as @panctl/cli. In June 2026 the project was renamed Overdeck, and on June 20, 2026 the package became @overdeck/core. The new name has no Doctor Who meaning. pan stayed as the short command and overdeck is the long one. That is also why planning files in your repo live under .pan/.
Get help
- Ask questions on the Overdeck Discord.
- Report bugs and request features in GitHub Issues.
- See the support page on overdeck.ai.