{"version":"2.1.299","anchor":"upload-failure-advice-now-says-to-commit-changed-files-by-na","canonical_anchor":"upload-failure-advice-now-says-to-commit-changed-files-by-na","heading":"Cloud upload failure advice tells you to commit changed files by name","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/upload-failure-advice-now-says-to-commit-changed-files-by-na","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Cloud upload failure advice tells you to commit changed files by name\n\nIf preparing a cloud session's upload fails, Claude Code advises committing the files you changed by name, then retrying\n\n**Unclear.** Whether this wording actually differs from the previous release.\n\n**What**\n\nA cloud session runs Claude Code on a remote machine, and it starts by uploading your git repository. If preparing that upload fails and Claude Code has no more specific advice, it shows: \"Commit the files that you changed by name (git add , then git commit), then retry.\" Earlier wording suggested running `git add .` or committing.\n\nThe separate warning about filenames that are not safe on Windows keeps the same wording.\n\n**Why**\n\nIn practice, the advice steers you toward committing only the files you meant to change, rather than adding everything in the folder at once.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}