{"version":"2.1.285","anchor":"sandbox-and-gateway-smaller-changes","canonical_anchor":"sandbox-and-gateway-smaller-changes","heading":"Small changes to sandbox status, the gateway and claude daemon","tier":"notice","area":"Sandbox","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/sandbox-and-gateway-smaller-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Small changes to sandbox status, the gateway and `claude daemon`\n\nSandbox status accounts for another fallback case, the gateway rejects some keys, and `claude daemon` gains a --[no-]chrome option\n\n**Unclear.** It is not clear which keys the gateway rejects.\n\n**What**\n\n- Sandbox status now takes into account one more case where commands can fall back to running outside the sandbox. The sandbox is a restricted environment that shell commands run inside.\n\n- The gateway now rejects certain keys with a message saying they are \"not supported through the gateway\".\n\n- `claude daemon` help lists a `--[no-]chrome` option to turn Claude in Chrome on or off for sessions it starts.\n\n**Why**\n\nThese are minor behaviour changes.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}