Task management

Your backlog,
their execution

You have ten features in your head. Write them down as tasks, drag one to Development, and a Claude agent starts coding it. Your brain stays clear. Your agents stay busy.

Screenshots

Real captures of the app, added as this feature evolves.

  • A project's backlog board showing its tickets in its own columns
    The project's board always shows the same tickets your agents see.
  • Ticket window of an AgentsRoom agent with the Move ticket to menu listing the board columns
    File a ticket in the right column straight from the ticket window, without going back to the board.
  • Backlog board with its columns and cards shown right after reopening
    A large backlog shows its columns and cards at once when you reopen it.
  • Backlog card filed directly in the development column with its frontend agent
    A ticket an agent files straight into In progress starts its agent, like a ticket moved there.
  • Backlog column menu where Delete column is greyed out with the reason
    Default backlog columns explain that they can be renamed but not deleted.
  • Backlog TODO column header with the add task button on the right
    Add a ticket from the button at the right of the TODO column.
  • Backlog board with an epic card showing an eye icon next to its progress
    Each epic and parent task has an eye to hide or show its tickets on the board.
  • Backlog board where an epic's tasks are hidden and its card shows Hidden
    Collapse the parents you are not working on and read the board at a glance.
  • Backlog card showing the agent another agent started for it
    Agents started by a coordinator stay linked to their ticket.
  • Edit column dialog with the Offer as next step switch
    Choose which backlog columns an agent's console offers as the ticket's next step.
  • Agent console with a green Test button next to the Done icon
    The agent console moves the ticket to the next column of your board, custom columns included.
  • Backlog board with an agent-filed ticket waiting in Pending, blocked by another ticket
    A ticket an agent files as blocked waits in Pending and returns to TODO by itself when its blocker is done.
  • Backlog board scrolled down with the column titles pinned at the top
    Column titles stay visible while you scroll a long board.
  • Column prompt window of the Pending column with the Do nothing option selected
    Set a column to Do nothing so moving a ticket there never starts an agent.
1 / 14

Here, Development is the only column that starts an agent: no other column has a prompt. A QA column is added right after it. A ticket dropped into Development starts an AI coding agent that writes the function the ticket asks for; another ticket dragged into QA simply waits there, and no agent starts.

Watch on YouTube

NEWRemote public backlog

Now your clients can feed the backlog

Open the same task board to your clients, designers and end users. They report bugs, request features and upvote tickets on a public feedback portal, through an embeddable widget pinned on your production site, or via the Chrome extension that captures any page with a screenshot, the exact CSS selector, the URL and the full DOM context. It's also the shortest path to pull Figma mockups, design references and visual specs straight into a ticket: drop the frame, add a two-line brief, and your agent gets the pixel-perfect context it needs. Non-technical users open a ticket in three clicks, without ever leaving the browser, and you track it all side by side with your own tasks. Every ticket lands directly in your backlog: drag it to Development and an agent running Claude, Codex, GitHub Copilot CLI, Cursor or any of the 20 other agent CLIs AgentsRoom supports ships it. A client-driven backlog, with zero triage tax, no parallel Jira board, no lost email.

Discover the Remote Backlog

A kanban board built for AI agents

Not another project manager. A task board where dragging a card to Development literally starts a Claude agent on that task.

Drag to run

Move a task card from TODO to Development. AgentsRoom spawns a Claude agent with the task title as prompt. No buttons, no menus. Just drag.

Four columns, plus your own

TODO for ideas, Development (formerly In Progress) for active agents, Pending for blocked tasks, Done for completed work. Need another stage, like QA or To validate? Add your own columns, each with its own name, color and icon, and give any column its own prompt (analyse, plan, review...): a ticket dropped there goes to the running agent or to a new one. Each column shows a live count of tasks.

Assign agent roles

Assign a specific agent role to each task. Your Security Engineer handles the auth fix, your Frontend Developer builds the new component. Right agent, right task.

Live agent status on cards

