{"version":"2.1.282","anchor":"sandbox-failure-guidance-can-point-users-at-sandbox-to-chan","canonical_anchor":"sandbox-failure-guidance-can-point-users-at-sandbox-to-chan","heading":"Sandbox failure guidance can say \/sandbox changes the sandbox settings","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/sandbox-failure-guidance-can-point-users-at-sandbox-to-chan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Sandbox failure guidance can say \/sandbox changes the sandbox settings\n\nAfter a sandbox block, Claude may now say `\/sandbox` can change the sandbox settings rather than manage restrictions, depending on the environment\n\n**Unclear.** It is not known which condition chooses the \"change the sandbox settings\" wording.\n\n**What**\n\nThe sandbox is a restricted environment that shell commands run inside, limiting what they can reach. When a command fails because of it, Claude receives an instruction to briefly explain which restriction probably caused the failure and to mention the `\/sandbox` command. That instruction used to always end with \"use the `\/sandbox` command to manage restrictions.\" It is now built at runtime:\n\n- \"change the sandbox settings\" is the ending when a condition in the build holds, which applies only in some environments.\n\n- \"manage restrictions\" is the ending in every other case, as before.\n\n**Why**\n\nThis is a small wording change. In some setups, Claude may now point you at `\/sandbox` as the place to change sandbox settings rather than to manage restrictions.\n\n- Area: Sandbox\n- Names: `\/sandbox`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}