[BUG] Mobile remote-control model picker shows stale selection after /model change in connected CLI session

Description

When a Claude Code CLI session is mirrored on the mobile app via Remote Control, the mobile app's model picker (Select model dialog) does not reflect model changes made from the CLI side with the /model slash command. It keeps the checkmark on the model that was last selected through the mobile UI.

Steps to reproduce

1. Start a Claude Code session in the CLI and connect to it from the mobile app via Remote Control.
2. At some earlier point, select a model from the mobile app's model picker (in my case Opus 4.8 (1M)).
3. In the CLI, run /model fable (or any other model). The CLI confirms: "Set model to Fable 5 and saved as your default for new sessions".
4. On the mobile app, open the model picker for the same remote-controlled session.

Expected behavior

The mobile model picker should show the session's current live model (Fable 5) as selected.

Actual behavior

The mobile picker still shows the previously selected model, Opus 4.8 (1M), with the checkmark. The session is actually running Fable 5 (confirmed by the model itself and by the CLI). This is confusing and risky: tapping the stale highlighted entry in the mobile dialog would silently switch the session back to Opus.

Environment

• Claude Code CLI: 2.1.170
• Desktop: macOS 26.5 (Darwin 25.5.0)
• Mobile: Claude mobile app on Android, Remote Control mode connected to the CLI session
• Subscription session (not API key)

Notes

The session transcript and behavior confirm the live model was Fable 5 while the mobile UI showed Opus 4.8 (1M) as selected, so this appears to be a UI state sync issue between the slash-command settings path and the mobile remote-control client.

Filed via Claude Code on behalf of the user.

🤖 Generated with Claude Code