Source Intelligence

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.208 Home All releases olderv2.1.207 v2.1.209newer
Claude Code v2.1.208

  • File deny rules now block edits, not just reads. A new clear error message is shown when a file is covered by a Read deny rule and the user attempts to edit it: "File is covered by a Read deny rule in your permission settings and cannot be edited." (search for "File is covered by a Read deny rule")
  • Ripgrep usage errors (invalid patterns, unsupported glob syntax, unknown file types) are now caught and reported as RipgrepUsageError rather than surfacing as raw subprocess failures. The error message includes the rejection reason: "Search failed — ripgrep rejected the pattern, glob, or file type without searching" (search for "Search failed — ripgrep rejected the pattern")
  • The apiKeyHelper script failure notification is now a clear user-facing message: "Your apiKeyHelper script is failing · This usually means you need to re-authenticate with your provider · Run /status to see the script's error output" (search for "Your apiKeyHelper script is failing")
  • Symlink resolution in the Linux sandbox deny-path logic was improved: deny paths are now resolved through symlinks before enforcement to avoid false positives when a deny path target is accessed via a symlink (search for "[Sandbox Linux] Resolve symlinked deny path")

See this entry in the whole of v2.1.208 →