- 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
RipgrepUsageErrorrather 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
apiKeyHelperscript 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")
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed apiKeyHelper script failures being hidden behind a generic 401 after ~10 silent retries; the script's own error is now shown within 3…