fix(web): Local environment switch stays reachable after turning it off

[ScottN-PV]

Problem

On desktop, turning off Local environment in Settings → Connections hides the switch that turns it back on. With the local environment off there is no primary environment, so the "This machine" card shows only "No environment selected", and the Settings search result for "Local environment" lands on the same empty card. The issue's workaround uses DevTools.

Change

ConnectionsSettings now renders LocalEnvironmentSetting in the "No environment selected" branch as well. The component returns nothing without the desktop bridge, so browser and hosted builds are unchanged.

Scope and approval

Closes #17013. The triage comment confirms the cause on main and suggests this fix. The branch condition changed in #9786.

Verification

An agent ran these checks. No person tested the change.

Desktop dev app (vp run dev:desktop) on Windows 11, isolated state, localEnvironmentEnabled: false, no remote environments:

Before (main)	After

Turning the switch on and confirming Restart and turn on relaunches the app with the local environment running, and Connections shows the machine card again (hostname covered):

recovery.mp4

Web tsc --noEmit passes. vp lint and vp fmt --check on the changed file pass. No unit test: the change adds one element to an existing branch, and a test would only assert component structure, which AGENTS.md asks us not to do. The desktop run above is the regression check. Not checked: macOS and Linux desktop builds, and the reporter's setup with a remote environment connected. The primary environment id is null in that setup too, so the same branch renders.

Model: Claude Opus 5.5, Claude Fable 5.1 (review), GPT-6-Astra (review). Harness: Claude Code, Codex.

[macroscopeapp]

Approvability

Verdict: Approved at 15dd720

Macroscope's review found this PR approvable — This localized UI fix keeps the existing local-environment switch visible after the local environment is disabled, without changing the toggle logic or other runtime paths. It introduces no schema, deployment, security, billing, or static-analysis changes.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7e073d16-0d06-41b2-afa7-8ead9c3b7df9

📥 Commits

Reviewing files that changed from the base of the PR and between d81afa0 and 15dd720.

📒 Files selected for processing (1)

• apps/web/src/components/settings/ConnectionsSettings.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

When no primary environment is selected, Connections settings now renders LocalEnvironmentSetting below the “No environment selected” row. The conditional T3 Connect row remains unchanged.

Changes

Connections settings

Layer / File(s)	Summary
Show local environment control in fallback apps/web/src/components/settings/ConnectionsSettings.tsx	The no-environment-selected section now renders LocalEnvironmentSetting beneath its message row.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix · Severity of issue fixed: Medium

Suggested reviewers: juliusmarminge

Merge Risk: ⚪ Minimal · up to 15dd7

The change makes the local-environment switch available in the no-environment settings view. No concrete merge-blocking behavior is identified.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 15dd7

The switch remains desktop-only and requires explicit confirmation. No new privilege or authorization bypass was identified. Recovery from an interrupted restart is not fully established, so the assessment retains limited uncertainty.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The changed interaction targets the current desktop installation’s persisted local-execution setting and restart lifecycle. It supplies no remote environment, tenant, credential, or arbitrary setting identifier to the privileged operation.

Trust Boundaries and Controls

• inferred — The new rendering location does not expand the desktop renderer’s existing IPC authority. Startup installs IPC handlers before the disabled-backend branch, and the preload already exposes the setter. UI confirmation is an interaction safeguard, not a new authorization boundary.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check		The title is concise, uses the repository's conventional format, and clearly describes the primary fix: keeping the Local environment switch reachable after it is disabled.
Description check		The description includes all required sections. It explains the problem, change, scope and approval, verification results, screenshots, limitations, and agent details.
Linked Issues check		Issue #17013 requires the Local environment switch to remain visible in the desktop Connections settings after the local environment is disabled. The PR adds LocalEnvironmentSetting to the “No environ…
Out of Scope Changes check		The reviewed change is limited to adding LocalEnvironmentSetting to the existing fallback branch in apps/web/src/components/settings/ConnectionsSettings.tsx. This directly supports issue #17013 and do…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}