Teleport now tells you whether the repo genuinely mismatched or the git remote just couldn't be read.
What's wrong with this entry?
The "You must run claude --teleport ... from a checkout of ..." error now tells you why the current directory did not match, separating a genuine repo mismatch from a git remote it could not parse.
- repo mismatch shows the session's repo plus a "This repo is ..." line
- an unparseable remote reports that case explicitly instead of implying a mismatch
- the session repo is qualified with its host when the host is not the default
Couldn't parse your git remote:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.223
Teleport and remote-control commands explain themselves inside cloud sessions
Both mention teleport
-
v2.1.224
--teleportand--cloudshow up inclaude --helpBoth mention teleport
-
v2.1.229
/teleporthint mentions both directionsBoth mention teleport