Model selection fails to update after restart (UI reflects change, but backend uses previous model)

[buYoung]

Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
• I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions

Describe the bug

debug ID : {"request_id":"8330495a-a78f-40e7-88ac-3c10c2473b7e","conversation_id":"bd2fe28c-d61d-4b4d-934c-f51c3f60f58e"}
debug ID2 : {"request_id":"d415b98e-f774-4e43-81b2-d34187aa2b9a","conversation_id":"72b235ae-a7f3-4c79-bff4-15e27c1b81fc"}

I initially suspected this was an issue specific to Gemini 3 Pro, but extensive testing reveals it is a broader bug related to how Warp handles model selection persistence after a restart.

The issue occurs when changing the model in the selector after Warp has been restarted. The UI correctly displays the newly selected model, but the actual API request routes to the previously selected model (or sometimes a completely different one). This indicates a serious desynchronization between the UI state and the backend execution logic.

To reproduce

1. Open the model selector and set the model to Model A (e.g., Claude 4.5 Sonnet or GPT 5.2 Codex).
2. Completely quit and restart Warp
3. Open the model selector again and change the model to Model B
4. Execute a prompt and check the Usage Summary
5. Observe the bug: Although the UI shows Model B, the log confirms that Model A (or an entirely different model) was actually called

Expected behavior

The model executed should match the model currently selected in the UI immediately, regardless of whether the app was restarted.

Screenshots, videos, and logs

Operating system (OS)

macOS

Operating system and version

mac os 15.5(24F74)

Shell Version

zsh 5.9 (arm64-apple-darwin24.0)

Current Warp version

v0.2026.01.28.08.14.stable_04

Regression

Yes, this bug started recently or with an X Warp version

Recent working Warp date

2026-01-30

Additional context

No response

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None