You'll notice
Useful2 Signal3
Teleport checks whether your local checkout diverged from the remote before deciding what to seed into the container.
What's wrong with this entry?
Anonymous. No account, no email.
What
When a teleport target syncs a directory into a container, Claude Code now checks whether your local checkout has diverged from the remote before deciding which source to seed from, and records the reasoning.
Details
- Requires directory sync to be armed, a git root, no agent id, an async capability check to pass, and a stored file mode of
container_sync. - The check module is loaded lazily and raced against a deadline, with abort support, so a slow probe does not stall the decision.
tengu_teleport_source_decisiongained dimensions for the probe verdict and failure reason, probe duration, counts of differing tracked files and digested paths, the container origin kind, a reason when sync was not armed, and whether the ref was pinned.
Evidence
tengu_teleport_source_decision
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.219
Teleport branch-mismatch error explains what the checkout actually is
Both mention teleport
-
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