{"version":"2.1.299","anchor":"cloud-session-git-sanitized-option-and-empty-repo-index","canonical_anchor":"cloud-session-git-sanitized-option-and-empty-repo-index","heading":"Cloud session repository setup handles empty repositories","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/cloud-session-git-sanitized-option-and-empty-repo-index","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Cloud session repository setup handles empty repositories\n\nRepository setup for cloud sessions now handles an empty repository and skips pushing some branches when a session is released\n\n**What**\n\nWhen Claude Code prepares a git repository for a session running in the cloud, it now:\n\n- accepts a \"sanitized\" option\n\n- loads the current commit into the staging area when the repository is empty, and reports an error if it cannot\n\n- skips pushing for some branches when the session is released, and does extra cleanup\n\n**Why**\n\nThese are behind-the-scenes changes to how cloud sessions set up and tidy up repositories.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}