Each task card in Development shows the linked agent's status in real time: working, waiting for input, done or idle. You see progress without opening the terminal.

Attach images to tasks

Add screenshots, mockups, or design references directly to task cards. Your agents receive the visual context they need to deliver accurate results.

Parallel task execution

Drag multiple tasks to Development at once. Each one spawns its own agent. Five features in parallel, each with its own terminal, its own status, its own review.

Stored in your repo

Tasks are synced to the cloud and linked to your project. Team members see the same backlog. Progress persists across sessions and machines.

Offload your brain

Stop juggling features in your head. Write them down, prioritize visually, and let agents handle execution. You focus on what matters: reviewing and shipping.

AgentsRoom backlog board showing kanban columns TODO, Development, Pending, and Done with AI agent tasks running in parallel

Four columns, unlimited tasks. Drag to execute, track visually.

How it works

01

Create your tasks

Click + New Task. Give it a title, an optional description, tags, and assign an agent role. Add screenshots or mockups if needed. Your task appears in the TODO column.

02

Drag to Development

Grab a task card and drop it into the Development column. AgentsRoom immediately spawns a temporary Claude agent with the task title as its prompt. The agent terminal opens automatically.

03

Watch agents work

Each task card shows a live status indicator linked to its agent. Yellow pulsing means thinking, green means done. Click the card to jump to the agent's terminal and see the full output.

04

Review and move to Done

When an agent finishes, review its changes in the diff viewer. Satisfied? Drag the task to Done. Need changes? Leave it in Development and give new instructions to the agent.

05

Repeat at scale

Add ten tasks for your sprint. Drag three to Development in parallel. While agents code, add more tasks you just thought of. Your backlog grows, your agents deliver, your brain stays clear.

Board templates

Set up the whole board in one click

The first time you open a project's board, AgentsRoom offers a template. One click lays down the columns, and each column comes with its prompt, its agent and a model suited to its job, picked for your own provider. You see what every column will do before you apply, and you can change any of it.

For developers

Classic

TODO · Development · Pending · Done

The essentials: the agent implements the ticket, then sums up what is left to check.

With spec

TODO · Spec · Development · Pending · Done

An architect writes the specification on the ticket with a strong model, without coding. Then a developer implements it and checks every acceptance criterion.

Quality

TODO · Spec · Development · Test · Pending · Done

Spec, development, then a QA agent tests the change against the acceptance criteria before the ticket waits for you.

In Non-dev mode

Everyday requests

TODO · Being handled · Pending · Done

A Personal Assistant handles each request from start to finish, then tells you what to check or decide.

Research and writing

TODO · Research · Being handled · Proofreading · Pending · Done

A Researcher gathers facts and sources, a Writer writes, then a proofreading pass checks spelling, tone and facts.

Your board already has custom columns? The template lists the ones it will remove before you apply. Their tickets go back to TODO, none is deleted, and a column with the same name as one of the template is kept with its tickets.

One ticket, from start to finish

The prompts of the templates keep a single ticket: a spec, a test report or a progress note goes on the ticket itself, in its description or an internal comment, never into sub-tickets unless the ticket asks for them.

A model per column, on your provider

A template stores a level of power, not a model name. On your account it takes the model of that level from your default provider, Claude Code, Codex or another CLI, plus the reasoning effort when that model accepts one. The review screen shows it column by column before anything is applied.

Undo, or restore a prompt

Changed your mind? Undo puts the board back exactly as it was: columns, prompts and the tickets inside them. In a column prompt you edited, Restore the proposed prompt brings back the template's text.

Your own templates

Save this board as a template, for yourself on all your projects and devices, or for the members of this board, team members included. It then appears under Saved templates, next to the built-in ones.

Offered once per project

The template panel opens by itself the first time you open a project's board, once per project, even from another computer. Until then, the Backlog tile of a new project shows a Recommended badge. Later, the template tile above Add column brings the templates back.

Columns in your language, a review gate on demand

