General router model does not persist across sessions

[mbornstein5]

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

The general router model does not persist when selecting it as base model

To reproduce

open settings -> agents -> profile -> based model -> 'general router'
when to window closes the base model changes to 'auto'
when using the general router credits where consumed although i was using my own api key.
all my credits where consumed

Expected behavior

the 'general router' model persists across sessions

Screenshots, videos, and logs

No response

Operating system (OS)

macOS

Operating system and version

26.5.1

Shell Version

No response

Current Warp version

v0.2026.06.24.09.19.preview_03

Regression

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

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

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

No response

[oz-for-oss]

@mbornstein5

Here's what I found while triaging this issue:

• I found a closely related report in Agent Profile model always set to auto after I set to a custom model #13136 where an Agent profile model selection reverts to auto; this issue appears to be the router-backed/macOS Preview variant.
• For credits already consumed, please contact Warp support rather than posting account details publicly.

I have a few follow-up questions before I can narrow this down:

1. Is general router a Custom Router you created in Settings > Agents > Custom Routers, and does it route only to your own BYOK/custom endpoint models?

Reply in-thread with those details and the triage workflow will automatically re-evaluate the issue and update the diagnosis, labels, and next steps.

Maintainer details

I concluded that selecting a custom/general router as an Agent profile base model appears to revert to the default auto model after Settings/model refresh, likely due to router IDs being omitted from one persisted-model reconciliation path..

Triage summary

This looks like an Agent profile/settings persistence bug for a router-backed base model. The report is on macOS Preview v0.2026.06.24.09.19.preview_03 and describes selecting general router under Settings > Agents > Profile > Base model, then seeing the selection revert to auto after the settings window closes.

A closely related open report, #13136, describes custom profile model selections reverting to auto, but the dedupe workflow requires at least two existing likely duplicates before marking this issue as a duplicate.

Likely code area

The relevant persistence path is the Agent execution profile model: the profile editor writes the selected base model into AIExecutionProfile.base_model, which is cloud-backed via AIExecutionProfilesModel. Custom model routers are represented as synthetic LLMInfo entries in the custom-router:* namespace.

One suspicious reconciliation path is LLMPreferences::reconcile_disabled_model_preferences: for persisted base/coding models it checks server-provided models and custom endpoint models, but it does not include the custom router lookup used elsewhere for active model resolution. That can make a local custom router selection look unusable and clear it back to None, which causes the active model to fall back to the default auto model.

The reported credit usage is plausibly downstream of the silent fallback to Warp-hosted auto, but any account-specific credit/refund investigation should go through support rather than the public issue thread.

Repro/impact

Repro confidence is medium: the issue includes a concrete settings path, exact build, OS, and expected behavior, and there is a very similar open report. The remaining ambiguity is whether general router is a locally-created Custom Router or a server/team-provided router.

Suggested next step

Confirm the router source and then check app/src/ai/llms.rs reconciliation logic so custom router IDs are considered usable when validating persisted profile model selections.

Question reasoning

1. Is general router a Custom Router you created in Settings > Agents > Custom Routers, and does it route only to your own BYOK/custom endpoint models? — The most likely client-side reset path specifically affects custom router IDs; confirming whether this is a local custom router versus a server/team-provided router changes root-cause confidence without requiring any secrets.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz