Scheduled tickets

  • Desktop, mobile and web
  • All plans

What it does

A To do ticket can start by itself later: after a delay, at a time, on a chosen day, or on the subscription's quota window. It starts with its own agent or team, on the computer you picked, exactly as if you had clicked Start there.

Where to find it

The clock next to Start on a To do card of the board, desktop and phone. Once armed, the clock becomes the moment ("In 12 min", "Tue 10 Nov, 09:00", "On quota"): click it to change or remove the timer. Not on an epic or in the idea box.

How to use it

  1. Click the clock on a card.
  2. When you have several computers with this project, choose Which computer runs it: this computer by default (a sleeping computer can be picked), another one, or First available. With a machine pool, First available is proposed and the pool decides at the moment it starts.
  3. Pick In 15 min to In 4 h, Tomorrow, or a day and a time. A time with no day means today if it is still ahead, otherwise tomorrow. Or pick a quota rule: when the quota comes back, or before it resets past a usage threshold.

Settings

None. autoLaunchAgentsAtStartup applies: see Limits.

Agent tools (MCP)

  • backlog_update({ schedule }): { at } (ISO date), { inMinutes } or { quota: { kind, window, leadMinutes, minPercent } }, plus an optional deviceId (none: the first available machine). null removes the timer.
  • backlog_list: shows scheduledStart on an armed ticket.

Providers

All providers: the start goes through the normal ticket start. Quota rules need a provider that publishes a dated quota window, and are not offered for a team.

Mobile

Same clock and chip on the cards, same choices in a sheet, same machines. The phone only sets and cancels: the computer holds the clock, so the ticket leaves with the phone closed.

Limits

  • AgentsRoom must be running on that computer. It does not wake a sleeping machine: the ticket starts when the machine is awake and the app open.
  • With Start agents at launch off, a moment that passed while the app was closed does not start the ticket: the card reads Late, a notification says so, and you start it or pick a new time.
  • A locked ticket, a paused project, a full machine or a signed-out CLI make it wait: it stays programmed and leaves as soon as it can. A ticket parked behind a blocker keeps its timer and leaves once released.
  • If the start itself fails (worktree, missing agent), the ticket stays in To do without its timer and a notification says so. It is not retried.
  • Starting the ticket by hand, or moving it out of To do or to another board, removes the timer.

Common questions

  • Can a ticket start by itself later, or at a set time? Yes: the clock next to Start.
  • Can it run on another computer than this one? Yes, even one that is off right now, as long as AgentsRoom runs on it at that moment. If it never comes up, the card reads Late.
  • Can it start twice with First available? No: the server gives the start to one machine only.
  • What if the computer is off at that time? It starts when AgentsRoom opens again on it, unless Start agents at launch is off (see Limits).