Skip to content

[Docs] Correct environment and MCP setup guidance - #1412

Draft
roomote-community[bot] wants to merge 1 commit into
developfrom
fix/docs-accuracy-audit-36idfe5b3p677
Draft

[Docs] Correct environment and MCP setup guidance#1412
roomote-community[bot] wants to merge 1 commit into
developfrom
fix/docs-accuracy-audit-36idfe5b3p677

Conversation

@roomote-community

Copy link
Copy Markdown
Contributor

​Created by Roomote. View the task or mention @roomote for follow-up asks.

What changed

  • corrected the custom MCP server guide to count all four supported connection types
  • updated the environment definition reference to explain that repository command failures currently produce warnings while setup continues

Why this change was made

A full audit of the public documentation found two claims that no longer matched the documented table or current repository setup behavior.

Impact

Operators now get accurate guidance when configuring custom MCP servers and interpreting repository command failures during environment setup. No product behavior changes.

@roomote-community

roomote-community Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor Author

1 issue outstanding. See task

  • apps/docs/environments/definition.mdx:204 incorrectly says continue_on_error never affects repository setup; snapshot-environment setup still honors it.

Reviewed 539a181

| `timeout` | number | no | Seconds before the command is killed. Defaults to `600`. |
| `retries` | integer | no | Extra attempts for a failing command, with a 1-second delay. Use only for idempotent commands. Defaults to `0`. |
| `continue_on_error` | boolean | no | When `true`, setup continues even if this command fails. Defaults to `false`. |
| `continue_on_error` | boolean | no | Currently does not change repository setup behavior; failures are recorded as warnings and setup continues. |

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

continue_on_error still changes behavior for snapshot-environment setup: that path passes continueRepositoryCommandFailures: false, so the command executor honors the per-command flag and continues only when it is true. The new absolute wording tells snapshot authors the opposite. Please scope the warning-only behavior to standard task environment setup, or document the snapshot distinction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant