Decisions

  • Desktop app
  • All plans
View as Markdown

What it does

Agents record on the backlog board the questions that must be settled before the work can go on: which approach to take, which trade-off to accept, a fact only you have. Each decision is linked to its tickets and carries its options (with what each one implies), the option the agent recommends, and who decides: you, or another agent such as an architect. A ticket can wait on an open decision: it sits in Pending until the decision is answered, then goes back where it was. Answers are kept on the ticket, so they outlive the agent's session: the next agent to start the ticket reads what was already decided. A coordinator agent sees in one call what is open, who owns each decision and which tickets it holds.

Where to find it

  • Turn it on: Settings > Backlog > Decisions (all your projects), or Project settings > Backlog > Decisions (Inherit / On / Off for one project). Also a switch in the footer of the backlog board.
  • On a ticket: the Decisions section of the ticket, above the comments.
  • Waiting on you: the needs input pill of the title bar lists Decisions to take under the waiting agents.
  • On a board card: a signpost count of the ticket's open decisions.

How to use it

  1. Turn Decisions on, then restart the agents that should use it (they get the decision tools at their next launch).
  2. When an agent working on a ticket asks you a question with a card, each question is also recorded on the ticket. Answer on the card as usual: the answer is saved on the ticket too.
  3. An agent can also record a decision that can wait (for you, or for another agent), and make its ticket wait on it. You answer it from the ticket, from Decisions to take in the title bar, or from the phone: pick an option or write your answer, add why if it helps, then Decide. The agent that asked receives your answer as a message.
  4. Withdraw a question that no longer matters; Mark as applied an answered decision once the work that follows from it is built.

A decision whose agent card is still on screen shows Answer on the agent's card: answer it there so the agent carries on at once.

Settings

  • backlogDecisions (global, Settings > Backlog > Decisions): off by default. Synced with your account, so every computer gets the same choice.
  • backlogDecisions (project override, Project settings > Backlog > Decisions): Inherit, On or Off for this project. Turning it off never hides a decision that is still open: it stays on its ticket, answerable, so a ticket it holds is never stuck.

Agent tools (MCP)

Listed only where Decisions is on:

  • decisions_create: record a decision (question, options, recommended option, owner, tickets, blocks to make them wait).
  • decisions_list: what is open, who owns each decision and which tickets it blocks (filters: state, owner, ticket).
  • decisions_get: the full record of one decision.
  • decisions_answer: settle a decision the agent owns, or relay the user's own words (userQuote) for one the user owns. An agent never picks for you.
  • decisions_update: mark applied, withdraw, supersede, link or unlink tickets. backlog_get also shows a ticket's decisions, and ask_user questions can present an existing decision (decisionId).

Providers

All agent CLIs that have an MCP client (every CLI AgentsRoom runs except Aider).

Mobile

The ticket sheet of the mobile app shows the Decisions section (answer, withdraw, mark as applied) and the board cards show the open decisions count. The section appears once a ticket has decisions; the setting itself is changed on the desktop. While a decision waits on you, a signpost button with a count appears in the header of the Activity tab: it opens Decisions to take, the open decisions of all your projects, answerable right there.

Limits

  • Off by default; agents get the tools at their next launch.
  • Only the questions of an agent working on a backlog ticket are recorded from its cards: a casual question outside a ticket stays a plain card.
  • Decisions are created by agents (tools and cards), not from the ticket form.
  • The cross-project Decisions to take list covers your own boards, not team boards.

Common questions

  • Can a ticket wait for an answer instead of another ticket? Yes: with Decisions on, an agent can record a decision with blocks, and the ticket waits in Pending until it is answered, then goes back where it was.
  • Where do I see every question waiting on me? In the needs input pill of the title bar: agents waiting now, then Decisions to take. On the phone, the signpost button of the Activity tab opens the same list.
  • Is the answer to an agent's question card kept after the session? Yes when Decisions is on and the agent works on a ticket: the answer is saved on the ticket and read by the next agent that starts it.
  • Can an agent answer a decision for me? No. It answers only the decisions it owns; for yours it may only relay your own words.

Related