{"version":"2.1.232","anchor":"sandbox-ripgrep-is-ignored-when-set-by-project-settings","canonical_anchor":"sandbox-ripgrep-is-ignored-when-set-by-project-settings","heading":"sandbox.ripgrep is ignored when set by project settings","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/sandbox-ripgrep-is-ignored-when-set-by-project-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### `sandbox.ripgrep` is ignored when set by project settings\n\nA repo's settings can no longer point sandboxed search at an arbitrary ripgrep binary.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- Resolution walks those sources directly rather than reading the fully merged config.\n- The setting's schema description was updated to state the restriction.\n\n**Evidence**\n\n`Only honored from user, managed\/policy, or CLI (--settings) settings`\n\n- Area: Sandbox\n- Names: `sandbox.ripgrep`, `--settings`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}