Mobile Offline Mode

  • Mobile app
  • All plans
View as Markdown

What it does

The phone is not always online. When agentsroom.dev cannot be reached (no signal, a captive Wi-Fi portal, a server that hangs), the mobile app keeps working for the things that do not need a live server: a ticket added in the subway, a todo ticked on a plane, an idea noted in a meeting. Each of these changes is applied on screen right away, kept on the phone, and sent in the order you made them as soon as the server answers again. Nothing is lost when you close the app in between.

The app decides "offline" by actually probing agentsroom.dev, not by asking the operating system whether it has a network: a 4G icon with no real connectivity is treated as offline, and a single lost request never flips the app into offline mode on its own. While the server is unreachable and the app is in front, it keeps probing with a growing delay.

This is about the AgentsRoom server. The connection to your desktop is a separate thing, shown by the connection banner and covered in Mobile-Desktop Sync.

Where to find it

There is nothing to turn on. You notice it through what the app shows:

  • A card at the top of the app the moment the server stops answering: agentsroom.dev is unreachable: working offline. with the hint Tap to retry. It shows once per outage and fades by itself.
  • A status banner on the Projects tab, the Settings tab and the prompt and skill library sheets: Working offline with "agentsroom.dev is unreachable. Your changes stay on this phone and are sent as soon as it answers." Once something is queued, the banner counts it: 1 change waiting to sync. / N changes waiting to sync. with a Retry action.
  • Backlog board: the same "changes waiting to sync" line with Retry above the header; each ticket captured or edited offline carries a Waiting to sync badge.
  • Todo list (list icon in the header of the Projects tab): an upload glyph in front of a line that has not been sent yet.
  • Radar: Waiting to sync in the meta line of an idea card.

How to use it

  1. Use the app as usual while offline: add a ticket with Add a task, tick or rename a todo, tap Write an idea then Add to the Radar.
  2. The change appears immediately, marked as waiting. Keep going; changes pile up in order.
  3. When the phone is back online, nothing to do: the queue is sent one item at a time as soon as the server answers, the desktop reconnects or the app comes back to the foreground. Tap Retry on a banner to force an attempt.
  4. Once sent, the badge disappears and the item takes its server identity (a ticket number, for example).

What is queued while offline:

  • Backlog tickets: create, edit, move to another column, Decline without email, delete. Photos attached to a ticket created offline are uploaded right after the ticket itself.
  • Todos: add, tick, rename, change bucket, delete.
  • Radar ideas: Add to the Radar, Park.

What is never queued, and fails with the usual error while offline:

  • Reordering a column (positions would conflict with other devices).
  • Anything that runs AI: merging tickets, clean up, automatic titles.
  • Starting a ticket, on the desktop or in the cloud. On a ticket that has not reached the server yet, Start and Start in the cloud stay visible but disabled, with the reason: "This ticket has not reached agentsroom.dev yet. It can start once it has."
  • Turning an idea into a ticket (it emails everyone who asked for it). On an idea noted offline, the answer is "Not synced yet: this will be available once it reaches agentsroom.dev."
  • Anything that drives the desktop: agents, terminals, git, teams, dev commands, SSH and databases, prompt and skill libraries.
  • Anything that writes to a person: Decline & notify, replies to a reporter, chat messages. Sending an email hours later without you knowing is a trap, not a feature.

If the server refuses a queued change once it is sent (for example the ticket was deleted from another device in the meantime), the change is dropped and the usual error message of that screen tells you.

Settings

None.

Agent tools (MCP)

None. Agents never see the phone's queue; they see the tickets, todos and ideas once they have reached the server.

Providers

All providers, no difference.

Mobile

This is a mobile-only feature. The desktop app has no such queue.

Limits

  • Only the actions listed above are queued; everything else needs the server or the desktop to answer right now.
  • A ticket, todo or idea created offline cannot be started, promoted or otherwise acted on by the server until it has been sent.
  • A change queued for an item that the server no longer accepts is discarded with an error, never silently kept.
  • The queue is sent in order, one item at a time: a network failure pauses it, a refusal from the server removes only the refused item.
  • Photos of a ticket created offline are kept on the phone until the upload; if an upload fails, the ticket is still created without that photo.
  • The demo mode of the app never queues anything.

Common questions

  • The app says agentsroom.dev is unreachable but I have signal. The app trusts its own probe, not the network icon. A captive portal, a VPN, or a server outage look the same to it. Tap the card to probe again.
  • The connection banner says the desktop is disconnected. Is that the same thing? No. The desktop link is about your computer being reachable through the relay; offline mode is about the AgentsRoom server. Both can happen at once, and both banners then stack.
  • I created a ticket offline. Can I start it now? Not until it has reached the server: the Start buttons are disabled with the reason. Wait for the badge to disappear, then start it.
  • Do the queued changes survive if I close the app? Yes, they are kept on the phone and sent the next time the server answers.
  • Why did my "Decline & notify" fail while offline? Because it emails the reporter. The app never queues an email to a person; use Decline without email or retry once online.

Related

  • Mobile-Desktop Sync: the other link, phone to desktop, and its own connection banner.
  • Backlog Task Board: the tickets that can be captured and edited offline.
  • Idea Radar: the ideas that can be noted and parked offline.
  • Mobile Companion: the companion's own queue for files shared while the desktop is unreachable.