{"version":"2.1.290","anchor":"safe-mode-is-now-evaluated-lazily-and-uses-the-same-check","canonical_anchor":"safe-mode-is-now-evaluated-lazily-and-uses-the-same-check","heading":"--safe-mode is now checked the same way as --restricted","tier":"notice","area":"Startup","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/safe-mode-is-now-evaluated-lazily-and-uses-the-same-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### `--safe-mode` is now checked the same way as `--restricted`\n\nThe `--safe-mode` flag now goes through the same check as `--restricted` and `--strict-mcp-config`, run when it is needed\n\n**Unclear.** What difference the new check makes in practice is not known.\n\n**What**\n\nA flag is an option you add when starting `claude`. Claude Code now checks the `--safe-mode` flag with the same routine it already uses for `--restricted` and `--strict-mcp-config`. The check now runs when it is needed rather than once up front.\n\n**Why**\n\nThis could change how `--safe-mode` is handled in some situations.\n\n- Area: Startup\n- Names: `--safe-mode`, `--restricted`, `--strict-mcp-config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}