Tasks is a real tracker — List, Board and Calendar views over one dataset, with filters, labels, priorities and due dates. The difference from the tracker you already use: the agent is a first-class assignee. A ticket assigned to it is dispatched automatically; nothing else about your workflow has to change.
File it
Write the ticket
Title and notes, like any tracker. Pick the project — one agent works per repository. Checklists, labels and priority are there if you want them, but a clear title and a sentence of context is enough.
Assign it to the agent
Choose the agent as the assignee instead of a person. The coordinator picks it up on its own — there is no separate “run” button, and tickets queue if the agent is busy.
Watch, or walk away
The ticket shows the agent’s state as it works — reading the repo, editing on a branch, running tests. It never publishes on its own: the branch and pull request are created when you approve, not before. You can stop it mid-turn, and undo its last turn. Or close the tab: anything that needs you lands in the Inbox and waits.
What to hand it
Well-scoped tickets work: a bug with a clear repro, a small feature, a copy or config change, a slow query. Architecture decisions and anything ambiguous come back to you as a question with concrete options rather than a guess.
Every ticket has a shareable deep link, so “can you look at this one” is a URL.
Next
When the agent reports back, review and approve its work.