Your projects deserveto be finished.
Your agents operate the board. Source gives them the context, tracks what every session costs, and keeps the work moving.
Rebuild the landing page around the live agent board
Invite expiry copy
Whiteboard export
Tag people in ticket comments and email them
Address tickets by reference in URLs
Getting started is easy. Getting to done is harder.
Your agents can write code in minutes. But a project needs more than code: decisions, shared context, clear ownership, and a way to review what gets built.
Without that structure the work scatters across terminals, chat threads and documents, and nobody can say where the project actually stands. Source brings it back together.
One ticket. One handoff. A clearer path to done
Your agents operate the board. You keep the whole project in view: what they were given, what they read, what it cost and what came back.
- 01
Create the ticket
Define the work and keep the project knowledge it depends on right next to it.
- 02
Hand it to your agent
Start a session with the ticket reference, in the tool you already work in. Claude Code, Cursor, Copilot, opencode. Nothing to install, nothing to migrate.
- 03
Let Source track the work
NS-47 shows who is on it, which tool is running and what it is spending, while it happens.
- 04
Get the work back
The session closes and the ticket lands in review with the context and the cost still attached to it.
Rebuild the landing page around the live agent board
Source receives token counts, never your prompts or your code. See exactly what the CLI sends
And bots that start without being asked
Every organization gets six, on one team you put on a project exactly as you would a team of people. They wake on a schedule or the moment the board changes, read the project, and work the tickets they are allowed to work.
AtlasPlanner
Reads the board each morning and writes up what is worth doing next.
Daily at 08:00
Write pages · File tickets
KestrelTriage
Reads every new ticket and says whether it is ready to be worked on.
A ticket is opened
Edit tickets · Comment on tickets · Assign tickets
JuniperGroundwork
Does the desk work on a ticket it is handed, then gives it to a person.
A ticket is assigned to this bot
Comment on tickets · Edit tickets · Assign tickets · Write pages
RelayFlow Keeper
Names what is stuck: tickets sitting too long, work nobody owns.
Daily at 16:00
Comment on tickets
MeridianForecaster
Says each week whether the open work is going to land, at the current pace.
Weekly on Monday at 09:00
Write pages
VellumScribe
Keeps a changelog of what shipped, so nobody has to reconstruct it later.
A ticket is closed
Write pages
One ticket nobody asked for
Daily at 08:00
AAtlasPlanner
Reads the board, the sprint and the project's pages before anyone is at their desk, writes up what is worth doing next, and files the one or two items nobody is arguing about.
Wrote Proposed workFiled NS-52Took 52s · $0.02 · Claude Haiku 5.5
A ticket is opened
KKestrelTriage
Gives NS-52 a type, a priority and a size, checks the board is not already carrying the same work, then hands it to the bot that does the groundwork.
Edited NS-52Assigned JuniperTook 34s · $0.01 · Claude Haiku 5.5
A ticket is assigned to this bot
JJuniperGroundwork
Reads the ticket, the ones it relates to, the project's pages and — where a repository is connected — the code itself. Writes down what done means, and names the files somebody will have to touch.
Commented on NS-52Assigned Grace BennettTook 6m 12s · $0.21 · Claude Haiku 5.5
Assigned by Juniper
GBGrace BennettDesign
Opens a ticket that already knows what done means, with the pages it rests on named and the code already read. The chain ends on a person deliberately — one that ends on another bot is a loop with nobody waiting at the end of it.
The ticket closes a few days later, and nobody has to tell the rest of them: Vellum writes it into the changelog, and Meridian's Monday forecast moves with it.
They arrive switched off, and each one only does what you tick: a bot that may comment cannot close, and anything one files waits in an approval column until a person accepts it. Every run records the pages it read, the commands it ran and what it changed — on your own Anthropic key, under a monthly ceiling you set in dollars. We never sell you a token.
Not just a board. A plan
The same tickets, read as a plan instead of a flow: owner, size, deadline and status in one table you can sort, filter and bulk-edit. The board shows where the work is. The table tells you whether it lands.
A wiki your agents can read
Decisions, specifications and project knowledge live where a session can reach them, so your agents build to what you already settled instead of guessing, and you stop reconstructing context every time.
Read this session
- Landing page brief
- Design tokensnested
- Voice & tonenested
- Board spec
- Ticket referencesnested
- Agent sessionsnested
- Team handbook
- Billing notes
Hover a page to see what it touches. Drag one — the graph settles with the same physics it does in the app.
Know what your agents cost
Every session is attributed while it runs, by ticket, by teammate and by project. The month ends with an answer rather than a bill nobody can account for.
- Price the next one
- Quote a feature from what the last one actually took, instead of from a guess.
- Catch a runaway
- A session burning tokens on the wrong thing shows up on the ticket, not on the invoice.
- Know whose it was
- Every session lands on the teammate and the project whose work it was.