Backlog Task Board

What it does

A kanban board attached to every project where each card is a task an agent can run. Four columns by default: TODO, In Progress, Pending, Done (a fifth, In Review, is opt-in). Dropping a card into In Progress spawns a temporary agent with the ticket (title, prompt, private note, attached images, linked tickets, reporter conversation) as its first instruction; the card shows the agent's live status, and several cards can run in parallel, each in its own terminal. Tickets are synced to your account, so every machine and the phone see the same board.

Where to find it

• Inside a project: the Backlog item of the dock ("Project tickets and tasks").
• Command palette (Cmd K / Ctrl K) with the # prefix to jump to a ticket.
• Board header: New Task, Start next, the search field ("Search tasks or ID"), the Client feedback filter, Public backlog, Import tickets, All projects (the tickets of every project of your account in one board, see All Backlogs), and More actions with Clean up.
• The board name under the "Backlog" title is a menu ("Switch board: another project, or your idea box"): it lists your Idea box first, then the projects open in this session (Open), then Other projects, with a search field. Picking one switches to that project's board without closing the backlog.

How to use it

1. Click New Task. Fill Title (or click the sparkle to generate it from the prompt), Prompt, Type, Tags, Agent (Project Agents, Generic Agents or Teams), attach Images. Advanced options pins a Provider, Model, Reasoning, Account and Skills mode for this ticket only; Code in a separated worktree for this task isolates its branch, with a Worktree picker that offers the project's existing worktrees or a New branch (see Git Worktrees). A ticket set to run in its own worktree shows its branch name, behind a branch icon, in the footer of its card on the board (desktop and mobile); hover it on desktop for the full name.
2. Drag the card to In Progress, or click Start task on the card, or click Start next to launch the top card of TODO. The agent's terminal opens.
3. Watch the status on the card (Working, Idle, Needs input, Done). Click the card and Go to agent to read the terminal; Restart agent or Resume reopens a session.
4. Review the result and drag the card to Done (or use the Done button of the terminal). Move it to Pending if it must wait.

Clicking the agent avatar on a card opens a quick menu to reassign the ticket to another project agent in one click; past five agents the menu gets a Search agents… field (accent and typo tolerant), and No agents found when nothing matches.

Clicking the provider and model badge next to it (tooltip "Provider: <name>") opens the runtime menu: one submenu per provider with its models, and under the list the Account, Effort and Context rows. Set the rows, then click a model: provider, model, effort and account are saved on the ticket, the same fields as Advanced options in the editor, without touching the assigned agent's own configuration. The Account row opens on the account the ticket currently runs on (its own pin, else the executor's); pick another profile to pin it, pick the current one to leave the ticket on inherit. The row only appears for a provider with account profiles, and picking a model on another provider drops the pin, an account never crosses CLIs.

Priority is the order inside a column: drag a card up or down, top is launched first. Reorder column (arrow icon in the column header) sorts a whole column by date, author, assignee, type or client priority; it rewrites the priorities, so a 10 second Undo toast follows.

Linked tasks in the ticket detail connects tickets (relates to, blocks, blocked by, depends on, parent of, child of, duplicates). A ticket whose blocker is still open is parked in Pending with an On hold badge and returns to TODO by itself when the last blocker is done; Start next skips it. Include in agent context injects the linked tickets into the prompt (on by default).

Select several cards (Cmd/Ctrl click, the checkbox, or the column header checkbox) to Merge them (AI-combined title and description you edit before confirming; upvotes, comments, images, links and every reporter move to the surviving ticket), Move them to another board, Send to the Idea Radar, or Delete them. Merge with… is also in the card menu. Clean up analyses the board for duplicates and for open tickets already covered by a shipped one, one suggestion at a time.

Move to another board… in the card menu sends a ticket to another project's board or to the idea box. The ticket keeps its id, description, attachments and history and lands at the top of its column there; its links with other tickets, its assigned team and any machine-local agent or reviewer assignment are dropped. Not offered on tickets reported by users through the public backlog.

