--remote-control: model selection in Claude app does not propagate to remote session

Description

When using claude --remote-control, changing the model via the Claude app UI has no effect on the model serving the session. The session remains on the model configured at the host level.

Steps to reproduce

1. Start claude --remote-control
2. Connect via the Claude app
3. Change model selection in the app (e.g. to claude-sonnet-4-6)
4. Ask the model what it is

Expected behaviour

Session model updates to the one selected in the app.

Actual behaviour

Model remains as configured on the remote host (e.g. claude-fable-5). The /model command in-session also has no effect — the new model is reported as set but the system context still reflects the host model.

Context

• Using --remote-control with the Claude desktop app
• App model selector appears to target cloud sessions only, not remote-controlled local processes
• Unclear if this is intended scoping or a missing propagation path