{"version":"2.1.290","anchor":"cloud-session-git-seeding-ahead-count-and-stricter-verifica","canonical_anchor":"cloud-session-git-seeding-ahead-count-and-stricter-verifica","heading":"Clearer errors when uploading a repository to start a cloud session","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-session-git-seeding-ahead-count-and-stricter-verifica","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Clearer errors when uploading a repository to start a cloud session\n\nUploading your repository for a cloud session now checks how far ahead of the remote your branch is and gives clearer errors\n\n**Unclear.** How Claude Code decides a branch is ahead of the remote before counting is not clear.\n\n**What**\n\nTo start a session that runs in the cloud, such as a remote or ultraplan session, Claude Code uploads a copy of your git repository. That upload step has changed:\n\n- Branch ahead of remote: it can count how many commits your branch is ahead of the remote copy, and gives an error saying the branch \"is too far ahead of\" it when that is too many.\n\n- Stricter checks: it double-checks each commit's parent commits, and lists files more efficiently.\n\n- Clearer failures: when stashing or updating git's index fails, the cause is labelled as a missing object, unmerged files, or a locked index.\n\n- Size error: the message for a repository that is too big now reads \"This repository is too large to upload: even without its history it is\" followed by details. Before, it said the repo was too large to bundle and asked you to set up GitHub on claude.ai\/code.\n\n**Why**\n\nThis affects starting remote and ultraplan sessions. When the upload fails, the message now tells you more about why.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}