You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
TeleportArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
Unclear Whether the repository check before stashing is always active or behind a switch is not clear.
What
Teleport brings a session that ran in the cloud into your local Claude Code. It changed in these ways:
It no longer falls back to an older way of loading the session when the main one returns nothing
It loads only the session's own history, and when that is missing it stops with "Couldn't load the history of cloud session"
It no longer shows a separate "not found. Run /status" message
Before stashing your local changes, it checks that the folder's .git directory still matches the repository the session is tied to, and stashes nothing if it does not
Stashing is git's way of setting your uncommitted changes aside.
Why
When resuming a cloud session goes wrong, you get a plain explanation, and your local changes are not stashed into the wrong repository.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether the repository check before stashing is always active or behind a switch is not clear.
Anthropic's release notes agreeFixed claude doctor and /status saying a linked managed settings file is still read when it could not be read
