Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.301 ·

Git config check for on-demand fetching can now target a named remote

Claude Code's safety check on git configuration before on-demand fetches can now check a specific named remote

Under the hood Internal Changes
JSON All of v2.1.301
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
GitArea: what it touches
Internal ChangesKind: in v2.1.301,
Internal ChangesSection of the release
What

In a partial git clone, some data is fetched only when it is needed (a "lazy fetch"). Claude Code checks the repository's git configuration before allowing this. That check can now be pointed at a specific named remote, a remote being a server git fetches from.

When it is:

  • It looks at that remote and at any remotes.<name> group setting.
  • It fails with named_remote_without_url unless the repository's own config sets remote.<name>.url.
  • It sets GIT_NO_LAZY_FETCH=1 and reports "GIT_NO_LAZY_FETCH is set, which switches this command off too".

Before, the check only ever looked at the remote that supplies missing data in a partial clone.

Why

It extends or tightens the safety checks Claude Code places around git fetching.

See this entry in the whole of v2.1.301 →

Feedback