Backlog Task Board

  • Desktop, mobile and web
  • All plans

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, Development (formerly In Progress), Pending, Done (a fifth, In Review, is opt-in), plus any custom columns you add with the Add column tile at the right end of the board (see Custom Backlog Columns). Dropping a card into Development 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. Large work is organized with epics, tasks and subtasks: see Backlog Epics, Tasks and Subtasks. A board with no ticket shows a pale Example card in the first column, once the template offer is closed: on desktop it passes once to Development, on the phone its column label changes. It cannot be clicked or moved, and it disappears with the first real ticket. A To do ticket can also start by itself later, at a moment and on a computer you choose: Scheduled tickets.

Video (1 min 23 s): Backlog Task Board, shown in the real app. A QA column is added after Development, a ticket dropped in Development starts its agent, which writes the code, and another ticket moved to QA just waits there: no agent starts. A second video (1 min 18 s) shows the Epics view of the board: see Backlog Epics, Tasks and Subtasks.

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. Every ticket has a short number per project (#42) on its card and in the board search; references printed by agents are clickable, see Ticket Numbers and Clickable References.
  • Under the project name, the Ideas and planning row shows the Backlog counter (tickets in Todo). An N new pill appears on it when tickets were created since you last opened the backlog; opening the backlog clears it.
  • Board header: New Task, Start next, the search field ("Search tasks or ID"; a ticket number works with or without #), 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. Since 2026-11-12 the video tutorial icon of the board header, right after the Board / Epics switch, opens a Video tutorials menu in both views: Create custom board columns, Group tasks into epics, Let your agent update the board, Share a public backlog, Scope a ticket with a mockup. Each opens its video on YouTube.
  • Open in its own window (picture-in-picture icon next to the close button of the backlog, main window only) moves the board to a separate window you can put on a second screen. That window follows the project selected in the main window, and opening it again brings it forward instead of creating a second one.
  • 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. The Prompt box of the ticket window follows its text, up to more than half of the window. In its toolbar, the expand icon opens the prompt nearly full window, with its library, dictation, sketch, improve and translate buttons: nothing to save, and Esc, the same icon or a click in the margin brings it back to the form. The eye icon shows the rendered text and the pencil the raw Markdown. A text containing a table or checkboxes opens on the raw Markdown, and its eye icon opens a read-only preview (headings, tables, checkboxes, images): the rich text editor would rewrite them, so it stays off for that text and you edit it with the pencil. The prompt library, skill and note editors have the same eye icon. With In my language on, the translated reading view of a ticket has the expand icon too.
  2. Drag the card to Development, or click Start on the card, or click Start next to launch the top card of TODO. While you hold a card over an empty Development column, the column reads Release to start the agent. When you drag it, the board stays open and the card shows the agent's live status; the agent's terminal is behind the board (close the board, top right, to read it).
  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. Open a ticket to read its Comments section: the team's own thread on that ticket, where you and the agents leave notes (progress, a hand-off, a blocker, a question). It is never shown to the reporter nor emailed. Since 2026-10-21 comments, and the reporter thread of a public ticket, are rendered in Markdown (headings, clickable links, images, tables, code), on the desktop and the phone. Since 2026-11-10 a comment keeps its line breaks, and command lines pasted without code fences show in a code box, on the desktop, the phone and the public ticket page. Type in the box and click Comment (Cmd/Ctrl Enter). The card shows the number of comments next to its attachments.
  5. 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.

As long as an agent is linked to a ticket, whatever column the ticket is in, its terminal pane shows Ticket, Backlog, Move ticket to… (arrow icon with a small chevron) and Done buttons. Move ticket to… opens the board's columns (TODO, Development, Pending and your custom columns, in board order) and moves the ticket there without opening the board. The column the ticket is already in stays in the list, greyed with a check mark and The ticket is already here: it cannot be clicked (since 2026-11-05; before, it was simply missing from the list). TODO puts the ticket back and deletes its agent (conversation discarded, changed files left as they are, nothing committed); the row asks for a second click (Click again to confirm) first. Any other column keeps the agent open and linked to the ticket, exactly like dragging the card on the board: a column that has a prompt runs it (and asks first when the column is set to ask). Done and In Review cannot be picked (they only show, greyed, while the ticket is in them): the Done button covers them, and it only goes away on a closed ticket or on a ticket waiting for its reviewer in In Review. The phone's agent console has the same button, which opens a sheet with the same columns (since 2026-10-27; before, the button only sent the ticket back to TODO). Ticket opens the ticket and carries two counters: the ticket's internal Comments, and, on a ticket reported by a user, the messages exchanged in the reporter Conversation (status changes and private mockups not counted).

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 type icon before the title of a card (bug, feature, chore...) opens a Type menu: pick another type and the ticket changes type at once, without opening the editor (since 2026-10-23, desktop; on the phone, change it in the ticket form).

The provider and model badge shows in every column (Pending, In Review and Done too since 2026-10-31, Resume relaunches on that model), but only when the board mixes runtimes: if no ticket pins a provider or a model, no card shows it. Clicking that badge (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. Once a ticket runs with settings different from its agent's, the badge shows them after the model: the context window (1M), the effort (brain icon and level) and a dot in the account's color, with a highlighted border; hovering the badge lists them ("Changed for this ticket: ..."). The phone card shows the same.

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 column of the board in one click (they land at the top of that column; a ticket already there stays where it is; towards Development each ticket starts its agent, like a drag; towards any other column it is a pure status change; the phone's selection bar has the same Move button) or to another board (tickets reported by users never leave their board: the menu says how many stay behind), set the same provider and model on all of them at once (Model: the ticket window's usual form for provider, model, context window, reasoning and account; only what you change is applied, the rest of each ticket stays as it was), 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.

Team backlog (Team plan, members of a live team only): the owner of the team turns it on for a project with the Team backlog button in the board head (shown only when at least one other member of the team has this project). It adds a second board for the project, shared by every member of the team, next to each member's own backlog. Members then switch between My backlog (private: nobody else ever sees it) and Team in the board head, desktop and phone. On the team board the ticket window has an In charge field: the teammate who owns the ticket, on top of the agent that runs it. That person receives a message in your private chat thread and a notification on their phone, once per assignment. Only the person in charge can start the ticket (drag, Start, Start next skip it for everybody else): its agent runs on their computer. Assigned to me filters the team board on your tickets. The owner turns the team board off with Turn off: the tickets are kept and come back when it is turned on again. A ticket moved from the team board to a private board loses its person in charge. The team board has no public backlog, Chrome extension, import or Clean up.

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. On such a ticket the green Done button of the agent's console reads Send to review (desktop and phone): it moves the ticket to In Review and notifies the reviewer instead of closing it, and the console stays open. When the reviewer approves, that console closes exactly as the Done button would have (since 2026-10-16; before, it stayed open and idle). A ticket sent back returns to Development 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. While a ticket waits in In Review, the reviewer agent shows which one it is on (since 2026-10-31): its row in the agents list carries a Reviewing 96 badge (the ticket number), whose tooltip names the agent that submitted it, and its console header reads Reviewing 96 from <agent>; a click opens the ticket. The same badge is on the phone. The review request and verdict messages also name the ticket by number and title, and the request says which agent submitted it.

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

  • backlogAutoClassify (global, Settings > Optimization > Adaptive Model > Backlog tickets > Automatic AI classification since 2026-10-29, formerly Settings > Backlog; project override; also the AI classification switch in the board footer): a ticket arriving in the backlog (description typed or dictated in the ticket window, ticket filed by an agent or a client) is classified by the AI on its own. Off: nothing is filled automatically, the AI button of the ticket window still works when you click it. On by default.
  • backlogClassifyPins (global, account-synced, Settings > Optimization > Backlog tickets > Always use these values; clicking the name AI classification in the board footer opens this section): provider, model (with its context window, e.g. 1M) and reasoning effort the classification writes on the ticket as they are instead of guessing them. A card left on Default keeps the usual behavior (the AI picks it when allowed by the fields above, otherwise the ticket inherits it from its agent). Picking a model or an effort pins its provider; changing the provider clears them. Never replaces a value chosen by hand on a ticket, never applies to a team ticket. Applied in the desktop ticket window, the phone's new ticket sheet and the automatic triage of incoming tickets. Default: nothing pinned. Project override (Project settings > Backlog > Always use these values): Inherit follows the account value (the row names it); Custom gives the project its own values, and a project left on Custom with every card on Default imposes nothing even when the account does. Switching to Custom starts from the inherited values.
  • aiGenerateTitle, aiGenerateType, aiGenerateAgent, aiGenerateTags (global, Settings > Optimization > Backlog tickets; project override). Models excluded in Adaptive Mode (Models it may choose) are never picked by the classification either. The first three times a ticket is classified, a mascot bubble above its fields says what was set and links to these settings: which fields the AI classification fills from the description.
  • aiGenerateModel (global, Settings > Backlog > Provider; project override): lets the AI size how the ticket runs on its provider. Its two children only show and apply while it is on: aiGenerateModelPick (Model) and aiGenerateEffort (Reasoning effort, providers that expose it). All on by default. A model or effort you picked by hand on the ticket is never replaced by the AI (since 2026-10-09).
  • Board footer (desktop): quick switches for AI classification, Review column and Auto-commit on done, plus Settings (opens the backlog settings). A switch changes the value where it comes from: the project's override if the project has one, otherwise the default for all projects (the tooltip says which).
  • backlogAutoTranslate (global, desktop; the In my language button in the board's toolbar and in the Idea Radar's toolbar, same setting for both; on the phone a switch in the board menu and above the Radar): tickets and ideas on screen are displayed translated into the interface language, in place: card titles, the ticket window (a reading view with the translated title and description, Original text opens the editor on the stored text, which is the only text ever saved), client replies, internal comments, idea cards, summaries, verbatims and theme names. Texts are translated when displayed, once per text and per language, and kept in a translation memory shared with every teammate and device, so a ticket nobody opens costs nothing and a title translated once is never translated again; a report written in your language shows the reporter's own words without any call. Translations run on your translate quota (Free: 20 batches a month, Pro: unlimited; once the limit is reached the texts already translated stay available) and need a signed-in account. Off by default, per device.
  • 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. An agent started for a ticket by another agent is wrapped up too when it was started with agents_spawn({ taskId }); one started without it is not linked to the ticket and must be closed by hand (fixed 2026-11-12: before, a coordinator had no way to link them). It works whatever the main window shows (another project, the Open space, the assistant), for an agent started from the ticket too (fixed 2026-11-13: before, only the project whose room was on screen was wrapped up). A ticket closed from the website or from another computer while its board is not open on this one is not seen: close that console by hand.
  • 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.
  • backlogCommentLead (project only, Settings > Backlog > project block, or Project settings > Backlog > Lead agent): the agent that receives an Agent Mail each time ANOTHER agent posts a comment on a ticket of this project, so it can triage it (answer on the ticket, reassign, reprioritize, or bring you in). A role (role:pm, follows whoever holds it, survives a machine change) or one saved agent. Default: Nobody. The lead is never mailed about its own comments, nor about comments you type yourself.
  • backlogTagMode (global, Settings > Backlog; project override): free text tags, or folders (only the project's root folders).
  • backlogCollapsedColumns (global, no UI switch: click a column header's fold arrow, or its rail to unfold it): the columns folded into a narrow rail. Kept when the Backlog is closed and reopened, the same on every board and synced to your account. Default: only Done folded. ticketPromptView (global, no UI switch: the eye or pencil icon of a ticket's Prompt, desktop and phone) works the same way: the last one clicked is the view the next ticket opens on, synced to your account. Unset by default; a new ticket stays writable.
  • Backlog Agent profile (backlogAgentProfile, Settings > Defaults, and project override backlogAgentOverride, 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). Status-only move (since 2026-11-11): backlog_update({ taskId, status: "in_progress", startExecutor: false }) puts the ticket in Development and starts nothing: no agent, no team run, no column prompt, on this computer or any other one of the account. The executor stays as it is, and a ticket locked for agents can be moved this way: it stays locked, so no agent can start it afterwards either. It is meant for a coordinator who handed the work to an agent already working on it (by message or assignment), so the board shows the real state without a second agent. Without startExecutor: false, a move to Development starts the ticket's executor as before, and a locked ticket is still refused. The answer says agentStart.reason: "status_only".
  • 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).
  • Team backlog: backlog_list({ board: "team" }) reads the team board (assignee: "me" keeps the tickets you are in charge of), backlog_create({ board: "team", assigneeUserId }) files on it, backlog_update({ assigneeUserId }) puts a teammate in charge ("me" for you, "" to clear; refused on a private board), backlog_start_next({ board: "team" }) skips the tickets a teammate is in charge of. backlog_get and backlog_list show assigneeUserId, and an agent started on a team ticket reads and updates it like any other. Since 2026-11-10 a short #42 finds a team ticket too (private board first, then the team board; board: "team" reverses the order), backlog_internal_comment and backlog_internal_comments work on team tickets, and backlog_create({ project, board: "team", assigneeUserId }) files on the team board of that other project with its teammate in charge.
  • backlog_internal_comment, backlog_internal_comments: write and read the internal Comments of any ticket (never published, never emailed). Writing mails the project's lead agent when one is set (notifyLead: false to skip). The latest 30 comments are also added to the starting prompt of an agent launched on the ticket.
  • backlog_publish_mockup: attach a mockup to a public ticket and ask its reporter to validate it.
  • backlog_link, backlog_unlink: dependencies between tickets; a second parent or a loop is refused. Epics, parentId, backlog_propose_breakdown, backlog_checklist: see Backlog Epics, Tasks and Subtasks.
  • Custom columns: backlog_list returns the board's columns; a col_... key is a valid status (see Custom Backlog Columns). backlog_columns_list, backlog_column_save and backlog_column_delete manage the columns themselves and every column's prompt. settings_get / settings_set, group backlog: every other backlog setting. Project scope adds teamBacklogEnabled (switch the team board), publicBacklog and publicBacklogUsers (see Public Remote Backlog), backlogAgentOverride and scopingAgentOverride; global scope adds backlogAgentProfile and scopingAgentProfile.
  • 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 (the segment reads Radar, Backlog, Agents since 2026-11-03, the order of the desktop dock) shows the same board as tabs per status; pull the board down to reload it in full (columns and team board included), and since 2026-11-03 coming back to it is instant and a card shows the same fields in the same order as on the desktop (source and reporter, then who works on it and on which model, then attachments and comments on the left and Start, or Resume to reopen the agent session, on the right) (since 2026-11-01 the Backlog square button next to a project card's assistant bar, in the Projects tab, opens it directly). 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, long press a card then drag it: a panel lists every column at the top of the board, and dropping the card on one moves the ticket to the top of that column (dropping it on the In Progress column starts the ticket, as on the desktop board; let go elsewhere and it goes back to its place), long press cards without moving to select them, then Model applies the same EXECUTION sheet to all of them, start a task with the Start button at the foot of each TODO card or from the ticket detail (the desktop must be running, the agent spawns there), close it with Done (or move it to another column with Move ticket to…, TODO deleting the agent) from the agent's console (the bar under the header names the ticket while the agent works on it; the desktop commits, merges and closes the agent exactly like its own Done button), 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. Custom columns show up as tabs (see Custom Backlog Columns). 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). Cards and the ticket detail show the ticket number (#42). The ticket detail shows the Comments section too (read and add a comment), and a card shows its comment count. The Lead agent setting is desktop only. The team backlog is there too: the My backlog / Team switch above the status tabs (the owner also turns it on or off there), Assigned to me, the In charge chips in the ticket form and the name on the card; starting a ticket a teammate is in charge of is refused with the same message as on the desktop. 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. In the ticket form, the expand icon next to Prompt opens the prompt on the whole sheet, with the same eye (read-only preview) and pencil (raw Markdown) icons as the desktop; Done brings it back to the form. The ticket detail shows the rendered prompt.

Limits

  • Requires being signed in: tickets live on your account, not in the repository. Signed out, the board simply shows empty, and any action on it (New Task, saving a ticket) opens the Sign in dialog over everything else (since 2026-10-23; before, it showed an error).
  • 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. Since 2026-10-15 a full description never refuses an agent's section: it is filed in the ticket's Comments, labelled Description full, filed here, and the rest of the update (a status change, a review verdict) still applies. Since 2026-10-16, on a ticket reported through the public backlog, an agent's appended section never enters the description, which the public page shows: it is filed in the Comments, labelled Public ticket, kept private here. 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.
  • A ticket starts once (since 2026-11-06): when two computers or agents start the same ticket, only the first start counts. The other reads "This ticket has already been started." and its board catches up; backlog_update and backlog_reorder tell the agent, which must not relaunch it. This covers every way of starting a ticket, phone included, not a colleague created by hand with agents_spawn for the same work.

Common questions

  • Can I read the backlog and the Radar in my own language? Yes: click In my language in the board's toolbar (or the Radar's): every ticket and idea on screen is shown translated into the interface language, titles, descriptions, replies, comments and verbatims included, and the ticket window gets a reading view with Original text one click away. Translation happens only when a text is on screen, once per text, and the result is shared with your teammates, so it does not consume your translate quota again for the same ticket. The phone has the same switch in the board menu and above the Radar.
  • Can new tickets always get the same provider, model or effort? Yes: Settings > Optimization > Backlog tickets > Always use these values (or click AI classification in the board footer). Pick a provider, then optionally a model, a context window and an effort; leave a card on Default to let the AI (or the ticket's agent) decide. A value you set by hand on a ticket always wins.
  • Can I assign a ticket to a colleague, not just to an agent? Yes, on the Team plan, on the project's team backlog: the team owner turns it on with Team backlog in the board head, then the ticket window has an In charge field next to the agent. The colleague gets a chat message and a phone notification, sees the ticket on the team board (Assigned to me), and is the only one who can start it, so the agent runs on their computer. Your own My backlog stays private: tickets there cannot be given to anyone.
  • Can I stop the project assistant (or any agent) from taking a ticket I am still thinking about, or that is too risky for now? Yes, since 2026-10-20: open the ticket and click the padlock next to the priority flag in the bottom bar (Lock for agents; on the phone, the Lock for agents button of the ticket sheet). The card then shows Locked. No agent starts a locked ticket: the project assistant and backlog_start_next skip it, Start next and a trigger's "start next" action pass over it, and an agent cannot move it to Development. You can still start it yourself (Start button, drag to Development). A coordinator agent may still mark it as being worked on with a status-only move (backlog_update with startExecutor: false): it lands in Development, nothing starts and it stays locked. The same move, on any ticket, is how a coordinator shows that work it handed to an agent already at work is underway, without a second agent starting. An agent can lock or unlock it only when you ask it to. The lock is stored on your account, so it holds on every computer and on the phone. Click the padlock again to unlock.
  • I folded some columns and they all came back unfolded when I reopened the Backlog. Since 2026-10-12 the folded columns are remembered, on your account, so the board reopens exactly as you left it (before, everything but Done unfolded again).
  • The AI keeps changing the model or the reasoning effort of my tickets. How do I stop it? Since 2026-10-09 a model or effort you pick by hand is never replaced. To stop the AI from choosing them at all, turn off Model or Reasoning effort under Provider in Settings > Backlog (or the whole Provider row). To stop the automatic classification entirely, turn off AI classification in the board footer or Automatic AI classification in the settings: the AI button still works when you click it. When Adaptive Model is on (Settings > Composer), the classification no longer chooses the model at all: Adaptive Model does, as a suggestion in the ticket's Model card (Suggest) or applied (Automatic), and a model set in Always use these values comes before both.
  • Why did a ticket sized by the AI run with a 200K context while my agent uses 1M? Since 2026-10-23, when the AI picks the model of a ticket, the ticket now keeps the context window it would have had without that pick, the one of its agent, or your Default context window setting when the agent's model has no choice. Before, every model picked by the AI landed on 200K. Tickets already sized keep their value: change it from the Context row of the card's model badge. Imported tickets (JIRA, GitHub, Linear, Notion) are not sized by the AI and always inherit their agent's model. A ticket still at 200K keeps the window of its agent. Since 2026-10-26 an agent whose model carries no chosen window follows your Default context window (Maximum unless you changed it); an agent explicitly set to 200K runs at 200K, launched from the board or from the sidebar. Switch the agent to 1M in its settings, or force the window for the whole project with Project settings > Backlog > Always use these values (pick the model with 1M).
  • What does "2 new" on the Backlog counter mean? Todo tickets created since you last opened this project's backlog, by you, an agent or an import. Opening the backlog clears it, and tickets created while it is open do not count. The last visit is stored on your account, so opening the backlog on another computer clears the pill here too. The phone does not show the pill.
  • 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 Development 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 Development? 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. And if a blocker is done but its blocked ticket stays in Pending? The ticket was already in Pending when the "blocked by" link was added, so the board treats it as parked by hand and leaves it where you put it (the On hold badge is missing on its card). Move it to TODO yourself. To have it wait and come back by itself, link it while it is in TODO: the board then parks it in Pending with the On hold badge. Since 2026-11-10 a ticket an agent files straight into Pending with its blocker in the same request (backlog_create with linkTo) is parked by the board and comes back on its own; an agent that links an existing Pending ticket is told it will not.
  • My ticket description filled up with agent updates and new ones were rejected. What now? Since 2026-10-15 nothing is rejected any more: the ticket keeps its description as the spec, and its Comments section is the activity log. Agent Mail checkpoints go straight to the Comments (labelled Agent Mail checkpoint), agents are told to post progress notes there with backlog_internal_comment, and once a description reaches its 200 000-byte limit, every further section an agent appends is filed in the Comments (labelled Description full, filed here) instead of being refused. The latest 30 comments are given to the next agent started on the ticket, on desktop and from the phone.
  • Can agents leave comments on a ticket, and can a lead agent be told? Yes. Every ticket has a Comments section (desktop and phone) where you and the agents write internal notes; agents use backlog_internal_comment. Set a Lead agent in the project's Backlog settings (for example the PM role): each comment another agent posts is delivered to it through Agent Mail, so it can react. Comments are never sent to the person who reported the ticket; to answer them, use the reporter conversation instead.
  • 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 console's Done button closed my ticket although it has a reviewer. Fixed on 2026-10-15: when a ticket names a reviewer, that button now reads Send to review and moves the ticket to In Review, notifying the reviewer; only the reviewer closes it. Dragging the card to Done yourself still 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 Development 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 Development) 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 an agent's notes show up on the public page of a user's ticket? No, since 2026-10-16: on a ticket reported through the public backlog, every section an agent appends goes to the private Comments (labelled Public ticket, kept private here), never into the public description.
  • Can two agents write the same ticket? Yes, with descriptionAppend: each adds a dated section and nothing is overwritten.
  • My board is empty (or shows another project's tickets for a moment) although I have tickets on this folder. Two fixes. A board briefly showing another project's tickets when one of its agents woke up was fixed in 1.175.0. And since 2026-10-29, when the same folder ended up with two project entries of the same name, the tickets left on the dead entry (numbers, columns, people in charge, links and the public page included) are moved to the entry you actually open, at startup, without asking. Team boards are never moved, and a ticket whose number or imported key already exists on the destination is renumbered or left where it is.
  • 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 open the backlog in a separate window, next to my agents? Yes since 2026-10-09: open the backlog and click Open in its own window (picture-in-picture icon, next to the close button). The board moves to its own window, which you can keep on a second screen while you work with the agents in the main window. It shows the project selected in the main window and follows it when you switch project. Starting a ticket there launches its agent in the main window, the card shows the agent's live status, and Go to agent brings the main window forward on that agent's console. Closing the window brings nothing back automatically: reopen the backlog from the dock. The window is reopened at the next launch when the app restores your session. Desktop only; for every project at once, use All projects (it has its own window button too).
  • 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 start a ticket from the list on my phone? Yes since 2026-10-09: in a project's backlog, every card of the TODO tab has a Start button at its bottom right, like the desktop card. It starts the ticket on the computer that has the project (its assigned agent, or its team), then opens the agent's console. When that computer is not connected, the button shows a crossed screen and a tap says why. Screen reader users find it in the card's actions. The Backlog tab of the bottom bar (every project at once) does not start tickets: open the ticket in its project.
  • I started a ticket too early. Can I put it back in TODO and get rid of its agent? Yes since 2026-10-22: in the agent's terminal pane, click the arrow button Move ticket to… next to Done, pick TODO, then click it again to confirm. The ticket goes back to TODO and the agent is deleted; the files it changed stay as they are. Same button in the phone's agent console. Since 2026-10-27 the same menu also lists Pending and your custom columns: those keep the agent open, and a column with a prompt runs it, like a drag on the board. If Pending seems missing on an older version, the ticket is already in it: since 2026-11-05 the current column stays listed, greyed, with The ticket is already here. Dragging a card out of Development on the board also keeps its agent open, and since 2026-11-04 the agent's buttons stay there in every column (before, they disappeared as soon as the ticket left Development): Done only goes away once the ticket is closed or waits for its reviewer.
  • Can I mark a ticket done and close its agent from my phone? Yes since 2026-10-08: open the agent's console; while it works on an in-progress ticket, a bar under the header shows the ticket with a Done button. It does what the desktop Done button does (auto-commit and worktree merge when turned on, ticket to Done, agent closed), on the computer that runs the agent, which must be connected. The "notify the reporter" sheet then opens on the phone.
  • Why did the AI type my visual bug as Style, not Bug? Since 2026-10-07 the AI that fills a ticket classes visual defects (overflow, alignment, overlapping text, responsive layout) as Style, even when described as a bug; a broken behaviour or lost data stays Bug. The titles it generates are also shorter (4 words at most). Change the Type by hand if you disagree.
  • 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.
  • The prompt box of a ticket is too small, and its eye icon is greyed out or only a preview. Why? Since 2026-11-04 the expand icon in its toolbar opens the prompt nearly full window (Esc brings it back; on the phone the icon is next to Prompt in the ticket form). A text with a table or checkboxes stays out of the rich text editor, which would rewrite it without them: its eye icon shows a read-only preview, and you edit it with the pencil (raw Markdown). Since 2026-11-05 the next ticket opens on the view you last clicked, so you no longer click the eye on each ticket.
  • 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. Backlog Server Tokens: a script on a server files cards with every desktop off.
  • 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.
  • Decisions: a ticket can also wait on an open decision, recorded on the board with its options and owner.
  • 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.