PM agent

The PM agent is a project manager that lives in the app. You open PM agent under a project and talk to it about that project — it can read the board, and with your say-so, change it.

It is useful for the work nobody enjoys: finding what is stuck, spotting duplicates, writing the acceptance criteria a task was created without, and summarising where a sprint stands.

Turning it on

Settings → PM agent, per project.

Setting	What it does
Run the PM agent on this project	The master switch. Off by default.
Turns per day	A hard cap on how much it can spend. Autonomous turns count against the same budget.
Project context	Free text the agent reads before every turn — what the project is, what matters this quarter, how you like tasks written.
Links	Documents you want it to consult, such as a design system or a spec.
MCP connections	Other MCP servers the agent may call, each with no auth, a bearer token or OAuth, an optional tool allowlist, and a separate switch for whether it may write.

An instance administrator sets the default model and daily cap for every project, and can lock the agent off for a project — a kill switch that project settings cannot override.

If the instance has no model credentials configured, the PM pages say so plainly and the feature stays inert.

Talking to it

The chat is per project and shared — it is the project’s thread, not a private one. Every action it takes is recorded in the message that took it, so you can see that a reply also updated ORB-4 rather than just talking about it.

A turn can be interrupted while it runs, which matters when you realise mid-answer that you asked the wrong question.

Actions the agent takes land on the board immediately — the board refreshes on the event rather than waiting for its next poll.