{"version":"2.1.300","anchor":"teleport-readiness-check-gains-an-untracked-state","canonical_anchor":"teleport-readiness-check-gains-an-untracked-state","heading":"Teleport check can now report an untracked branch","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/teleport-readiness-check-gains-an-untracked-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Teleport check can now report an untracked branch\n\nBefore teleporting a session, Claude Code now runs an extra git check and can report the branch as untracked\n\n**What**\n\nBefore teleporting a session, Claude Code checks the state of your git repository. It used to report one of four results: no git, uncommitted changes, unpushed commits, or ready. It now runs one more git check, and if that check fails it reports a new result, untracked. The order of the unpushed-commits check has also changed.\n\n**Why**\n\nA branch that is not yet tracked could now stop a teleport with this new status.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}