[BUG] --teleport of a web session restores only the first turn; later turns missing

Summary

claude --teleport on a Claude Code on the web (cloud) session resumed only the first assistant turn. The later user message and its reply, both visible on claude.ai, did not come through. The branch checkout also failed.

Environment

• Claude Code 2.1.273, native install, Linux (Debian, kernel 6.1)
• Cloud session on claude.ai/code, GitHub app connected with access to the repo
• Local clone of the same repo, on the same commit as the web session (7dbff8c, clean tree)

Steps to reproduce

1. On claude.ai/code, start a web session on a GitHub repo. The first turn runs one shell command and gives a summary.
2. Send a second message (hola) and wait for the reply to finish.
3. Click "Open in terminal" and run the copied claude --teleport ... command from a local clone of the repo.

Observed

The local terminal shows only the first turn:

❯ Sesion Web
  Ran 1 shell command
Estoy conectado al repo nomad (rama actual con el último commit 7dbff8c ...) ...
Dime la tarea y trabajo sobre la rama claude/web-session-q2n2va.

● Session resumed without branch: Failed to checkout branch 'claude/web-session-q2n2va'

The web session shows two turns: the one above, then hola and the assistant's reply. Neither of those reached the local copy, and nothing in the resume output says the transcript is incomplete.

Expected

The local session contains the same turns claude.ai shows, or the resume output says it is partial.

Branch checkout

git ls-remote origin 'claude/*' returns nothing: the web session never pushed claude/web-session-q2n2va because it made no commits. The code matched here, so nothing was lost, but if the web session had uncommitted or unpushed work, Session resumed without branch would drop it with a one-line notice. A note on what "without branch" means, or pushing the branch before handoff, would help.

Not yet verified

I have not checked whether this is timing (teleport fetched a snapshot from before the second turn was saved) or a real cutoff (teleport only brings part of the log). A repeat with a third turn, waiting for the page to show it after reload before teleporting, would tell the two apart.

Related

• #74277: teleport restored no history (closed as inactive, not fixed)
• #93892: teleport of Remote Control sessions
• #92734: teleport drops prompt history (conversation itself restored fine there)