the agent office
Coding agents for your issue tracker
Your tickets land on one office board. Each one gets its own coding agent, you approve the risky moves, and the PR and a summary go back to the ticket.
your tracker
-
LIVE
Linear
Open issues assigned to you, a Claude Code agent per issue, the PR posted back and the issue moved to In Review.
Set up Linear → -
LIVE
Jira
Pick your projects or write JQL, put a Claude Code agent on each ticket, and get the PR posted back with the ticket in review.
Set up Jira → -
LIVE
8090
Work orders on the board, a coding agent on each, with the PR and summary written back and the work order moved to Review.
Set up 8090 → -
LIVE
GitHub Issues
Open issues from the repos you can access, a Claude Code agent per issue, the PR posted back and the issue labeled in review.
Set up GitHub Issues →
what happens
- 1/4
Ticket on the board
Your assigned tickets from every connected tracker show up in one place.
- 2/4
An agent per ticket
Click a ticket and a worker takes it, in its own git worktree and branch.
- 3/4
You approve
Pushes, installs and deletes wait for your OK.
- 4/4
PR and summary posted back
Mark it done and the PR and a summary go on the ticket, which moves to In Review.
faq
Which issue trackers does it work with?
Linear, Jira, 8090 and GitHub Issues, all on one board. You can also type a task with no ticket at all.
Which coding agents run the tickets?
Claude Code by default. Codex, Copilot and Cursor work too, and each uses the sign-in it already has. The office never asks for an API key.
Can I connect more than one tracker?
Yes. Every connected tracker feeds the same board, and a source filter shows or hides each one.
Will an agent change my tickets without asking?
No. A ticket moves to In Progress when you start work, and the PR and summary are posted when you mark it done. Anything else an agent wants to do to a ticket waits for your OK.
open the office
For Apple Silicon Macs with a coding agent installed. Windows coming soon