Remote control messages not persisted to local session JSONL

Description

When a Claude Code CLI session transitions to remote control (via iPhone/mobile app or claude.ai/code), messages exchanged during the remote-controlled portion are not written to the local session JSONL file at ~/.claude/projects/<key>/<session-id>.jsonl.

The local JSONL contains all messages from the CLI portion of the session, but once remote control takes over, no further entries are appended. System entries and a last-prompt record are written, but the actual human/assistant conversation turns from the remote session are missing.

Steps to reproduce

1. Start a Claude Code CLI session: claude
2. Enable remote control: /remote-control
3. Connect from the iPhone app or claude.ai/code
4. Have a multi-turn conversation via the remote client
5. Disconnect remote control
6. Inspect ~/.claude/projects/<key>/<session-id>.jsonl

Expected behavior

All conversation turns (both CLI and remote-controlled) should be persisted to the local session JSONL file, since the local CLI process is still running and mediating the session.

Actual behavior

Only pre-remote-control messages appear in the JSONL. The remote portion is entirely absent from the local file. The conversation is visible on claude.ai/code in the browser, confirming it exists server-side, but it never reaches the local log.

Impact

Any tooling that reads from ~/.claude/projects/ session files (e.g., memsync for cross-machine memory management, or custom harvest scripts) cannot access the remote portion of the session. Users who transition between CLI and remote control during a session lose that portion of their local session history.

Related issues

• #28402 — Remote Control session not visible in session list
• #28039 — Web→CLI teleported sessions not appearing in Resume Session list
• #28571 — Remote control session fails to resync after connection drop

Environment

• Claude Code version: 2.0.73+
• OS: Windows 11 Pro
• Remote client: iPhone (Claude iOS app) and claude.ai/code