{"version":"2.1.285","anchor":"wip-stash-seeding-handles-ntfswsl-and-cancellation","canonical_anchor":"wip-stash-seeding-handles-ntfswsl-and-cancellation","heading":"Starting a cloud session from WSL or an NTFS folder handles Windows file rules","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/wip-stash-seeding-handles-ntfswsl-and-cancellation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Starting a cloud session from WSL or an NTFS folder handles Windows file rules\n\nWhen copying unsaved work into a cloud session, Claude Code now applies Windows file-name rules on WSL and NTFS, and reports a clear error if listing stops\n\n**Unclear.** It is not clear whether this seeding step is available to everyone or only when switched on.\n\n**What**\n\nWhen a cloud session starts, Claude Code can package your uncommitted work (changes not yet saved in git) to seed it. That step now:\n\n- applies NTFS path rules, the file-name rules Windows drives use, when it runs on WSL (Windows Subsystem for Linux) or in a folder on an NTFS drive\n\n- fails with a clear message if listing your git index is cancelled or runs out of time, rather than a vague \"could not list the index\"\n\n**Why**\n\nStarting a cloud session from Windows or WSL is less likely to trip over file names, and when it stops early you can see why.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}