RooCodeInc · roomote-community · Aug 4, 2026
@@ -21,7 +21,9 @@ When anonymous telemetry is enabled, your deployment sends:
   setup timestamps; counts of users, environments, and connected repositories;
   task, model, token, and cost totals for the past day; pull-request statistics
   for the past week; configured provider types; and enabled built-in
-  integrations.
+  integrations. It also includes total and enabled custom automation counts and
+  the keys of enabled built-in automations, but not automation prompts,
+  schedules, or destinations.
 
 What is **never** sent: names, emails, repository names, task contents,
 prompts, code, tokens, or credentials.

@@ -80,6 +80,10 @@ Create arbitrary scheduled agent runs with:
 - an optional **report destination** channel (Slack, Discord, Teams, or
   Telegram)
 
+The destination selector lists only communications providers that are
+currently connected. If a saved provider is disconnected, reconnect it before
+editing the automation or choose another destination.
+
 Admins can also choose **Custom schedule** and enter either a standard
 five-field cron expression or a natural-language schedule such as “weekdays at
 9am.” Roomote previews the interpreted schedule before saving and asks for
@@ -110,7 +114,9 @@ an explicit IANA timezone.
 
 Admins can also manage custom automations from a Roomote task through the
 `manage_custom_automations` tool: list, resolve a schedule, create, update,
-delete, or run an enabled automation immediately.
+delete, or run an enabled automation immediately. After creating an automation
+conversationally, Roomote asks whether you want to run it immediately as a
+test.
 
 ## Channel automations
 
@@ -134,9 +140,9 @@ the Roomote bot can already see in your server.
 
 A few provider-specific behaviors to know:
 
-- On Discord, messages from people who have not linked their Discord account
-  to Roomote do not start tasks; Roomote sends them a direct message
-  explaining how to link instead.
+- On Discord, Roomote keeps the latest request from an unlinked person for 10
+  minutes and sends them a direct message explaining how to link. Completing
+  the link during that window starts the saved request automatically.
 - Messages posted by other bots or webhooks (for example a deploy or alert
   feed) can start tasks too. Use launch criteria to keep noisy feeds in
   check — for example, only launching on new or worsening alerts.

@@ -60,8 +60,10 @@ linked, Roomote can attribute a task to the right user, respect access rules,
 and continue the right thread when someone replies later.
 
 If someone asks Roomote to do work from chat before their account is linked,
-Roomote prompts them to link the account. After linking, they may need to send
-the request again.
+Roomote prompts them to link the account. On Discord, Roomote keeps the latest
+request for 10 minutes and starts it automatically when linking succeeds during
+that window. Other communications providers may require the request to be sent
+again.
 
 Telegram and Discord use one-time link codes instead of acting as sign-in
 providers. Generate a code under **Settings > Personal > Linked Accounts** and

@@ -11,6 +11,8 @@ Admins use the other settings pages to connect tools and configure shared
 behavior. Individual teammates use Personal Settings to link their own
 identities, adjust the app, and manage profile details.
 
+Open the signed-in user menu and select the **Personal settings** icon.
+
 ## Open your profile
 
 Use **Profile** to update account details such as your name, email,

@@ -83,7 +83,8 @@ Azure snapshots capture memory and disk, so a restored sandbox resumes in
 sub-second time with processes still alive. Task standby uses the same
 memory-preserving suspend/resume, and sandboxes bill storage-only while
 suspended. Preview port URLs do not survive a snapshot restore; Roomote
-re-adds ports after resume.
+re-adds ports after resume. Suspended tasks wake only when Roomote explicitly
+resumes them, such as for a follow-up; preview traffic does not wake a sandbox.
 
 ## Egress TLS inspection
 

@@ -37,6 +37,10 @@ on [ChatGPT pricing](https://chatgpt.com/pricing).
 
 ## Common issues
 
+- **A device code expires.** Select **Restart** to generate a fresh code and
+  begin authorization again.
+- **A workspace policy blocks authorization.** Ask a ChatGPT workspace admin to
+  allow the Codex app, then select **Restart**.
 - **Authorization expires or fails.** Use **Reconnect** and finish the device
   flow with the same eligible ChatGPT account.
 - **Usage is not displayed.** The unofficial usage endpoint may be unavailable;

@@ -129,6 +129,10 @@ empty PostgreSQL/MinIO/Redis volumes, and starts the recorded Roomote release.
   in a single transaction while the previous release keeps serving. If a
   migration fails, the schema rolls back, the previous configuration is
   restored, and the previous release stays up.
+- **Failed upgrades restore the previous configuration.** Failures before the
+  new release starts, including image-pull failures, restore the prior
+  environment, Compose, and Caddy configuration and restart the previous
+  controller when needed.
 - **Rollback is one command.** Every release's schema keeps the previous
   release working, so `roomote rollback` re-deploys the prior release without
   touching the database. `roomote upgrade <tag>` does the same for any

@@ -81,10 +81,17 @@ look for:
 | Preview           | Whether the visible result matches the claim for UI or workflow changes                    |
 | Artifacts         | Plans, reports, screenshots, or other outputs you may want to reuse or review              |
 
+Command tool calls show their output in a collapsed, copyable section in the
+transcript, so you can inspect the details without leaving the task.
+
 When an environment setup command fails, open the task **Logs** panel and
 select its `Setup: <command>` entry. The command's output is available there
 without needing to enter the sandbox workspace.
 
+If an environment fails to start before the agent produces any output, the
+task may show **Retry**. Roomote hides that action after agent output exists to
+avoid running the same work twice.
+
 ## Continuing work
 
 You can send follow-up instructions while a task is active. If a task has

@@ -110,7 +110,8 @@ browser allows it. The full invite URL is only shown at creation time, so copy
 it before leaving the page.
 
 You can revoke an invite before it is used. Revoking an invite does not affect
-people who already joined with it.
+people who already joined with it. Revoked and fully used invites disappear
+from the Settings list; create a new invite when you need another link.
 
 ## Manage existing users