A repo's settings can no longer point sandboxed search at an arbitrary ripgrep binary.
What's wrong with this entry?
The custom ripgrep command used for sandboxed searching is now read only from trusted settings sources: managed/policy settings, settings passed with --settings, and your user settings. A repository's .claude/settings.json can no longer point ripgrep at an arbitrary binary.
- Resolution walks those sources directly rather than reading the fully merged config.
- The setting's schema description was updated to state the restriction.
Only honored from user, managed/policy, or CLI (--settings) settings
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.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox