{"version":"2.1.323","anchor":"teleport-stash-now-works-on-a-private-copy-of-the-git-index","canonical_anchor":"teleport-stash-now-works-on-a-private-copy-of-the-git-index","heading":"\/teleport stashes your changes more carefully and refuses unusual git setups","tier":"notice","area":"Teleport","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/teleport-stash-now-works-on-a-private-copy-of-the-git-index","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### \/teleport stashes your changes more carefully and refuses unusual git setups\n\nWhen \/teleport stashes uncommitted changes, it now works on a private copy of git's index and refuses setups where that is unsafe\n\n**Unclear.** It is not clear whether this replaces the previous way of stashing for every \/teleport, or only in some cases.\n\n**What**\n\n`\/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.\n\nIt refuses to stash, with a message starting \"Nothing was stashed:\", in cases such as:\n\n- `.git\/index` is a link or has a second name\n\n- the `objects`, `refs` or `reftable` entries in the git folder are links or junctions\n\n- the index could not be copied to the private place\n\n**Why**\n\nIf 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.\n\n- Area: Teleport\n- Names: `\/teleport`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}