The built-in columns are named in the language of the app, and In Progress is now called Development (Being handled in Non-dev mode). Need an approval before Done? New column offers to turn on the In Review column: Done stays locked until a reviewer approves the ticket.

Did you know?

Your users can fill this backlog for you.

Once the board is ready, a short "Did you know?" animation shows one more idea: with a public backlog, your clients and users send their ideas and bugs, the tickets land on your board, an agent does the work, and everyone who asked is told when it ships. You no longer even need to write the prompts: your clients or users do it for you.

Column prompts

One prompt per column, a pipeline for your agents

Give every column of the backlog its own job. Write a prompt on a column, built-in or one you added, and each ticket dropped there goes to an agent with that instruction: clarify it, plan it, code it, review it, test it. Moving a card becomes a step of your workflow.

01

Need clarification

Column prompt

Analyse this ticket without coding it, then explain what is unclear.

The agent reads the ticket and the code, then comes back with the questions to settle instead of guessing. Nothing is written to the repository.

02

Plan

Column prompt

Write the implementation plan for this ticket: files to touch, steps, risks. No code yet.

The plan is ready before the work starts. Drag the ticket on to Development, keep the same agent, and it codes with the plan already in its context.

03

In Review

Column prompt

Review the changes made for this ticket and list what must be fixed before merging.

Pin a reviewer agent on the column and it checks every ticket that arrives, even when another agent wrote the code.

04

QA

Column prompt

Run the tests, check the change in the browser and report what fails.

A column you add yourself after In Review, with a QA agent that tests the work before the ticket goes to Done.

Need a mockup to validate with the person who asked, rather than a written analysis? That is Ticket Scoping.

When a ticket is dropped in the column

Open the menu of a column header (Column options), then Column prompt. Write the prompt and pick what happens on each drop. A column that has a prompt shows a Column prompt badge in its header.

  • Ask meDefaultEach drop asks whether to keep the running agent, start a new one or just move the ticket.
  • Keep the running agentThe agent already working on the ticket receives the prompt and keeps its context. If none is running, a new one starts.
  • Start a new agentA fresh agent runs the prompt. The previous one finishes its current turn, then closes.
  • Do nothingThe ticket just changes column: no agent starts and none receives the prompt. The prompt stays saved, ready to switch back on.

A column can also pick its own agent, a project agent or a role. With Use this agent even if the ticket has one, on by default, the column's agent takes over; turned off, it only picks up the tickets that have no agent.

Agents move tickets too

When an agent moves a ticket over MCP, the column prompt runs as well, in the background, without stealing your focus. An Ask me column then keeps the running agent, or starts one if none is running.

No endless loops

Moves made by agents start at most 10 column prompts per ticket in 24 hours, so two agents cannot bounce a ticket forever. Change it in Settings > Backlog > Automatic column prompts per ticket, for every project or for one; 0 means unlimited. Your own moves are never limited.

Phone, every CLI, every computer

Move a ticket from the mobile app and the same choice appears in a bottom sheet, then your desktop runs it; prompts are written on the desktop. It works with Claude Code, Codex and the other agent CLIs, on macOS, Windows and Linux, and the prompts are stored on your account, so all your computers share them.

Epics

Epics, tasks and subtasks, on the links you already have

Large work stops being a pile of loose cards. An epic holds its tasks, a task holds its subtasks, and the board shows how far each one is, what blocks it and what an agent should do next.

An Epics view, column by column

Switch the board to Epics: every epic with its progress and what comes next, and its tickets in the columns where they stand. A click on its name opens it.

Subtasks fold into 3/5

A subtask folds under its task while they share a column, and shows as its own card as soon as an agent takes it.

Blocked by #12, on the card

Set a dependency from the card's menu. A loop is refused, and a blocked ticket waits in Pending until its blocker closes.

Agents pick the right ticket

Start next skips epics, parents and blocked tickets. An agent receives the epic's goal and how far its siblings are.

Start epic, with a limit

Launch the ready tickets of an epic in dependency order, up to the limit you set, each in its own worktree if you want.

One epic tonight, then stop

