Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.219 Home All releases ←olderv2.1.218 v2.1.220newer→
Claude Code v2.1.219

register_repo_root accepts launch-time directories and rejects duplicates

Use it now
Useful4 Signal0
SDK Notable

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

--add-diradditionalDirectoriesregister_repo_root
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.219 →