fix(web): changing projects no longer creates a draft

[extoci]

Changing projects while a prompt had been typed used to create a draft and move the prompt into it. That was confusing and unnecessary, this fixes it (videos below).

Keep the existing draft and composer session. Changing projects now retargets the draft logical-project mapping in place; leaving the draft still triggers the normal persistence behavior. Remove the transfer workaround and its tests.

Before

Screen.Recording.2026-09-02.at.12.00.42.AM.mov

After

Screen.Recording.2026-09-01.at.11.59.16.PM.mov

Verification: 116 focused tests passed, plus targeted lint and web typecheck.

Built by Codex on behalf of @extoci.

---

Note

Medium Risk
Touches composer draft identity, project mapping, and cross-environment attachment metadata; behavior change for project switching is user-visible but removes a confusing draft-creation path rather than altering send/auth flows.

Overview
Changing the project from the draft hero headline no longer mints a new thread or sidebar draft row. The picker retargets the same draftId via setLogicalProjectDraftThreadId, so typed prompt and attachments stay in the current composer session; a sidebar draft only appears if the user navigates away later.

The old path—handleNewThread with carryComposerContent and moveComposerPromptAndImages—is removed from the store and useNewThreadHandler, along with related upload-queue tests and attachment-stay-behind toast behavior.

Draft store updates for in-place retargeting: reassigning a draft clears any other logical-project key still pointing at that draftId, and when the target project’s environment changes, file rows drop cross-environment upload metadata so attachments surface as needing reattach. Model defaults still apply via shared hasExplicitComposerModelSelection when the user hasn’t explicitly picked a model.

^{Reviewed by Cursor Bugbot for commit 4dd676d. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Retarget open draft to selected project in place instead of creating a new draft

• Selecting a project from DraftHeroHeadline now calls setLogicalProjectDraftThreadId to retarget the currently open draft to that project, preserving the prompt and session.
• Removes the old moveComposerPromptAndImages store method and all related carry-content logic from useNewThreadHandler; new thread creation no longer moves content from the viewed draft.
• Adds clearStaleFileUploadMetadata so retargeting a draft to a different environment clears uploadedAttachmentId and uploadEnvironmentId; affected files report composerFileNeedsReattach.
• Adds hasExplicitComposerModelSelection to centralize explicit-model detection; when the current draft lacks an explicit pick, retargeting applies the project's default model.
• Behavioral Change: moveComposerPromptAndImages is removed from ComposerDraftStoreState; any out-of-tree callers relying on it will break. Retargeting also removes the draft's previous logical-project mapping and clears cross-environment file upload metadata.

^{Macroscope summarized 4dd676d.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 3f5a7fa. Configure here.}

[macroscopeapp]

This is the state transition the PR's fix depends on (a retargeted draft must stop resolving from its previous logical project), but no test asserts it — the existing remap tests only check branch/worktree/env-mode. A focused case would guard the regression directly:

store.setProjectDraftThreadId(projectRef, draftId, { threadId });
store.setProjectDraftThreadId(otherProjectRef, draftId);
expect(store.getDraftThreadByProjectRef(projectRef)).toBeNull();
expect(store.getDraftThreadByProjectRef(otherProjectRef)?.draftId).toBe(draftId);

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Approved at 4dd676d

Macroscope's review found this PR approvable — The PR removes the unintended draft-creation path when switching projects and keeps the existing composer session, with focused coverage for project remapping and cross-environment attachments. The remaining changes are localized cleanup and model-selection handling rather than a new workflow or schema change.

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

[extoci]

Codex on behalf of @extoci: addressed the review findings in 4dd676d.\n\n- Cross-environment retargets clear stale upload metadata, so hydrated files cannot reuse an upload from the old environment.\n- In-place retargets reapply sticky and destination-project defaults unless the composer selection is explicit.\n- Added focused regression coverage for stale uploads, destination remapping, and explicit-selection handling.