Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

/teleport stashes your changes more carefully and refuses unusual git setups

When /teleport stashes uncommitted changes, it now works on a private copy of git's index and refuses setups where that is unsafe

You'll notice Improvements
JSON All of v2.1.323
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 It is not clear whether this replaces the previous way of stashing for every /teleport, or only in some cases.

What

/teleport pulls a cloud session into your terminal. When you have uncommitted changes, Claude Code stashes them, meaning it sets them aside with git so they are not lost. It now does this by copying your checkout's index, git's record of what is staged, to a private place under Claude Code's config folder, stashing there, and then putting the index back in place.

It refuses to stash, with a message starting "Nothing was stashed:", in cases such as:

  • .git/index is a link or has a second name
  • the objects, refs or reftable entries in the git folder are links or junctions
  • the index could not be copied to the private place
Why

If your checkout uses an unusual git setup, such as a linked index, a checkout created with git-new-workdir, or one shared with WSL, /teleport now stops with instructions instead of stashing your changes.

Read from
Names in the bundle/teleport
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 doubtIt is not clear whether this replaces the previous way of stashing for every /teleport, or only in some cases.

See this entry in the whole of v2.1.323 →

Feedback