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.219 ·

register_repo_root accepts launch-time directories and rejects duplicates

You can register repo roots under any directory passed with --add-dir, and duplicates now say so clearly.

Use it now Notable Improvements
JSON All of v2.1.219
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
SDKArea: what it touches
ImprovementsKind: in v2.1.219,
What probably matters to youSection of the release
What

The SDK register_repo_root request no longer requires the target to be a strict subdirectory of cwd, and now reports an already-registered directory as its own error instead of a subdirectory failure.

Details
  • the path is realpathed and confirmed to be a directory before anything else
  • accepted locations are directories under cwd or under any directory passed at launch via cliArg sources, that is --add-dir or the SDK additionalDirectories
  • registering a directory that is already a working directory fails with a dedicated error
  • on success, DirectoryAdded hooks are dispatched; hook failures are debug-logged and do not fail the request
  • the request schema description was rewritten to match
  • previously this threw register_repo_root: ... is not a subdirectory of cwd
Evidence

register_repo_root: directory is already a registered working directory

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle--add-diradditionalDirectoriesregister_repo_root
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded DirectoryAdded hook that fires after /add-dir or the SDK register_repo_root control request registers a new working directory…

See this entry in the whole of v2.1.219 →

Feedback