{"version":"2.1.301","anchor":"read-file-tool-gated-as-ccs-read-file-git-fetch-ref-not-fou","canonical_anchor":"read-file-tool-gated-as-ccs-read-file-git-fetch-ref-not-fou","heading":"Clearer error when git fetch cannot find a branch, plus smaller fixes","tier":"notice","area":"Git","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/read-file-tool-gated-as-ccs-read-file-git-fetch-ref-not-fou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Clearer error when git fetch cannot find a branch, plus smaller fixes\n\nA git fetch for a branch or tag missing on the remote now fails with a clear, permanent error, and vim mode's `%` does nothing when it has nowhere to jump\n\n**Unclear.** What the list of `ccs_` names controls, and so what adding `ccs_read_file` to it changes for a reader, is not clear.\n\n**What**\n\nThis release brings several small changes:\n\n- When Claude Code fetches from git and the branch or tag (a ref) does not exist on the remote, it now reports `git fetch failed (permanent): ref not found on the remote`.\n\n- In vim mode, the `%` key jumps to a matching bracket. It now does nothing when the cursor would stay where it is.\n\n- `ccs_read_file` has been added to an internal list of names that begin with `ccs_`.\n\n- A setting named `streamEventFlushOnFirstDelta` is no longer passed through with other configuration.\n\n**Why**\n\nThe git error marks the failure as permanent, so it is clear that trying the same fetch again will not help.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}