From a5e7b995fda5e22c398401a0ef08cdf657687ff4 Mon Sep 17 00:00:00 2001 From: Roomote Date: Thu, 13 Aug 2026 03:07:09 +0000 Subject: [PATCH] docs: sync recent user-facing behavior --- apps/docs/environment-variables.mdx | 4 ++-- apps/docs/environments.mdx | 6 ++++++ apps/docs/integrations/roomote-mcp.mdx | 17 +++++++++++++---- apps/docs/self-hosting.mdx | 8 ++++---- apps/docs/skills.mdx | 7 +++++++ apps/docs/tasks.mdx | 4 ++++ 6 files changed, 36 insertions(+), 10 deletions(-) diff --git a/apps/docs/environment-variables.mdx b/apps/docs/environment-variables.mdx index eadbe990d..b039e8312 100644 --- a/apps/docs/environment-variables.mdx +++ b/apps/docs/environment-variables.mdx @@ -291,8 +291,8 @@ as per-task auth tokens or workspace paths. | `R_GITHUB_CLIENT_SECRET` | GitHub | GitHub OAuth client secret. | | `R_GITHUB_WEBHOOK_SECRET` | GitHub | GitHub webhook secret. | | `GITHUB_MCP_SERVER_URL` | Optional | GitHub MCP server URL override. | -| `GITHUB_AUTOMATED_SKIP_REPOS` | Optional | Repository skip list for automated GitHub processing. | -| `GITHUB_AUTOMATED_SKIP_OWNERS` | Optional | Owner skip list for automated GitHub processing. | +| `GITHUB_AUTOMATED_SKIP_REPOS` | Optional | Comma-separated repository skip list for automated GitHub handling. Review activity still reaches existing Roomote tasks. | +| `GITHUB_AUTOMATED_SKIP_OWNERS` | Optional | Comma-separated owner skip list for automated GitHub handling. Review activity still reaches existing Roomote tasks. | | `GITLAB_BASE_URL` | Optional | GitLab base URL for self-managed GitLab. | | `GITLAB_CLIENT_ID` | GitLab | GitLab OAuth application ID. | | `GITLAB_CLIENT_SECRET` | GitLab | GitLab OAuth application secret. | diff --git a/apps/docs/environments.mdx b/apps/docs/environments.mdx index e6272e8c5..599bc8772 100644 --- a/apps/docs/environments.mdx +++ b/apps/docs/environments.mdx @@ -48,6 +48,12 @@ The setup task is meant to produce a working environment Roomote can reuse. If it cannot finish, adjust the input and try again from **Settings > Environments**. +During setup, Roomote asks only for environment variables that block the local +install, canonical tests, selected startup path, or another capability the +environment is meant to verify. Credentials used only by optional integrations, +deployment workflows, production services, or other unvalidated paths remain +deferred until a task actually needs those capabilities. + ## Start from a brand-new repository You do not need an existing codebase to set up an environment. From diff --git a/apps/docs/integrations/roomote-mcp.mdx b/apps/docs/integrations/roomote-mcp.mdx index 0a14dc253..65ec0033c 100644 --- a/apps/docs/integrations/roomote-mcp.mdx +++ b/apps/docs/integrations/roomote-mcp.mdx @@ -37,12 +37,17 @@ This is useful when you want to: ### Bring in Roomote and chat context Ask what your Roomote deployment can do or which integrations are connected. -You can also read relevant conversation history from connected chat channels. -For Slack and Discord, provide a channel or message link when you want context -from a specific conversation. +You can also list discoverable chat channels, then read relevant conversation +history from a selected channel. Roomote can list public Slack channels the app +has joined and Discord channels your linked Discord account can access. Microsoft +Teams and Telegram do not support channel listing, but you can still provide a +channel or message link when you want context from a specific conversation. Roomote still applies the access rules from the connected service, so the MCP -only returns conversations your signed-in user is allowed to read. +only returns conversations your signed-in user is allowed to read. For Slack, +public channels are available when the Roomote app has joined them, even if your +linked Slack account has not. Private channels require both the app and your +linked Slack account to be members. ## Things to try @@ -54,6 +59,7 @@ only returns conversations your signed-in user is allowed to read. morning.” - “Tell the running task to add a regression test before it opens the PR.” - “Use this Slack message as context and explain what the team decided.” +- “List the Slack and Discord channels you can access.” - “Cancel the task working on the old approach.” ## Connect your MCP client @@ -152,6 +158,9 @@ and connected-service access checks still apply to every request. You can revoke the connection from your MCP client. If a saved session expires or is revoked, Roomote asks you to approve access again in the browser. +Roomote rotates refresh tokens and revokes the whole session if an already-used +refresh token is replayed. If that happens, reconnect the MCP client to start a +new session. ## Troubleshooting diff --git a/apps/docs/self-hosting.mdx b/apps/docs/self-hosting.mdx index cce01adf1..7208e7db8 100644 --- a/apps/docs/self-hosting.mdx +++ b/apps/docs/self-hosting.mdx @@ -212,7 +212,7 @@ deployment should let you: not the container's), so it defers garbage collection and lets memory drift well above what the service needs; a container memory cap then kills the process before Node ever feels pressure. Current app images cap each Node - service's heap by default (768 MB for web and api, 512 MB for controller and - bullmq, reduced to ~75% of the container's memory when a cgroup limit is - set). Set `NODE_OPTIONS=--max-old-space-size=` on a service to override - the default, or on older images to add the cap manually. + service's heap by default (4096 MB for web, 768 MB for api, and 512 MB for + controller and bullmq, reduced to ~75% of the container's memory when a + cgroup limit is set). Set `NODE_OPTIONS=--max-old-space-size=` on a + service to override the default, or on older images to add the cap manually. diff --git a/apps/docs/skills.mdx b/apps/docs/skills.mdx index 4522be357..441b980e1 100644 --- a/apps/docs/skills.mdx +++ b/apps/docs/skills.mdx @@ -10,6 +10,13 @@ specialized workflow. In the task prompt, type `/` to search the packaged skills available to Roomote, then select one to insert its slash invocation. +For example, select **Doctor** when you want Roomote to check whether an +environment can complete a specific developer or user journey. Doctor launches +a fresh, read-only task against that environment and reports the smallest +boundary where a failure belongs. It does not change the environment or +repository unless you explicitly ask it to repair the problem; after an +authorized repair, it verifies the same journey again in another fresh task. + Use Skills when the same guidance keeps showing up across tasks in an environment: a framework-specific review checklist, a release process, a design-system rule, a data workflow, or a repeatable debugging path. diff --git a/apps/docs/tasks.mdx b/apps/docs/tasks.mdx index 04ae6393b..bcb63c39b 100644 --- a/apps/docs/tasks.mdx +++ b/apps/docs/tasks.mdx @@ -91,6 +91,10 @@ You can send follow-up instructions while a task is active. If a task has completed and Roomote has a restorable snapshot, a follow-up can resume from that prior workspace instead of starting over. +In the prompt composer, type `/` to search available commands and packaged +skills. Use the **Context** menu to search for and attach repository files; +typing `@` does not open file search. + Good follow-ups are specific: - "Apply the second option and add a regression test."