Skip to content

[Improve] Rename Settings Compute to Sandboxes - #35

Merged
mrubens merged 3 commits into
developfrom
improve/rename-compute-to-sandboxes-2cwn95pda6nja
Jul 9, 2026
Merged

[Improve] Rename Settings Compute to Sandboxes#35
mrubens merged 3 commits into
developfrom
improve/rename-compute-to-sandboxes-2cwn95pda6nja

Conversation

@roomote-roomote-v1

@roomote-roomote-v1 roomote-roomote-v1 Bot commented Jul 9, 2026

Copy link
Copy Markdown

Opened on behalf of Matt Rubens. Follow up by mentioning @openmote, in the web UI, or in Slack.

What changed

Renames the user-facing product term from Compute to Sandboxes across the settings surface, setup flow, public docs, and operator/deploy guides and templates.

  • Settings nav/title and route: Sandboxes at /settings/sandboxes
  • In-page labels use sandbox provider terminology
  • Public docs, Coolify/Railway/Fly/Render READMEs and templates use sandbox provider / hosted sandboxes wording (including hyphenated hosted-sandbox references)
  • Legacy /settings/compute route removed
  • Internal computeProvider APIs, packages, env var names, and DB fields unchanged

Why this change was made

Team consensus was that "Compute" is too generic and Sandboxes is the clearer product term. Follow-up review passes caught remaining mixed wording in operator deploy docs/templates after the initial product UI rename.

Impact

Admins and operators see Sandboxes consistently in the UI, setup, docs, and deploy guides/templates. Runtime provider behavior and env var names are unchanged.

Screenshots

Settings nav and page title show Sandboxes

Default sandbox provider and Hosted sandbox worker image sections

Sandboxes page still loads at /settings/sandboxes after redirect removal

Use Sandboxes as the user-facing product term for sandbox provider
settings and docs, while keeping internal computeProvider APIs.
@roomote-roomote-v1

roomote-roomote-v1 Bot commented Jul 9, 2026

Copy link
Copy Markdown
Author

No new code issues found. See task

  • deploy/coolify/README.md:25 - The Sandboxes rename is still incomplete in operator-facing deployment docs/templates: Coolify still says "Hosted compute", and Railway/Fly/Render guides/templates still use "hosted-compute" or "compute provider" (for example deploy/railway/README.md:198, deploy/fly/fly.toml:21, deploy/render/README.md:317, and render.yaml:39). Please finish sweeping public/operator references or explicitly mark the old term as legacy.

@roomote-roomote-v1

roomote-roomote-v1 Bot commented Jul 9, 2026

Copy link
Copy Markdown
Author

Fixed remaining operator deploy wording in 89e8092.

  • Coolify README / compose comments: Hosted sandboxes
  • Railway / Fly / Render READMEs + templates (fly.toml, template.yaml, root render.yaml): hosted-sandbox workers and hosted sandboxes wording
  • Left env var names like EXCLUDED_COMPUTE_PROVIDERS unchanged

No open review threads (summary checklist item).

mrubens added 2 commits July 9, 2026 15:33
Sweep remaining operator/docs "compute provider" wording and remove the
legacy /settings/compute redirect.
Replace remaining Hosted compute / hosted-compute product wording in
Coolify, Railway, Fly, and Render operator docs and templates.
@mrubens
mrubens marked this pull request as ready for review July 9, 2026 15:44
@mrubens
mrubens merged commit 1121add into develop Jul 9, 2026
@mrubens
mrubens deleted the improve/rename-compute-to-sandboxes-2cwn95pda6nja branch July 12, 2026 04:19
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