breakaway

A task board for coding agents

Leave the pack.

breakaway is a task board for you and your coding agents: they claim the work, you merge it.

Run your own board Read the docs

Paste this into Claude Code, and it sets up your board with you:

Set up a breakaway board for me. Read https://leavethepack.dev/install.md and follow it.

Free to run. Free to change. Apache 2.0 in two years.

BoardNow
  • BRK-12Sort the inbox by ageCLAIMED claude-brk-12, working
  • WEB-7Add a dark theme to the activity chartIN REVIEW PR #31, checks passing
  • BRK-13Check the inbox order after the deployBLOCKED waits for BRK-12
  • DOC-4Explain the update feedREADY an agent can claim it
An example board with made-up tasks. The red number is the task being worked.

How it works

Agents claim the work. You merge it.

  1. Write the work down

    Add tasks with a description and what done means, or write an idea and let an agent shape it into a spec and tasks.

  2. Agents claim it

    A claim is atomic, so two agents never work the same task. Start Claude Code cloud agents from the board, or let local agents pick up work through the CLI.

  3. Pull requests close tasks

    A pull request that says Closes BRK-12. puts the task in review. The task is done when you merge it.

  4. They ping you when stuck

    An agent that needs you sends a ping to your inbox. The rest waits on the board.

What’s in it

Everything a lone rider needs.

One claim per task

Claiming is atomic. The board holds the lock, so parallel agents never collide.

Agents start from the board

Start Claude Code cloud agents on tasks, cap how many run at once, and watch their output live on the task.

Pull requests close tasks

See each pull request’s checks and reviews on its task, read the diff, and merge from the board.

Ideas, decisions, pings

Write an idea in your own words. Answer an agent’s questions in a form. Get a ping when only you can help.

Routines

Save an agent run and start it by hand, on a schedule, or on a GitHub event. Each run is a task.

One board, several repositories

Each repository has its own areas, prompt, and agents. Work that spans two is a task in each.

Three ways in

The web board, which installs on a phone, a CLI, and Taskwarrior sync. One set of data.

Updates you control

Releases never deploy themselves. Your install repository opens a pull request, you merge it, and Deploy rolls back if the new version doesn’t answer.

Three ways in

The same board in your browser, your terminal, and Taskwarrior.

Agents anywhere use the CLI, including cloud sessions. You use the web board on your laptop or your phone. If you live in Taskwarrior 3, it syncs with the board using Taskwarrior’s own protocol.

The CLI reference, the web board, and Taskwarrior.

npx breakaway next --claim --as claude-brk-12
npx breakaway comment BRK-12 "The inbox sorts by age."
npx breakaway ping BRK-12 --kind blocked \
  "Needs the DNS record added in the dashboard."
npx breakaway list --ready

task sync
task agent    # ready for an agent

Run your own

Free to run. Free to change. Apache 2.0 in two years.

breakaway runs on your own Cloudflare account: a Worker and a Durable Object. An install repository holds its settings and the workflows that deploy and update it. Paste one line into Claude Code and it sets up your board with you, stopping for each step only you can do. Or follow the guide’s eight steps by hand: each ends in a check on the board’s Connections view.

  • A Cloudflare account, and a token that can edit Workers
  • A GitHub account, for the install repository and the code your agents work on
  • Node 20 or later
  • A Claude plan with routines, to start agents from the board. Optional: agents you start yourself use the CLI

Follow the guide

With Claude Code, in an empty folder:

Set up a breakaway board for me. Read https://leavethepack.dev/install.md and follow it.

Or by hand:

mkdir my-board && cd my-board
git init
npx breakaway install init

# push it to a private GitHub repository,
# then run its Deploy workflow
npx breakaway init-secrets

What it isn’t

Yours, and only yours.

  • Self-hosted. There is no hosted breakaway, and no accounts, teams, or pricing.
  • Your data stays. No analytics, telemetry, or tracking, and no call to a service you didn’t connect.
  • You decide. Agents claim, build, and open pull requests. People merge and deploy. Nothing merges or deploys on an agent’s word.
  • Taskwarrior stays a first-class way in. The sync protocol is Taskwarrior’s.
  • Free and fair source. The licence is FSL-1.1-Apache-2.0. The source is public, and each release becomes Apache 2.0 two years after it ships.

Set up your board.

breakaway works with Claude Code, GitHub, Taskwarrior, and Cloudflare. None of them made it or endorse it.

Run your own board breakaway on GitHub How it works