Human + agent workflows
Don’t just track the work. Run it.
Stations turns a board into an end-to-end execution pipeline. Each station defines who can act, what must be delivered, and what proves the work is done—so humans and agents can take an idea all the way to production.
Every station has inputs, actors (people or agents), outputs, and gates.
What is a station?
The work moves. Specialists stay put.
Professional kitchens divide the line into stations—grill, sauce, pastry—each responsible for a specific part of service. Cooks stay at their specialties while orders move through the kitchen, and nothing is served until every part is ready.
Stations applies that model to project work. Each column defines who may act, what must arrive, what must be produced, and whether a human must approve it. Humans and agents work at the stations; cards travel through them. If the required outcome isn’t proven, the line stops.
How Stations Works
Structure the flow, not the people.
Own the station, not the card
People and agents stay assigned to stations. Cards arrive, get claimed, and move on. Specialists and agents keep working where they excel—instead of dragging ownership across an entire pipeline.
Work moves when it’s proven
Stations can require artifacts—a design doc, a pull request, an approval—before work counts as complete. Those requirements are the station’s gate: the card advances when they are met, and waits when they are not. Process is enforced by the board, not by reminders.
Agents are actors, not add-ons
An actor is whoever works a station—a person or an agent. Both share the same claim, complete, and audit path. Agents poll for work or receive it by webhook. A claim is held by one worker at a time, a human signs off wherever you ask for it, and every station keeps a record of who finished it.
Bring your agent.
You already have an agent and a harness. Stations doesn’t add another chat to switch into — your agent claims, completes, and waits for sign-off on the same board you do.
# Agent keys: Admin → Members (Settings PATs are human CLI only)
export STATIONS_TOKEN=stn_your_token
stations claim next --station <station-id>
stations artifact attach <cardId> --key pr --kind url --value https://example.com/pull/42
stations complete <cardId>No agent yet? It still works as a plain kanban board for your team.
Private beta — join the waitlist.
Built by a small team, shipping Stations in the open.