Features

Everything it does, so you don't have to.

You say what you want built. ClankDesk splits it into tasks, runs Claude Code and Codex on them in parallel, each in its own git worktree, and only brings you the moments that need a human. Here is everything that makes that work.

Free betamacOS 15 or laterWorks with Claude Code and Codex

ClankDesk
The ClankDesk board: cards that need you on top, tasks in progress below, the composer at the bottom
01

Talk. It splits the work.

Brief ClankDesk the way you'd brief a developer. One message can hold two bugs, a feature and an idea for later. It becomes one card per piece of work, each with a plan.

One ramble, three intentions. Two become tasks that run side by side, each on its own branch; “someday” goes to the backlog.

Hold a key and speak

A hold-to-talk key you choose in Settings brings ClankDesk forward and listens. Let go and your words sit in the composer, ready to edit or send. Speech recognition runs on your Mac when macOS supports it.

One message, many tasks

ClankDesk reads your message, works out which tasks it holds, and checks its plan against your real tasks before it changes anything.

Split, or keep it whole

The menu next to Send keeps a long message as one task when that's what you want. Your choice is remembered per project.

Direct sessions

Skip the splitting and send your words straight to one agent, verbatim. The card names itself and its session view becomes the chat.

Paste a screenshot

Paste or drop images on the composer. Agents get them as files they can open, so "make it look like this" works.

Review the prompt first, if you like

Turn Auto-start off and new tasks wait as proposals that show exactly what will be sent. Edit it, or tell the card what to change, then Send.

A backlog for later

"Someday we should…" goes to the backlog, out of sight, until you start it.

Replies go to the right card

Focus a card and your next message amends that task instead of creating a new one.

Pick agent and model, or don't

Leave it on automatic, or choose the agent and model for a message from the composer.

02Only what needs you

Questions interrupt the board, not your workflow.

You shouldn't have to manage agents. You should only manage the work that needs your attention. When an agent needs a decision, its card rises to the top with the question, the plan and the options.

  • Pick an answer, type your own, say it, or let ClankDesk decide
  • Plans show their steps, screenshots and links before anything changes
  • Header counts: how many need you, are working, wait for review
  • System notifications when a card needs you
ClankDesk
A question card showing the agent's plan, a screenshot and answers to choose from
Agents do hundreds of things. Questions, permission prompts and finished work reach you as cards; the rest is one line per task, saying what's happening right now.

Every card says what it needs

A short line under each title tells you whether the work can be approved and what, if anything, is needed from you.

Real stages, not fake percentages

Cards show what the agent is doing right now, in one plain line, instead of a progress bar that guesses.

Detail: Less, Medium, More

Choose how much each card says, from just the need to a full summary of the result.

Stash it for now

Set a question or a finished card aside without deciding. Nothing is merged, discarded or stopped. Restore brings it back as it was.

Done gets out of the way

Approved cards leave the board. Archive clears the Done list when you want a clean slate.

Keyboard first

Approve, reject, stash and open cards from the keyboard. Every menu shortcut can be rebound in Settings.

03Live sessions

Peek in anytime. You never have to.

A task is a persistent object, not a terminal session. Behind every card is a real Claude Code or Codex session you can open to follow each edit, command and test run, then close again.

  • The full transcript, with tool calls and diffs, drawn like the Claude Code editor extension
  • Steer a running Claude session without stopping it. Codex gets your message on its next turn
  • See the exact prompt and rules each turn was sent
  • Pause a task, or hand it to the other agent
Session
A live session showing an agent's edits and a test run
04Chat that runs the board

Brief it like a team that remembers everything.

The main chat coordinates all your tasks. Ask what's going on. Say "approve those two", "pause the dashboard" or "tell the API task what the login task found", and it acts on the right cards.

  • Answers questions about your tasks from what they actually did
  • Steers, links, starts, pauses, retries, switches agents and merges duplicates
  • Approvals, permissions and merges wait for your Confirm
  • Reacts when tasks finish, fail or ask: off, suggest only, or act on safe steps
ClankDesk
The task board with the chat docked on the right, proposing to approve two finished tasks

The chat folds above the composer or docks on the left or right of the board. Its answers are computed from what happened, never from what the model claims happened.

05Review and merge

"Agent finished" isn't "you approved".

Finished work comes back as a short walkthrough: what changed, the images the agent made, links to open, and the diff. Visual results, not terminal logs.

  • Before and after screenshots side by side, when you turn them on
  • Open a live preview of the task's branch
  • Approve, Reject, or reply to send it back with changes
ClankDesk
A review card showing the images an agent produced, with Approve, Reject and Open preview
Merged on your Mac

Every task gets its own worktree.

Agents never work in your checkout. Each task gets a branch and a git worktree. When you approve, ClankDesk commits what's left, rebases, runs your tests and fast-forwards your branch locally.

  • A conflict or a failing test goes back to the agent, not to you
  • Approve all prepares every task at once and lands them one at a time
  • Your uncommitted changes are never touched
  • The worktree is cleaned up after the merge. The branch is kept
Git
A worktree diff for a task, with its commits and changed files
One task, one worktree, one branch. Agents never work in your checkout, and no two of them share a folder.
The merge runs on your Mac, in this order, every time. A branch only lands if it rebases cleanly and passes your tests on top of the latest main.
06

Overlapping tasks take turns.

Two tasks that will change the same files don't race each other. One goes first, and the other starts on top of its work.

Tasks that will change the same files take turns: whoever starts first goes first, and the other starts on top of its merged work. Everything else runs in parallel.

