{"version":"2.1.280","anchor":"much-more-detailed-refusal-messages-for-uploadingcapturing","canonical_anchor":"much-more-detailed-refusal-messages-for-uploadingcapturing","heading":"Much more detailed refusal messages for uploading\/capturing an untrustworthy git checkout","tier":"notice","area":"Git Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/much-more-detailed-refusal-messages-for-uploadingcapturing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Much more detailed refusal messages for uploading\/capturing an untrustworthy git checkout\n\nRemote session handoff now explains exactly why an untrustworthy git checkout is refused\n\n**What**\n\nWhen Claude Code hands a working copy of your repository off to a remote session (for example through bridge\/remote control features that upload or capture your checkout), it now gives a specific, worded explanation when it refuses to do so because the checkout looks untrustworthy. Cases include:\n\n- the `.git` entry being a symbolic link (which the session could re-point elsewhere)\n\n- the `.git` entry being a hard link\n\n- use of \"reftable\" storage for git references\n\n- objects borrowed from another repository\n\n- a nested repository inside the checkout\n\n- worktree-specific config\n\n- git config injected via environment variables\n\nEach case now gets a plain-language sentence explaining why the session refuses to proceed and what to do instead, such as starting from an ordinary clone.\n\n**Why**\n\nPreviously a refusal in these situations likely gave little or no explanation. Now users get a concrete reason and a suggested fix, making it easier to understand why a handoff was blocked and how to get past it.\n\n- Area: Git Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}