Skip to content

Simplify cloud environment dropdown when only one environment exists#2304

Draft
joshsny wants to merge 1 commit into
mainfrom
joshsny/simplify-cloud-env-dropdown-2004
Draft

Simplify cloud environment dropdown when only one environment exists#2304
joshsny wants to merge 1 commit into
mainfrom
joshsny/simplify-cloud-env-dropdown-2004

Conversation

@joshsny
Copy link
Copy Markdown
Contributor

@joshsny joshsny commented May 22, 2026

Problem

When a user has only one cloud environment (the built-in Default), the workspace mode dropdown shows a "Cloud environments" section header with a single "Default" item underneath. This is confusing — "Cloud environment: default" doesn't clearly communicate what it means.

Changes

Modified WorkspaceModeSelect to detect when there are no custom sandbox environments and render a simple "Cloud" option inline with the other workspace modes (Worktree, Local) instead of the full "Cloud environments" section.

  • 0 custom environments: Shows a single "Cloud" item with description "Run in a cloud sandbox", no separator or section header
  • 1+ custom environments: Preserves the existing behavior with the "Cloud environments" section, "Default" entry, and all custom environments listed

How did you test this?

Verified the component typechecks and that the lint-staged pre-commit hooks pass. No existing tests for this component.

Publish to changelog?

no

Slack Thread

Open in Web Open in Cursor 

When the user has no custom sandbox environments, show a single 'Cloud'
option inline with the other workspace modes instead of a separate
'Cloud environments' section with just the 'Default' entry. The full
section with separator, header, and per-environment list is preserved
when the user has created custom sandbox environments.
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.

2 participants