{"version":"2.1.232","anchor":"sandbox-binary-paths-in-project-settings-are-surfaced-at-the","canonical_anchor":"sandbox-binary-paths-in-project-settings-are-surfaced-at-the","heading":"Sandbox binary paths in project settings are surfaced at the trust prompt","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/sandbox-binary-paths-in-project-settings-are-surfaced-at-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Sandbox binary paths in project settings are surfaced at the trust prompt\n\nSandbox binary paths set by a project now show up in the folder trust prompt before you accept.\n\n**What**\n\nWhen a project's settings set `sandbox.bwrapPath`, `sandbox.ripgrep` or `sandbox.socatPath`, those keys now appear in the summary shown before you trust the folder, and their presence disqualifies the settings file from the shortcut that auto-trusts files containing only environment variables.\n\n**Details**\n\n- The three keys are reported by name, for example `sandbox.ripgrep`.\n- A separate check gates the quiet-trust path, so such a file always requires an explicit decision.\n\n**Evidence**\n\n`\"bwrapPath\", \"ripgrep\", \"socatPath\"`\n\n- Area: Sandbox\n- Names: `sandbox.bwrapPath`, `sandbox.ripgrep`, `sandbox.socatPath`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}