With the Review column enabled, a ticket can name a Reviewer: the agent that did the work cannot close it, it submits it to In Review and the reviewer approves or sends it back with feedback. A ticket sent back returns to In Progress with the agent that submitted it while that agent's console is still open (it is asked to fix and resubmit), and to TODO when that console was closed.

History (clock icon in the header of an existing ticket): every save that changes a ticket's title, description, type, tags, private note, agent or team, provider, model, effort, account, skills, reviewer or worktree settings keeps the previous state, including edits made by agents (backlog_update, appended sections). Moving it between columns or reordering it is not a version. The selected version is compared line by line with the form (title, description, then one line per setting), and Restore this version loads it into the form as unsaved edits: save to keep it.

Settings

• aiGenerateTitle, aiGenerateType, aiGenerateAgent, aiGenerateTags, aiGenerateModel (global, Settings > Backlog): which fields the AI magic button fills from the description.
• backlogTypeFilter (global, Settings > Backlog): shows one chip per ticket type above the board.
• backlogReviewColumn (global, Settings > Backlog; project override): adds the In Review lane and the reviewer field. Off by default.
• backlogMemorizeCloseOnDone (global, Settings > Backlog; project override): when a ticket reaches Done, its console is asked to memorize to Project memory, then closed. This also happens when the agent moves its own ticket to Done (backlog_update, backlog_review) or when it is closed from the phone, even if the board is not open; before 2026-09-24 such a console could stay open and idle. Off by default.
• backlogAutoCommitOnDone (global, Settings > Backlog > Commit automatically when work is done; project override): when a ticket reaches Done, or a team run is closed with Finish run, AgentsRoom commits the files its agents changed, and only those (other agents' work in the same folder is left alone). In a ticket worktree, everything the worktree holds is committed before the auto-merge. A cancelled run commits nothing, nothing is pushed. The commit message is the one the agent set (git_set_commit_message), else the ticket title with its type prefix and reporter credit. A toast says what was committed, and says it plainly when nothing was: the agent's CLI does not report which files it changed, the commit failed, or the project folder is not a git repository. Off by default.
• backlogTagMode (global, Settings > Backlog; project override): free text tags, or folders (only the project's root folders).
• Backlog Agent profile (Settings > Defaults, and Project settings > Default agents): the agent spawned for tickets that arrive without an assignee. Unset = the project's first developer-type agent.

Agent tools (MCP)

• backlog_list, backlog_get: read the board and one ticket (effective executor, linked tasks, blocked state).
• backlog_create, backlog_update: create or edit a ticket; descriptionAppend adds a section without overwriting other agents' sections; agentId or teamId assigns an executor. An explicit empty string for agentId leaves the ticket unassigned on purpose: the AI triage never picks an agent for it (omitting the field leaves the ticket to the project's triage).
• backlog_delete, backlog_comments and backlog_comment (read and answer the reporter thread of a public ticket), backlog_reorder (move and reorder in one call), backlog_start_next (starts a ticket assigned to a saved agent from any computer of the account).
• backlog_publish_mockup: attach a mockup to a public ticket and ask its reporter to validate it.
• backlog_link, backlog_unlink: dependencies between tickets.
• backlog_submit_for_review, backlog_review: the review gate.
• backlog_notify_done: park the reporter notification until the next release (see Public Remote Backlog).

Providers

All providers. A ticket can pin its own provider and model; the reasoning effort only applies to CLIs that expose one (Claude, Codex, Grok, Kimi, oh-my-pi and Antigravity among them), and an account profile pinned on one machine falls back to the executor's account on another. On Codex, fast mode is enabled automatically for backlog tasks.

Mobile

Present: the Backlog segment of the project screen shows the same board as tabs per status. Create and edit tickets (provider, model, reasoning effort and the Account chips under EXECUTION; the Default chip names the inherited account), assign a ticket to a team (the agent picker lists the project's teams under TEAMS; starting that ticket runs the team on the desktop and the phone switches to the project's agents view, where the run box shows), tap the provider and model badge of a card to open the same EXECUTION sheet on an existing ticket, start a task (the desktop must be running, the agent spawns there), Start next, sort a column, merge (long press to select), Clean up, prioritize or decline a client ticket, Move to another board… from the ticket detail (one ticket at a time). The Backlog tab of the bottom bar shows the tickets of every project at once, see All Backlogs. The idea box is reached from the lightbulb icon of the projects list; the board menu has no mobile equivalent, the Projects tab plays that role. Not on the phone: the Linked tasks section (parked tickets still show up in Pending), the Review column setting (the In Review tab appears only when a ticket is in it). The edit form has Version history too; it restores the fields the phone edits (title, description, type, tags, assignee, private note, provider, model, effort, account), the other settings are restored from the desktop.

Limits

• Requires being signed in: tickets live on your account, not in the repository.
• A merge takes 8 tickets at most; Clean up compares the 400 most recently updated tickets.
• descriptionAppend is capped at 6000 characters per call; the description itself at 200 000 bytes. Every append answers with descriptionBudget (bytes used, bytes left), plus a warning once fewer than 30 000 bytes remain, so a long pipeline sees the ceiling coming instead of discovering it on the append that carries the PR link. Bytes, not characters: an accent or a curly quote costs 2 to 3 of them.
• Editing a description by hand replaces it entirely, so a section an agent appended meanwhile is lost.
• A ticket assigned to a Team ignores the ticket-level model settings (each team agent runs on its own).
• The AI triage of incoming client tickets (best agent, sized model) needs the Pro plan; Free uses the deterministic developer default.

Common questions

• How do I keep a ticket unassigned (work only a human can do)? Save the ticket with no agent and no team after having had one, or create it over MCP with agentId: "": since 2026-09-28 the empty assignee is remembered as deliberate and the AI triage leaves the ticket alone (before, it wrote a role in within seconds and again in background batches). Assigning an agent or a team later works as usual. A ticket that simply ARRIVED without an assignee (client report, agent filing) keeps being routed automatically.
• Who is this reporter, and do they write to me often? A ticket that came from one of your users shows the reporter's name with a count of the reports that person has sent to this board (tickets and Radar signals); hover it for the email. Same chip on the phone.
• Why can't I assign a ticket to Bot? Since 2026-09-28 Bot, the conversational assistant, is no longer offered as an assignee or reviewer, and the AI triage never picks it. A ticket still assigned to Bot from before starts on the usual fallback agent.
• A card I dragged to In Progress jumped back to TODO. Fixed on 2026-09-28: a board refresh that started before the move no longer puts the card back in its old column, on the project board and the global backlog alike.
• Nothing happens when I drag a card to In Progress? The agent spawns in the project's room; check the Terminal tab and that a provider CLI is installed. The ticket keeps its status until you move it.
• Why did a ticket jump to Pending on its own? One of its linked tickets blocks it. Open the ticket: the Linked tasks section names the prerequisites, and it returns to TODO when they are done.
• Can an agent mark its own ticket done? Yes, unless the ticket has a reviewer: then only backlog_review by someone else closes it.
• The reviewer rejected a ticket: who fixes it? Since 2026-09-26, the agent that submitted it, when its console is still open: the ticket goes back to In Progress and that agent gets a message asking it to fix and resubmit, with the feedback on the ticket. If its console was closed, the ticket goes back to TODO and the board decides who picks it up. Since 2026-09-29 the same happens when the reviewer sends the ticket back with a plain status change (backlog_update to TODO or In Progress) instead of backlog_review: it counts as a rejection, the feedback it appends is the review note. Before 2026-09-26 a rejection always went to TODO and told the author it was no longer its ticket, and a second review round did not notify anyone.
• Where does a new ticket land? At the top of its column, on every device.
• Can two agents write the same ticket? Yes, with descriptionAppend: each adds a dated section and nothing is overwritten.
• My board showed tickets from another project for a moment. That happened when an agent of another project woke up (a team run, for instance) while this board was open; fixed in 1.175.0, a board now only shows its own tickets.
• How do I move a ticket to another project? Card menu, Move to another board…, pick the project. Reporter tickets cannot move.
• Can I choose the account a ticket runs on without opening it? Yes: click the provider and model badge on the card, set the Account row, then click a model. On the phone, tap the same badge. The pin is local to the machine that holds that account profile.
• My agent is called after a ticket key, can it start on it? Yes, with the project setting "Start on the ticket in the agent's name" (see Start on the ticket in the agent's name). It applies to the agent's name, not to backlog cards, which brief their agent themselves.
• My agent marked its ticket done but its console stayed open. Fixed on 2026-09-24: with memorize-and-close on Done turned on, the console now closes whoever moved the ticket to Done (the agent itself, another agent, the phone).
• The AI assigned my ticket to the QA agent because the description mentioned it. Fixed on 2026-09-25: an agent or role named in the story ("the QA node hit this bug") is no longer a reason to pick it; a QA or tester profile gets a ticket only when the deliverable is tests.
• A ticket created by an agent shows "Claude" next to a GPT model. Fixed on 2026-09-26: when an agent pins a provider that does not list the model it chose, the ticket now takes the provider that does (the model is the precise choice). A provider and model you pin yourself in the ticket form are never changed.
• Can I see the tickets of all my projects at once? Yes, All projects in the board header, or the Backlog tab on the phone. See All Backlogs.
• Can I give a ticket to a team from my phone? Yes since 2026-09-26: in the ticket's agent picker, pick a team under TEAMS. Starting it from the phone runs the whole team on the desktop (before, it ran only one agent). The list of teams comes from the desktop, which must be connected. Creating or editing a team stays on the desktop.
• Can AgentsRoom commit the work when I close a ticket? Yes, turn on Commit automatically when work is done in Settings > Backlog (or per project). It commits only the files that ticket's agents changed; with a CLI that does not report its files, nothing is committed outside a worktree and a toast sends you to the Changes tab. Commit + Close from Changes keeps your manual commit: files you excluded stay uncommitted.
• I turned auto-commit on and my team runs closed without committing anything. Since 2026-09-29 the toast says why, and the answer of team_finalize_run carries the same verdict, so an agent that closes a run is no longer left believing the work was committed. The reported case was a project opened on a folder that is not a git repository but groups several repositories: nothing at the root can be committed. Open each repository as its own project.
• An agent overwrote the description of my ticket. Can I get the old one back? Yes: open the ticket, click the clock icon (Version history), pick the version before the change, Restore this version, then save. The last 50 versions of each ticket are kept.

Related

• All Backlogs: every project's tickets in one board, desktop and phone.
• Public Remote Backlog: lets clients and users file the tickets that land on this board.
• Ticket Scoping: frame a feedback ticket into a mockup before building it.
• Import Tickets: bring GitHub Issues, JIRA or Notion items onto the board.
• Idea Radar: where demands you have not decided on wait instead of rotting in TODO.
• Idea Box: the project-less board for ideas you wrote yourself, and where Move to another board… sends them.
• Agent Teams: assign a ticket to a chained team instead of a single agent.
• Git Worktrees: run a ticket on its own branch.
• Start on the ticket in the agent's name: an agent named after a tracker ticket key (ARD-221) starts on it at its first launch.
• Multiple Accounts: the account profiles a ticket can be pinned to.
• Project Memory: what the memorize-on-done wrap-up writes to.
• Mobile Offline Mode: tickets captured or edited on the phone without network, sent later.