You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Web / desktop composer, multiple connected environments.
Steps to reproduce
Connect two environments that support starting without a project.
Open a new draft for a normal project available on both environments.
Use Run on to select the remote environment.
Select or start without a project (or choose No project from the project picker).
Try to change Run on again before sending a message.
Expected behavior
The draft can retain the selected environment, and Run on remains usable to choose another connected environment that supports No project.
Actual behavior
No project inherits the previously selected environment, but the host choices collapse to that environment. On a remote environment its indicator remains visible but the picker is disabled; on the primary environment the indicator can disappear. The user cannot change where the unsent No project draft will run.
Impact
Minor bug or occasional failure. The user must choose the intended environment through a normal project before starting without a project.
Version / environment
Reported on macOS desktop with multiple connected environments. The same client path is present on main at cfdff56f7b3c9c931ae368224041aa14825649fd.
Related fix
#15200 fixes this reproduced problem by deriving No project choices from connected scratch-capable environments, rather than matching the current scratch project. This report records the observed failure; no competing implementation is proposed.
Before / after verification
Reproduced in T3 Code’s Browser panel with two isolated environments named Laptop and Remote server. Both captures use the same draft, project data, dark theme, and 1280 × 800 viewport.
Before: main at cfdff56f7b3c9c931ae368224041aa14825649fd. Selecting No project retains Remote server but removes the host picker.
Focused verification: vp test run apps/web/src/hooks/useScratchProject.test.tsx apps/web/src/components/BranchToolbar.logic.test.ts apps/web/src/composerDraftStore.test.ts — 234 tests passed across 3 files.
Area
Web / desktop composer, multiple connected environments.
Steps to reproduce
Expected behavior
The draft can retain the selected environment, and Run on remains usable to choose another connected environment that supports No project.
Actual behavior
No project inherits the previously selected environment, but the host choices collapse to that environment. On a remote environment its indicator remains visible but the picker is disabled; on the primary environment the indicator can disappear. The user cannot change where the unsent No project draft will run.
Impact
Minor bug or occasional failure. The user must choose the intended environment through a normal project before starting without a project.
Version / environment
Reported on macOS desktop with multiple connected environments. The same client path is present on main at
cfdff56f7b3c9c931ae368224041aa14825649fd.Related fix
#15200 fixes this reproduced problem by deriving No project choices from connected scratch-capable environments, rather than matching the current scratch project. This report records the observed failure; no competing implementation is proposed.
Before / after verification
Reproduced in T3 Code’s Browser panel with two isolated environments named Laptop and Remote server. Both captures use the same draft, project data, dark theme, and 1280 × 800 viewport.
cfdff56f7b3c9c931ae368224041aa14825649fd. Selecting No project retains Remote server but removes the host picker.dd58107652fac6ef25f258902c67bcbb2ce515b2. The No project picker remains available; switching to Laptop and back to Remote server succeeds.Focused verification:
vp test run apps/web/src/hooks/useScratchProject.test.tsx apps/web/src/components/BranchToolbar.logic.test.ts apps/web/src/composerDraftStore.test.ts— 234 tests passed across 3 files.