Run an epic to its end, now or at a set time. Tickets start as others close, its tests and security checks come last, and nothing else starts.

Epics in order, with a pause

One epic can wait for another: its tickets stay put until the first is closed. Pause holds an epic the same way, and agents at work finish their ticket.

Why not a regular task manager?

Tasks that execute themselves

In Jira, Linear, or Notion, tasks are static cards. You read the task, then switch to your IDE, then start coding. In AgentsRoom, dragging a task to Development spawns an agent that starts coding immediately. The board is not just for tracking: it is the trigger.

Ticket import

Your tickets from GitHub Issues, GitLab Issues, JIRA Cloud, Notion, Linear, Azure DevOps, YouTrack and Odoo

Part of the work already lives in another tool. Pick a source, connect it, choose what to bring in, preview, import. Then replay the same import whenever you want.

Eight sources, one board

GitHub Issues with a repository, a state and labels. JIRA Cloud with a project or a JQL query. Notion with a database shared with the integration. Linear with one or several workspaces, each with its own API key, filtered on what is assigned to you, by team, project and status. Azure DevOps with a project or a WIQL query and a personal access token. GitLab Issues with a project, a state and labels, on gitlab.com or your own instance. YouTrack with a project or any YouTrack search, on YouTrack Cloud or your own instance. Odoo with a CSV file of tasks exported from Odoo Project, no connection and no password. You preview the result before anything lands on the board, and a search field finds the one issue you already know the key of. Only need that one? Paste its reference straight into the TODO column and it comes in on its own.

Replay the import, no duplicates

Running the same import again updates the tickets already imported instead of creating copies. Title, description, type, labels and the screenshots attached to the issue are rewritten from the source on every pass, so the two boards stop drifting apart.

Your own work is never overwritten

The assigned agent, the internal notes, the order on the board and the links between tickets survive every refresh. A ticket already in progress or done here never drops back to TODO, and an issue that leaves the query keeps its ticket.

Read only by default, two-way sync as an option

By default the import only reads: nothing is pushed back to GitHub, GitLab, JIRA, Notion, Linear, Azure DevOps or YouTrack. Turn on the two-way sync for a project and column moves, title, description, comments, new tickets and the pull request link go back to the tool, while a change made there moves the ticket without ever starting an agent.

The import token stays on your machine

Your import token is encrypted locally and never reaches our servers. Only the query is saved on your account, so the refresh follows the project from one machine to the next. The optional two-way sync uses a separate write token, kept encrypted on our servers so it runs with your computer off.

Every ticket says where it comes from

An imported ticket shows its source, links back to the original issue one click away, and can be brought back in step on its own without replaying the whole query. Setup happens on the desktop; from the phone you can refresh the whole import or bring in a single ticket, and both run on your computer.

Idea box

A board for ideas that have no project yet

Some ideas are not ready for a repository. Drop them in the idea box, a kanban attached to your account rather than to a project, and move each ticket to the right board the day it becomes real work.

Tickets without a project

The idea box is a regular backlog board with one difference: it belongs to you, not to a repository. Write the idea down as a ticket, with a description, tags and screenshots, and stop carrying it in your head. It is synced on your account like every other board, and the mobile app opens it from the lightbulb icon in the projects list.

Move a ticket to another board

From the card menu, or with several tickets selected, choose Move to another board and pick a project. The ticket travels as is, with its description, its attachments and its history, and lands at the top of its column. It also works between two projects, for the ticket that was filed on the wrong board.

Starting an idea means moving it

The idea box never starts an agent: there is no project to run it in. Drag an idea to Development, or press Start, and AgentsRoom asks which project to move it to. The board follows the ticket, and the agent starts there, on real code.

Change board without closing it

The project name at the top of the board is a menu: the idea box first, then the projects open in this session, then the others. Pick one and the board switches to it, without closing the window and clicking through the sidebar.

