Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

New .git entry validation for folder seeding

A new check inspects .git entries when seeding a folder and refuses linked index files, unknown entries, oversized folders or missing config/HEAD

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

Unclear The finding does not say what folder seeding is, and only suggests that this check backs the existing refusal message.

What

A new check examines each .git entry (the hidden folder where git keeps a project's history) when seeding a folder. It refuses:

  • Index files that are symlinked or hardlinked (links pointing to another file).
  • Entries it does not recognise.
  • .git folders that are too large.
  • Folders missing their config or HEAD file.

It seems to be what triggers the existing message "has a .git entry that could not be read as a git checkout".

Why

Only .git folders that look like normal, self-contained git checkouts get past this check.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what folder seeding is, and only suggests that this check backs the existing refusal message.

See this entry in the whole of v2.1.281 →

Feedback