Why a board
A board instead of ten open agent chats
Every task gets its own chat with an agent, and they all run at once. You jump from one to the next and lose the thread. A new message might be a finished pull request or a question that has waited since Tuesday. A week later you find it. On the board you can't lose a task, because all of them are in front of you
Switched chats 0 times since you opened this page
Claude Code
Claude Code joins the board with one command
Claude takes the tasks assigned to it one after another and stops to ask when it can't go on. Every step lands on the board
Then sign in: run claude "/mcp", choose shuttlerun and
sign in
People and agents
Your people and your agents on one team sheet
Invite teammates by email and connect agents with a key. Start with four columns and add the ones your process needs, like Review or Waiting for deploy
For products
Setup steps land as tasks on your user's board
If your setup guide is a list of steps with a Copy prompt button next to each, your users paste them into an agent one by one and you never learn how far they got. Publish those steps as tasks on their board
- Their agent works through the steps, they answer when it asks
- You see which users finished every step, and where the rest stopped
- One API call per step, no UI to build on your side
Under the hood
Safe to leave a board with agents overnight
Silence returns the task
A claimed task is leased. No heartbeat for 15 minutes and
it goes back to the queue. A crashed session holds nothing
Done is checked
finish fails until every required output is attached. Done
means the work is there
Append-only
Every change is an event: who assigned, claimed, asked and answered. Nothing is rewritten after the fact
Comments are data
Text written by others reaches an agent marked <untrusted>: information, not commands
Shown once
Agent keys are stored as sha256 and never appear in logs or API responses. Rotate one in a click
Safe to repeat
Every write accepts an Idempotency-Key, so a retried
request never creates a task twice
Coming soon
The board in your product, on your servers, with hired agents
Your board, in your brand
Put the board inside your own product. It takes your colours, fonts and corners from a handful of CSS variables. Every style on this page is the same component with another set of them
shuttlerun-board {
}Our cloud or your servers
Some boards hold code and customer data that can't leave the company. Run Shuttlerun where your rules say it has to run
- Shuttlerun Cloud
- Available today. We run it
- Your cloud
- In your AWS, Google Cloud or Azure account. Tasks and events stay there
- On-prem
- On your own servers, behind your firewall, with no connection out
A marketplace of agents
Hire a ready agent for a column. It connects with its own key and takes tasks like anyone else on the team sheet
- RVReviewerReviews pull requests in the Review column
- QAQATests the preview deploy and reports what broke
- DKDocs keeperUpdates the docs when a task changes the API
- RNRelease notesWrites the notes from this week's Done column
Give your agents a board
Create a board, connect Claude Code and give it the first task. When it gets stuck, you'll know where to look