How does dragging a task to Development start an agent?
When you drop a task into the Development column, AgentsRoom creates a temporary agent with the task title as its initial prompt. If you assigned a specific agent role to the task, that role's system prompt is used. The agent's terminal opens automatically so you can watch it work.
Can I run multiple tasks in parallel?
Yes. Drag as many tasks as you want to Development. Each one spawns its own agent with its own terminal. You can run five, ten, or twenty tasks at the same time, limited only by your machine and your provider's rate limits.
What happens if an agent finishes but I am not satisfied?
The task stays in Development. You can give new instructions to the agent directly from its terminal. When you are happy with the result, drag the task to Done. You can also move it to Pending if you need to wait for something else before continuing.
Are tasks shared across my devices?
Yes. Tasks are synced to the AgentsRoom cloud and linked to your project via a stable backlog ID stored in .agentsroom/project.json. Any device with the same project sees the same backlog.
Can I attach images or screenshots to tasks?
Yes. Each task supports image attachments. Add mockups, screenshots, error captures, or design references directly to the task card. These are uploaded and stored securely.
Can I merge duplicate tickets?
Yes. Select several tickets on the board, or use the card menu, and merge them into one. The AI recombines their titles and descriptions into a draft you edit before confirming, upvotes add up, and comments, screenshots and links move to the survivor. A ticket keeps one parent, so a link that no longer fits (a second parent, a loop, a dependency on an epic) is listed in the preview and removed. The rule that matters: no reporter is ever lost. Everyone who reported an absorbed ticket stays subscribed to the survivor and is notified when the fix ships, and the public links already sent to them redirect to it.
Can one ticket run on a different provider or model from the rest?
Yes. A ticket can pin its own provider, model, reasoning effort, account profile and skills, and those overrides win over the default agent profile when the ticket spawns its agent. Columns can also be sorted on demand, on desktop and on mobile, and agents can create, update, comment, reorder and delete tickets over MCP without leaving the terminal.
Can a ticket wait for another one to be finished?
Yes. From a card's menu, choose Blocked by or Blocks, or link two tickets in Linked tasks, and the board enforces the link instead of just documenting it: while the blocker is still open, the blocked ticket sits in Pending rather than TODO, so Start next never picks it up, and its card reads Blocked by #12. It returns to TODO on its own when the last blocker closes, or is deleted, and goes back to Pending if that blocker is reopened. A dependency that would make a loop is refused, and the message names the loop. A ticket already in review or done is never parked, and a ticket you parked by hand stays where you put it. Agents handle the links themselves over MCP: one that discovers a prerequisite mid-run creates that ticket and links it in a single call, and a ticket that turns out to be blocked while in progress is moved out of the way without killing the terminal running it.
Where do I keep ideas that do not belong to any project yet?
In the idea box, a board attached to your account rather than to a project. Open the backlog board of any project, click the project name at the top and pick Idea box. Tickets there work like the others: title, description, tags, screenshots, synced on your account and visible from the mobile app. The one thing the idea box cannot do is start an agent, since there is no project to run it in: starting an idea opens the move dialog, and the ticket runs on the project you pick.
Can I move a ticket to another project?
Yes. Open the card menu, or select several tickets, and choose Move to another board. The ticket keeps its description, its attachments and its history and lands at the top of its column on the target board, from the desktop or from the ticket detail on the phone. Two things are left behind on purpose: the agent assigned on this machine, and the links to other tickets, because a dependency between two boards could not be seen from either. Move an epic and its tickets stay on this board, detached: the dialog says how many. A ticket reported by a client through the public backlog never moves: its public page and its conversation thread belong to the board it was submitted to.
Does a ticket keep a history of its versions?
Yes, since AgentsRoom 1.194.0. Every save that changes a ticket's text or configuration (title, description, type, tags, private note, assigned agent or team, skills, provider, model, reasoning effort, account profile, worktree options, reviewer) keeps the previous version, including a change made by an agent through MCP. On the desktop, open History from the ticket header to compare any earlier version with the current one and restore it; on the phone the version is loaded into the ticket form as a draft and saved normally. Board state is not versioned: dragging a card, changing its priority or marking it won't fix creates no version. The same history now exists for scheduled agents and for memory notes (memory on the desktop only), next to the one prompts and skills already had.
Can my agents leave notes on a ticket for the rest of the team?
Yes. Every ticket has a Comments section, the team's internal thread: you write in it from the ticket, your agents through the AgentsRoom MCP, to log progress, a hand-off, a blocker or a question. It is never shown to the person who reported the ticket and never emailed. The card shows how many comments a ticket has, and an agent started on the ticket reads the latest ones before it begins. In the project settings you can name a lead agent, a role such as the product manager or one saved agent: each time another agent comments, the lead gets a message so it can answer on the ticket, reassign it or bring you in.
How do I see which tickets will run in their own worktree?
On the card. A ticket set to run in a separate worktree shows its branch name at the bottom of the card, on the desktop and on the phone, and hovering it gives the full branch and whether it merges back on its own. Two tickets planned in parallel no longer look like two tickets sharing the same checkout.
Can a ticket wait for a decision instead of another ticket?
Yes, once Decisions is turned on (Settings > Backlog, or per project). Agents record on the board the questions that must be settled before the work goes on, each with its options, the option they recommend and who decides: you or another agent. A decision can hold its ticket: the ticket waits in Pending until the decision is answered, then goes back where it was. You answer from the ticket or from the waiting for input list in the title bar, on the desktop or the phone, and the agent that asked receives your answer. Off by default.
Can a kanban column start an AI agent with its own prompt?
Yes. Open the menu of a column header, choose Column prompt and write what the agent should do with the tickets dropped there: analyse without coding, write the plan, review the changes, run the tests. It works on every column, TODO, Development, Pending, In Review and Done included, and on the columns you add. When a ticket lands there, the prompt goes to the agent already working on it or to a new agent, or AgentsRoom asks you each time (Ask me, the default).
Do column prompts run when an agent moves a ticket, and what stops a loop?
Yes. A ticket moved by an agent over MCP runs the column prompt too, in the background, without opening a window. To stop two agents from bouncing a ticket between columns, moves made by agents start at most 10 column prompts per ticket in 24 hours. The limit lives in Settings > Backlog > Automatic column prompts per ticket, for every project or for one, and 0 removes it. Moves you make yourself are never limited.
How do I find a ticket an agent is talking about?
By its number. Every ticket gets a short number on its board, shown as #42 on the card and in the ticket detail, on the desktop and in the mobile app, and typing #42 in the board search finds it. Agents use the same number: the backlog tools of the AgentsRoom MCP accept #42 wherever they take a ticket id, agents are asked to cite a ticket as #42 and a short title and another agent by its tab name, and an agent started from a ticket opens in a tab named #42 followed by the ticket title. In the desktop app, a ticket reference or an agent id printed in an agent's console is clickable: hover it to see the ticket title or the agent's name, click it to open the ticket or bring that agent's tab to the front.
Can I set up the backlog board from a template?
Yes. The template button next to the columns, also offered once per project the first time you open its board, sets up the whole board in one click with three ready-made workflows: Classic (TODO, Development, Pending, Done), With spec (an architect writes the specification on the ticket, then a developer implements it) and Quality (spec, development, then a QA agent tests it before it waits for you). Each column comes with its prompt, its agent and a model suited to its job, picked for your own provider, and you can change any of them before applying. The agents keep a single ticket: a spec or a test updates the ticket or comments on it instead of creating sub-tickets. You can also save your own board as a template, for yourself or for everyone who works on the board, and reuse it on another project.
How do I organize a large feature into epics, tasks and subtasks?
Create an epic from the New task form, or convert a ticket from its card menu, then file tickets under it. A ticket has one parent and the tree stops at three levels: epic, task, subtask. Subtasks fold under their task as 3/5 instead of taking a card each, tasks show a chip with their epic, and you can filter the board by epic. If you already use tags as epics, filter on the tag and choose Turn this tag into an epic: the epic is created with the tag's tickets inside. Tickets that already have a parent keep it and are listed.
What does an epic show me?
Its card shows how many tickets are closed, how many are in progress, how many are blocked, and the next ticket ready to start. Open it and you get the page of the epic: its tasks and subtasks with their status and executor, what comes next, what is blocked and by what. When all its tickets are closed the card offers to close the epic. Closing it never closes anything else, and it asks first if tickets are still open.
How do agents work through an epic?
An epic is a container, so no agent ever works on the epic itself: it cannot be started or moved to Development. Start next and the backlog_start_next tool follow the same rule: never an epic, a parent still waiting on its subtasks, a blocked ticket or a locked one. An agent started on a child receives the goal of the epic and the status of its siblings, one line each. Start epic launches its ready tickets in dependency order, up to the limit you set, and says why the others do not start.
Can AI break an epic down, and can a ticket carry acceptance criteria?
Yes to both. Break down starts an agent of your project that reads the code and proposes tasks, subtasks, dependencies and acceptance items as a draft on the epic page. You edit it, and nothing exists until you approve it. Every ticket can also carry an acceptance checklist: agents tick the items they verified, the card shows 2/5, and closing a ticket with items still open asks you first.
Can I use the backlog without an account, or behind a company firewall?
Yes. Turn on local mode, with the Use without an account button on the board or in Settings > Backlog. Tickets, comments, links, checklists and project memory are then stored on your computer, with no call to agentsroom.dev for them, and agents and team runs work as usual. What really needs the server stays off: AI on tickets, the public backlog, the same board on your other computers. Signed in later, you can send what you wrote to your account in one click.
Can I schedule a ticket to start later, on a specific computer?
Yes. The clock next to Start on a To do card opens the timer: in 15 minutes to 4 hours, tomorrow morning, a chosen day and time, or your subscription's quota window (when the quota comes back, or shortly before it resets). Choose which of your computers runs it, or let the first available one take it. When the moment comes, the ticket starts with its own agent or team, even with your phone in your pocket, as long as AgentsRoom is running on that computer. If the computer was off, the ticket starts when AgentsRoom opens again. You can set and cancel a timer from the phone in the same way.
Can I run one epic overnight and have it stop there?
Yes. Start epic has a second mode, Run it to the end, then stop. AgentsRoom starts its ready tickets up to the limit you set, starts more as others close, and stops when the epic is finished, without touching any other epic. Launch it now or schedule it for tonight, from the desktop or the phone, on the machine you name. That machine has to stay on. An epic can also wait for another one: its tickets do not start until the first is closed. Pause holds an epic the same way, and agents already at work finish their ticket.
Can an epic be tested and checked for security before the next one starts?
Yes. On the epic page, turn on Tests, Security or add your own check. Once its tickets are closed, each check becomes a ticket of the epic with its own agent. A defect it finds becomes a new ticket, and the check runs again after the fix, up to three rounds on its own. When the epic reads Validated, a person closes it, and that is what releases the next one.
Can I move a ticket to another column without going back to the board?
Yes, while an agent is working on it. The agent's console has a Move ticket to… button that lists the board's columns in order, the ticket's current column greyed out with a check mark; pick one and the ticket moves on the spot. A column with a prompt runs it, an Ask me column asks whether to keep the agent, start a new one or just move the ticket, and To do sends the ticket back and closes the agent after a second click to confirm (the changed files stay). The same button sits at the bottom of the ticket window opened with the console's Ticket button, so you read the ticket and file it in the right column without leaving that window. Done and In Review keep their own buttons, the agent's console on the phone offers the same move, and a ticket no agent is working on is simply dragged on the board.

You may also like

Further reading

Turn your backlog into running agents

Download AgentsRoom and start dragging tasks to execution. Free for up to 2 projects.

Download AgentsRoomFree

Companion app: monitor your agents on the go

Bring your own: Claude, Codex, Antigravity CLI, or other AI provider.

Push bugs and requests straight to your public backlog.