the agent office
Use cases / Product managers
AI for product managers: from idea to ticket to PR
Most AI for product managers stops at a nicer spec. In The Agent Office the spec keeps going: you pin an idea, a Planner reads the code and drafts the ticket, and a coding agent builds it in its own branch. Nothing ships until it is approved, and an engineer still reviews the PR.
Download the app Other use cases
the flow
-
1/5
Pin an idea
Click the corkboard on the office wall and add an idea in a sentence or two: the problem, who has it, anything you already know.
-
2/5
The Planner drafts the ticket
Click Shape with Planner. A Planner reads the code and writes the ticket in your team’s template, with a summary, scope and acceptance criteria. Reading changes nothing.
-
3/5
One click files it
Check the draft, pick the project and click Create ticket. It lands in Jira, Linear or GitHub Issues, marked as drafted with AI.
-
4/5
An agent builds it
Hire a worker for the new ticket. It writes a plan first, works in its own git worktree and branch, and asks before pushes, installs and deletes.
-
5/5
The PR is ready for review
The agent opens the PR. Mark it done and the PR and a summary go on the ticket, which moves to In Review for an engineer to check.
three good first tasks
Small, clear and easy for an engineer to review.
-
A copy change
Rename the Checkout button to Pay now, fix a typo on the pricing page or reword an error message. You know the words; the agent finds the file.
-
A small UI fix
Show a Saved! toast when a wishlist saves, stop a button wrapping on mobile or add an empty state. Describe what you see and what you want instead.
-
A prototype behind a flag
Try a gift wrap option with a few shoppers before the holidays. Ask for it behind a feature flag, so nobody sees it until the team turns it on.
what done looks like
When the work is finished, the PR is linked on the ticket with a summary of what changed, and the ticket moves to In Review. The office tells you, and the worker goes off to post the win.
what you need
- A Mac with Apple Silicon. The Agent Office is a Mac app. It runs on your machine and keeps everything in ~/.agent-office.
- git and access to the repo. The agent works in a copy of the code on your Mac, so it needs the repo the ticket is about.
- A coding agent you are signed in to. Claude Code, Codex, Copilot or Cursor. Each uses the sign-in it already has, so there is no API key to paste.
- An engineer to review the PR. The agent writes the code and opens the PR. A person who reads code still checks it and merges it.
You do not need to read code to pin ideas, file tickets or hire workers. You do need someone who reads code to review the PR.
other use cases
-
Engineers
Put a coding agent on every ticket, run them side by side and review PRs instead of writing every line.
See how engineers use it → -
Project managers
Tickets that get done, not just tracked: assign the backlog to agents and see every status on one board.
See how project managers use it →
open the office
For Apple Silicon Macs with a coding agent installed. Windows coming soon