{"version":"2.1.290","anchor":"teleport-stash-refuses-when-tracked-files-became-folders","canonical_anchor":"teleport-stash-refuses-when-tracked-files-became-folders","heading":"Teleport refuses to stash when a tracked file has become a folder","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/teleport-stash-refuses-when-tracked-files-became-folders","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Teleport refuses to stash when a tracked file has become a folder\n\nBefore stashing for teleport, Claude Code now stops with 'Nothing was stashed' if a tracked file was replaced by a folder\n\n**What**\n\nBefore teleporting, Claude Code can stash your uncommitted changes, which means setting them aside with git. It now first checks whether any file or link that git tracks has been replaced by a folder. If so, it refuses with a message that begins 'Nothing was stashed' and explains that stashing could delete what is in that folder for good.\n\nIf the check itself cannot be completed, nothing is stashed either.\n\n**Why**\n\nIn this situation stashing could permanently delete the folder's contents. Refusing keeps your files where they are.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}