Tickets
Tickets are units of work. Each ticket describes something for the agent to implement.
Creating tickets
Click New Ticket in the tracker. A ticket has:
| Field | Description |
|---|---|
| Title | Short description of the work |
| Description | Detailed requirements in markdown. The agent reads this. |
| Kind | The type of work: Bug, Feature, Task, or Chore. Each kind has its own methodology prompt. |
| Priority | Urgency level: Urgent, High, Medium, or Low. Affects the agent's reasoning effort and approach. |
| Assignee | Who is responsible. Assign to the agent to indicate it should work on this. |
Ticket lifecycle
Tickets move through these statuses:
| Status | Meaning |
|---|---|
| Inbox | New, untriaged |
| Backlog | Accepted, not started |
| In Progress | Agent is actively working |
| In Review | Agent completed work, pending review |
| Done | Approved and merged |
| Cancelled | Closed without completing |
The agent automatically moves tickets from Backlog → In Progress when it starts and In Progress → In Review when it finishes.
Starting the agent
Open a ticket and click Start Agent. The agent:
- Creates a git worktree for the ticket's branch
- Reads the ticket description and project context
- Explores the codebase using its tools
- Implements changes, runs tests, and commits
- Moves the ticket to In Review
You can watch the agent work in real time. The activity feed shows every action: file reads, shell commands, thinking, and commits.
Interacting with the agent
While the agent is running, you can send it messages. Type in the comment box and send. The agent receives your message as additional context and can adjust its approach.
You can also stop the agent at any time with the Stop button.
Reviewing work
Unprotected mode (default)
When the agent finishes, the ticket moves to In Review. You can:
- Approve — Merges the worktree branch to your default branch and pushes to origin
- Discard — Deletes the worktree and branch
- Re-run agent — Send more instructions and start the agent again
Protected main mode
With protected_main enabled, the agent automatically creates a GitHub pull request when it finishes. Review happens on GitHub. See Protected Main Branch.
Ticket numbering
Tickets are numbered sequentially per project, starting at 1. The agent references tickets by number in commit messages (e.g. [#3] Fix authentication bug).
Filtering and search
The tracker supports filtering by status and searching by title or description. Use the status tabs to filter and the search bar for text queries.