fix(web): Resume continues on the model picked in the composer

[akbarakma]

Problem

After a thread stops on a usage limit, picking another model or provider account and pressing Resume still runs on the old, limited one. It fails again right away. Typing a message instead works, because Send passes the picked model and Resume does not.

Fixes #15555

Change

The Resume handler now passes the composer's current model selection with its "Continue where you left off." turn, the same way Send does. The server already switches provider when a manual continuation arrives with a different model.

No UI change. #16889 fixes the same omission and also redesigns the Resume button. This PR is only the missing argument, in case the smaller change is easier to land.

Scope and approval

A very small, focused fix for a confirmed bug: two lines in ChatView.tsx. Resume after a manual Stop uses the same handler, so it follows the picker too.

Verification

Web dev build on macOS with its own data folder. A second Claude instance was pointed at a local endpoint that answers 429, which T3 classifies as a usage limit. The "Ran on" column is the provider instance recorded on each run.

Code	Picker set to	Action	Ran on	Result
main	limited instance	typed message	limited instance	failed, usage limit
main	default Claude	Resume	limited instance	failed, usage limit
this PR	default Claude	Resume	default Claude	completed
this PR	unchanged	Stop, then Resume	same instance	resumed
this PR	limited instance	Resume after Stop	limited instance	failed, usage limit

• The completed Resume answered the original request, so the conversation carried over to the new instance.
• vp fmt --check and vp run --filter @t3tools/web typecheck pass. vp lint on the file shows the same warnings as main.
• Not checked: a switch to a different driver such as Codex, a real usage limit, the packaged desktop app.

Before, on main. The default Claude account is picked and Resume hits the limit again:

After. Same click, and the run completes on the picked account:

Built with Claude Opus 5.5 through Claude Code, running in T3 Code.

[macroscopeapp]

Approvability

Verdict: Approved at 7f3ff79

Macroscope's review found this PR approvable — This is a two-line, self-contained web bug fix that makes Resume use the composer's existing model/provider selection, matching the behavior of Send. The request field is already supported and existing fallback behavior remains intact.

^{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: fd97e809-211d-48a5-bc1e-9812994dc91b

---

📥 Commits

Reviewing files that changed from the base of the PR and between 50647de and 7f3ff79.

---

📒 Files selected for processing (1)

• apps/web/src/components/ChatView.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 a run resumes, onResume now includes the composer’s selected model in the startThreadTurn request when one is available. Other continuation fields and held-queue resume behavior remain unchanged.

Changes

Resume model selection

Layer / File(s)	Summary
Include the selected model in manual resume apps/web/src/components/ChatView.tsx	onResume conditionally passes the composer’s selected model to startThreadTurn.

Priority: ⬇️ Low

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

Change: Bug fix · Severity of issue fixed: Low

Suggested reviewers: juliusmarminge

---

Merge Risk | ⚪ Minimal · up to 7f3ff

Merge Risk: ⚪ Minimal · up to 7f3ff

Resumable-run Resume now follows the composer’s selected model, with the existing server handoff preserving prior context when providers differ. A specific driver pair was not runtime-tested, but source inspection establishes no actionable merge blocker.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 7f3ff

Resume now follows the account selected in the composer, using the same request path as Send. Existing continuation checks remain in place, and no new permission or externally accessible endpoint was identified. Risk is low, with interrupted provider-switch recovery not fully verified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The newly affected action is manual continuation of a resumable thread, potentially carrying its conversation context to another selected provider instance. Comparable provider selection and context transfer were already reachable through Send; no greater provider-access or tool authority was established from this change.

Trust Boundaries and Controls

• observed — Client-supplied model selection does not replace the server’s manual-continuation eligibility checks. The referenced run must be the latest executed run and either interrupted or usage-limit failed; archived/deleted threads and pending runtime requests are rejected independently of selection.

Resilience and Maintainability Implications

• observed — The existing handoff-start path checks the current attempt before starting a provider turn, attempts to restore unsent handoffs when a prompt is refused, and records accepted delivery. Failure to record delivery can leave a pending marker that forces a fresh native thread later; this behavior predates the PR. Complete interruption and restart recovery remains unverified.

---

Pre-merge checks | 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: Resume now uses the model selected in the composer.
Description check		The description covers the problem, change, scope justification, verification results, limitations, screenshots, and agent details. It is complete and consistent with the pull request changes.
Linked Issues check		For [#15555], ChatView.tsx now passes the composer’s current model selection to startThreadTurn in the Resume handler. This matches the Send path and allows the existing server handoff path to use…
Out of Scope Changes check		The pull request changes only the Resume request in apps/web/src/components/ChatView.tsx. The two added lines directly implement [#15555]. No unrelated UI, server, or cleanup changes are present.

---

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

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

---

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