One place for runs, reviews and hand-offs
See every run in flight, review what is ready and pick up what an agent could not finish. The workspace is where people and agents meet.
A board of work
Tickets move from intake to planning to building to review. Nothing is hidden inside a chat.
Review queue
Pull requests that are ready sit in one list, with the trace beside the diff.
Escalations
When an agent stops, it says why. The question, the options and the context arrive together.
Know what is running. Decide what ships.
The workspace shows the factory floor: what is in intake, what is building and what is waiting for you.
The board
Every ticket assigned to an agent has a card. Drag to reprioritise, click for the run.
Review with the trace
Read the plan, the diff and the test results side by side. Leave a comment and the agent picks it up.
Escalations that carry context
An agent that stops hands you the question, the options it considered and a link to the exact line.
Frequently asked questions
The questions engineering teams ask before the first run.
No. It mirrors the tickets you assign to agents and writes status back. Linear, Jira and GitHub issues stay the source of truth.
Every member can see the runs in every connected repository, except sessions their creator has made private.
Yes. The pull request carries the trace as a comment, and review comments there reach the agent the same way.