[BUG] Remote Control: a session created on an older CLI greys out newer models ("Update Claude Code on the machine running this session") after the machine is updated

Environment

• Claude Code 2.1.284 on Linux, running claude remote-control --name <name> --capacity 32
• Viewing client: claude.ai web

What happens
A session in the machine's Remote Control entry was created on 2.1.278, with --model claude-opus-5. The machine has since been updated to 2.1.284, and the server has been restarted several times. Every restart re-dispatches the session on 2.1.284: its process runs 2.1.284 --print --sdk-url … --model claude-opus-5.

In that session's model picker on claude.ai, Opus 5.5 stays greyed out with "Update Claude Code on the machine running this session to use this model." The picker footer shows "Opus 5".

A new chat in the same Remote Control entry, on the same machine and server, offers Opus 5.5 normally.

Expected
Once the machine runs a CLI that supports the model, an existing session should be able to switch to it. Or, if the block is intentional for existing sessions, the message should say that, not ask for an update that is already installed.

Notes

• The block appears to come from claude.ai's record of the session (created on the old CLI), not from the machine's current version.
• Possibly related: #84225 (model changes in Remote Control sessions not applying).