Uploading your repository to a cloud session checks the bundle and refuses more unusual setups

What

When you start a cloud session or use teleport, Claude Code packs your git repository into a single file called a bundle and uploads it. This step now does more checking and gives more specific reasons when it refuses.

• The bundle is checked after it is built and before it is uploaded. Missing objects, objects that were not listed and extra bytes at the end are caught.
• Refusals now cover git config files inside the checkout, GIT_CONFIG_GLOBAL, reftable and ref_storage settings, submodule modes, a filter driver named "unset" or "unspecified", a folder layout that changes during the build, and unstaged changes in a repository whose branch has no commits yet.
• The git folder is checked for tampering: a replaced git folder, HEAD or packed-refs not being plain files, hard-linked refs, objects changing mid-upload, dubious ownership, bad config, an unknown extension, a git stand-in that does not actually run git, and missing objects folders. These replace a single general tampering error.
• A message such as "Not uploading this working tree: this folder was moved, removed or replaced while the upload was being prepared" explains what went wrong.
• The starting-branch error now differs when a private git folder is used, and the upload can be limited to the current branch.
• When git stash fails, the reason is now read from git's structured results (object_missing, unmerged, index_locked) instead of matching git's message text, and the advice includes a retry hint for silent failures.

Why

A damaged or tampered bundle is caught before it is sent, and a refusal tells you exactly what about your checkout is the problem. If you use an unusual git setup, expect new, specific refusals where the upload used to go ahead or fail vaguely.