{"version":"2.1.282","anchor":"sandboxexcludedcommands-setting-now-documented-in-the-schem","canonical_anchor":"sandboxexcludedcommands-setting-now-documented-in-the-schem","heading":"Settings schema now describes sandbox.excludedCommands","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/sandboxexcludedcommands-setting-now-documented-in-the-schem","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Settings schema now describes sandbox.excludedCommands\n\nThe settings schema now explains that sandbox.excludedCommands is a convenience, not a security boundary, and that its patterns merge across sources\n\n**What**\n\nThe settings schema (the description of valid settings that editors use for hints and checking) now explains `sandbox.excludedCommands`. Before, the entry had no description. It now says:\n\n- the entries are command patterns, written like Bash permission rules, that always run outside the sandbox\n\n- it is a convenience, not a security boundary, and excluded commands still go through the permission flow\n\n- patterns from different settings sources are merged together\n\n**Why**\n\nEditors that read the schema now show this explanation, making clear that excluding a command from the sandbox does not skip permission prompts.\n\n- Area: Settings\n- Names: `sandbox.excludedCommands`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}