fix(web): apply sticky model selection when reusing draft threads

[JoeEverest]

What Changed

When creating a new thread, the sticky model/provider/options are now applied in all three code paths in useHandleNewThread, not just when creating a brand-new thread.

Extracted an applyStickyModel helper inside the callback to avoid duplicating the logic across paths.

Why

Only Path C (brand-new thread creation) applied the user's sticky model selection. Paths A and B — which reuse existing draft threads — skipped it entirely. Since draft threads are persisted in localStorage and survive app restarts, clicking "New Thread" almost always hits Path A, finding a stale draft with provider: null and model: null. This causes ChatView.tsx to fall back to the default provider ("codex") and model ("gpt-5.4"), resetting the user's selection.

Path A (line 57): Existing draft found for project via getDraftThreadByProjectId() → navigated to it without applying sticky model.
Path B (line 79): Current route is already a draft for this project → reused it without applying sticky model.
Path C (line 95): Brand new thread → was the only path that applied sticky model correctly.

Before	After
before.mov	after.mov

Closes #1276

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

Note

Apply sticky model selection when reusing existing draft threads

When reusing an existing draft thread (stored project draft or active draft for the current route), sticky model/provider settings are now applied if the draft has no model already set. A new helper applyStickyModel(threadId, draftModel?) in useHandleNewThread.ts encapsulates this logic. Behavior for brand-new threads is unchanged.

^{Macroscope summarized 50de946.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: aad93ef0-7506-464e-bb41-a1af3c3fcbd6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.

[Copilot]

Pull request overview

Ensures the user’s sticky model/provider and model options are applied consistently when starting a “New Thread”, including when the app reuses an existing persisted draft thread (common due to localStorage-backed drafts).

Changes:

• Added an applyStickyModel(threadId) helper within useHandleNewThread to centralize sticky model/provider/options application.
• Applied sticky model/provider/options to the two draft-reuse paths (stored project draft and “already on a draft for this project”), not just the brand-new draft creation path.
• Removed duplicated sticky-application logic from the new-thread creation path in favor of the helper.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[maria-rcks]

@JoeEverest tell your agent to rebase and force push (making this pr just one commit)