[Bug] switchModelsOnFlag silently switches models without user notification

Resolved 💬 2 comments Opened Jun 11, 2026 by JWVENTURE Closed Jun 15, 2026

Bug Description
switchModelsOnFlag silently switches off the user's chosen model (Fable -> Opus) with no clear notice

On Claude Code with model: claude-fable-5 as my default, a message got safety-flagged mid-session. switchModelsOnFlag (ON by default) silently switched the active model to Opus 4.8 and continued — no surfaced message that a switch happened or why. Only noticed later via /model.

Problems:

  1. Silent — losing an explicitly-chosen model should be loud, not a quiet default-on behavior. I had just spent a session fixing model persistence (stale env overrides), so an extra invisible reason the model changes is especially confusing.
  2. Discoverability — had to dig to find switchModelsOnFlag was the cause.

Asks:

  • Surface a visible notice on flag-triggered switches ("Switched Fable -> Opus due to a content flag").
  • Consider making it opt-in, or document the default prominently near model selection.

Env: Claude Code, macOS, default model claude-fable-5.

Environment Info

  • Platform: darwin
  • Terminal: WarpTerminal
  • Version: 2.1.170
  • Feedback ID: 590fd850-66a6-4150-8aac-f0538dd57a97

Errors

[]

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