Teleported session fails to open in VS Code extension ("No conversation found with session ID")

When teleporting an active Claude Code session from the mobile/web app to the VS Code extension, opening the teleported session in VS Code fails with:

Error spawning Claude (on channel <channel-id>): Error: Claude Code returned an error result: No conversation found with session ID: <session-id>

The channel is then closed and the session state resets to idle without ever loading the conversation.

Investigation:
A local stub file exists at ~/.claude/projects/<project>/<session-id>.jsonl containing only:

{"type":"teleported-from","remoteSessionId":"session_...","messageCount":0}

The actual conversation content (remote session) is never synced into this local file before VS Code attempts to load it, so the local lookup finds messageCount: 0 and reports "no conversation found." Multiple occurrences of this stub-without-content pattern were found for separate teleport attempts, suggesting a race condition between stub creation and remote sync.

Steps already tried (did not resolve):

1. Reopening the session in VS Code
2. Reloading the VS Code window ("Developer: Reload Window")
3. Checking for VS Code extension updates

Environment: Linux (headless server, accessed via VS Code Remote), extension used to teleport from the official Claude mobile/web app.