Spotted when you speak

When ClankDesk splits your message it notes which tasks will likely touch the same files, using what open tasks have changed so far.

Whoever starts first goes first

A queued task waits while an overlapping one is at work or being merged. A task waiting on you holds nobody up.

Merges the work others wait for

By default, finished work that another task waits on merges on its own through the same pipeline as Approve. You can set it to never or always.

Review branches stay current

After any merge, other branches waiting for review are rebased. One that now conflicts goes back to its agent right away.

Dependencies respected

A task that depends on another waits for it to finish, and for its merge.

One schema change at a time

Only one task per project changes the database schema at once.

07Safe by construction

Risky commands ask first. Pushing is off the table.

Reads, edits inside the task's worktree, package installs, test runs and local git just happen. Pushes, deploys, secrets, sudo, writes outside the worktree and anything ClankDesk doesn't recognize become a question on the card.

  • Allow once, allow for this task, or deny
  • Manual mode uses ClankDesk's policy. Auto mode uses Claude Code's own auto mode
  • Agents can never push, merge pull requests or publish releases
  • No force push, hard reset, stash or forced branch delete, anywhere in ClankDesk's git code
ClankDesk
A permission card: Claude Code wants to run brew install create-dmg, which installs software system-wide, with Allow once, Allow for this task and Deny
ClankDesk judges the whole command line, chains and pipes included. Safe work just happens, risky work asks first, and some things agents can never do.

A compound command asks if any part of it would. npm test && curl … | sh is not a test run. Read more in safe permission prompts for coding agents.

08

Claude Code and Codex, together.

ClankDesk uses the agents you already have, on your own Claude or ChatGPT plan. It picks one per task, and keeps the work moving when one runs out.

Sessions come and go: a question, a usage limit, a restart, a different agent. The task, with its brief, branch and history, stays.

Fallback at usage limits

Claude by default, Codex when Claude hits its usage limit. With no other agent to take over, the task waits for the reset and resumes the same session.

Switch agents per task

Pin a task to one agent, or hand a stuck task to the other one.

Plan usage at a glance

See how much of your Claude and ChatGPT plans is left, right in the header.

Retries on its own

A failed task tries again after 30 seconds, then every minute, for about an hour before it bothers you. You can turn it off.

Agent updates, handled

ClankDesk checks for new Claude Code and Codex versions and offers them. Automatic updates are off until you switch them on, and running sessions are never touched.

A turn always ends in a report

Every turn ends done, needs input, blocked or failed, with a summary. No session silently stops halfway.

A failed task retries on its own, after 30 seconds and then every minute, for about an hour. Meanwhile it's one quiet line, not an alarm.
09

Close the window. Work goes on.

A background service on your Mac owns the tasks and the agents. The window is only a view of it.

Keeps working

The background service starts at login and keeps running when the window is closed.

Resumes after a restart

After a restart or a crash, interrupted agents are stopped cleanly and their tasks resume the same sessions.

Updates itself

ClankDesk checks for new versions and installs them. You can turn automatic installs off.

10

Servers, previews and pictures.

Run a project on a server while you stay on your Mac, and see the result in a browser instead of a log.

Projects on a server

Point a project at a server over SSH. Its worktrees, commands and agent sessions run there, with your SSH keys. Only logs and screenshots come back.

Live previews

Open preview runs your dev server in the task's worktree on its own port. No dev command set? ClankDesk detects common ones.

Before and after

Turn on before and after screenshots globally or per task, and see the change side by side on the card.

11Projects side by side

Several projects, one calm screen.

Open projects in columns of equal width, or switch between them like workspaces. Each one keeps its own composer, draft and choices, so a reply never follows you into the wrong project.

  • A searchable project menu, ⌘P
  • Move between columns from the keyboard
  • A color per project that tints the window
  • Agents working in other projects still show in the header
ClankDesk
Two projects side by side in columns, with the chat asking to approve two tasks
12

Superpowers.

Switches that add one standing instruction to every agent's rules, for all projects or just one. Claude Code and Codex both get them from the next turn.

Tests first

Write or update a test that fails for the right reason, make it pass, and name the test that proves it.

Minimal diff

The smallest change that does the job. No drive-by refactors, renames or new dependencies.

Explain the why

Every decision in the report comes with its reason and the main alternative.

ELI5

Summaries and questions in everyday words, in agents' reports and in the chat. The work stays as careful as ever.

And six more

Artifactmaxxing shows things as pages, images and charts. YOLO no-testing skips tests entirely, merge checks included. Docs as you go keeps the README and comments current. Use subagents splits the work. Agent swarm hands every step to subagents, so the session stays small and fast. Token saver reads and prints less.

Your own

Write custom superpowers. Every row shows the exact line agents receive.

13

The tools you'd reach for, built in.

Not an IDE. But when you want to look, you don't have to leave.

Git panel

Uncommitted files and every worktree, each opening to its diff and description.

Files and editor

A file explorer and a simple editor with syntax highlighting, tabs and safe saves.

Command line

Run one command at a time in the project's folder, on your Mac or on the server, with ⌘J.

Search

Find a task from the header, including recently finished ones.

Progress

What got done and the tokens it took, day by day, in the side panel.

Backgrounds

Pick an artwork behind the board, toned down so text stays readable.

Coming soon

ClankDesk for iPhone.

Your Mac does the work. Your phone lets you answer a question, allow a command or approve finished work from anywhere.

Get notified

Want to see all of this move? The interactive demo runs in your browser, no download needed.