Remote Control: archiving a session on iOS doesn't sync to the macOS app (archive state is per-client)

Summary

Archiving a Remote Control session in one client (Claude iOS app) does not archive it in another client (Claude macOS Desktop app). The session stays visible in the session list on the device where it wasn't archived. Archive state appears to be per-client and does not propagate.

Steps to reproduce

1. Start a Remote Control session on a Mac (claude remote-control).
2. Connect to it from both the Claude iOS app and the Claude macOS app.
3. Archive the session from the iOS app's session list.
4. Open / refresh the session list in the macOS app.

Expected

The session shows as archived on both clients. Archive is a session-level organizational intent, and per the docs the clients are "just a window into that local session," with state synced across devices.

Actual

The session is archived on iOS only. macOS still lists it as active. Archive state does not sync.

Why this looks like a bug rather than intended behavior

The Remote Control docs state the session syncs across all connected devices and that "the web and mobile interfaces are just a window into that local session." Conversation state already syncs across clients; archive — a session-level intent — should follow the same model. There's no scenario where a user archives on one device but wants the session to persist in the list on another, and the sync channel that carries the session list already exists.

(For contrast, the docs do call out things that are legitimately per-client/per-process — connection status, QR display, local-only commands like /mcp and /resume. Archive isn't in that category.)

Environment

• Clients: Claude iOS app + Claude macOS (Desktop) app
• Feature: Remote Control (research preview)
• Claude Code version: 2.1.167