Crash Screen

  • Desktop, mobile and web
  • All plans
View as Markdown

What it does

When the interface itself breaks, AgentsRoom shows a readable screen instead of a black window (desktop) or a white one (phone). It names the error, tells you that your projects, agents and teams are safe on disk and that your running agents are untouched, and gives you two ways back in, from the least destructive to the most. One of your agent portraits is drawn at random and shown as the one who "was on shift when the interface went down", so the worst moment of the day is not a warning triangle.

Your agents keep running behind it: the crash is in the window, not in the CLIs.

Where to find it

Nowhere on purpose. It replaces the whole window when a screen fails to render, or when the app fails to boot at all. On the desktop it also appears when the interface cannot reach the app process at start (the message then begins with Electron bridge unavailable); that screen shows up at once with the generic message, and its Technical details gain the exact cause (Preload error: followed by the app process's own exception) a moment later, once the app process has handed it over. Both surfaces show the same thing:

  • The error class as a pill (TypeError, ReferenceError...), the title AgentsRoom hit an unexpected error, then What went wrong with the error message.
  • Two buttons, then Install the latest version, the agent card, and Technical details folded over the stack trace.
  • This error was reported to the AgentsRoom team. appears when data sharing is on (on the phone, only once the report has actually left).

How to use it

  1. Click Reload. It rebuilds the interface where you were; nine times out of ten that is the end of it.
  2. If the crash comes back at every launch, use the second button. On the desktop it is Reload without restoring the last session: it drops the saved window layout, which is replayed at every start and is usually what replays the crash. On the phone it is Reload on the home screen: it lets go of the screen you were on, which is the phone's equivalent of that layout.
  3. If it still comes back, press Install the latest version. It opens the download page on the desktop, and your App Store or Play Store listing on the phone: a crash that keeps coming back is often one that a newer build already fixes, and a crash loop is the one moment where you cannot reach the update button anywhere else in the app.
  4. Open Technical details if you want to read (or copy) the stack trace before reloading.

Nothing else is asked of you: if you consented to data sharing, the report already left with the error, its fingerprint, the app version and the platform. For an Electron bridge unavailable screen, one single report leaves: the detailed one when the cause reaches the screen within a few seconds of start, the generic one otherwise.

An agent that crashed is a different case: the window is fine, only the CLI in that pane has exited. Relaunch it with Restart the agent, in the Pane options menu (the three-dot button of the terminal header) or in the right-click menu of the agent's tab; the entry is there at all times, not only after a crash, so it also restarts a live agent. The right-click menu of the terminal itself offers the same as Restart. The terminal prints Restarting… and the CLI comes back on the same conversation.

Settings

  • Settings > Privacy & data, data sharing: the single gate. Off, nothing is sent and the "reported to the team" line does not appear. Home directory paths are stripped from the report before it leaves.

Agent tools (MCP)

None.

Providers

All providers, no difference: this is the AgentsRoom window failing, not a CLI. A crash of the app does not stop the agents already running.

Mobile

Present, with the same design and the same server-side reports; the body sentence and the footer hint are worded for the phone. Three differences, all deliberate: the second button is Reload on the home screen instead of dropping a window layout the phone does not have, Install the latest version opens the App Store or the Play Store rather than the download page, and the "it is fixed" email that follows a desktop crash is not sent for a phone-only crash, because it points at the desktop download page.

Limits

  • A crash of the display process itself (out of memory, killed) is not caught by this screen: the desktop reloads the window on its own, at most twice within a minute, then leaves it as it is.
  • Reports are grouped by fingerprint, with anti-flood caps: crashing in a loop does not send hundreds of reports.
  • A crash on the phone and the same crash on the desktop are one entry for the team, not two.
  • The screen is deliberately built out of almost nothing (its own avatar list, its own English fallback text): a crash means the module graph is already broken, so it can only rely on itself. It may therefore show English strings when everything else is translated, and the Electron bridge unavailable message and its Preload error cause exist in English only.

Common questions

  • Did I lose my work? No. Projects, agents, teams and memory are on disk, and the agents that were running are untouched.
  • The app crashes again every time I reopen it. Use the second button: on the desktop Reload without restoring the last session, on the phone Reload on the home screen.
  • The message says Electron bridge unavailable. Neither reload button can help: the app process and the interface are not talking, usually because the installation is damaged (under Technical details, PreloadMissing: file not found names the file). Restart AgentsRoom, then reinstall it with Install the latest version if the screen comes back.
  • Was the error sent to you? Only if data sharing is on; the screen says so when it was.
  • It is my agent that crashed, not the app. How do I bring it back? Open the Pane options menu of its terminal header (three dots) or right-click its tab and choose Restart the agent. The CLI is relaunched on the same conversation. The same entry works on an agent that is still running, when you want a fresh CLI without losing the thread. A tab that is not in the visible layout has no such entry: open it first.
  • Will I be told when it is fixed? For a desktop crash, yes: an email points at the version that fixes it. For a phone-only crash, not yet.

Related