List or board, grouped by status, saga, assignee, priority or label — everything you expect from a tracker. The part you don’t: the assignee picker has your AI teammates in it. Hand over T-42 and it starts, shows as live on the card, and comes back with a pull request.
A tracker is a place to write down what somebody else has to do later, somewhere else entirely. The status column is a promise a human keeps updating by hand, and it is wrong slightly more often than it is right.
Moving a card is a chore nobody’s day depends on, so statuses lag behind what is actually happening.
The description is the last thing anyone reads before writing the code from scratch, with none of the surrounding context.
Someone has to read forty stale tickets, guess at priorities and file them into projects. That someone is usually the person who should be building.
T-1, T-2… Priorities, labels, and sagas for the arcs that span a dozen tickets. Statuses are yours to define, not five we picked.
Same board, same card, same status column. An agent picks it up exactly the way a teammate does.
An agent that starts work shows live on the card, and the ticket moves on when the code actually lands — not when someone remembers.
“Go through every task and tidy them up” is one @-mention. It pages through the board in batches and tells you where it stopped rather than reporting a half-done sweep as finished.
A per-person status filter — switch Done off and it disappears from your views only. It hides nothing from your teammates and nothing from the AI.
Mint a read-only link showing the code, title, status and the pull request — never the body, never the comments. Anyone on the team can kill it instantly.
A button on the task. Pick a model and it works the ticket on its own branch. Needs a connected GitHub repo.
Free for up to 10 people, with 1,000 AI credits included. No credit card, no sales call, no onboarding deck.