{"version":"2.1.280","anchor":"bare-and-safe-mode-flag-descriptions-clarify-pluginhook","canonical_anchor":"bare-and-safe-mode-flag-descriptions-clarify-pluginhook","heading":"--bare and --safe-mode flag descriptions clarify plugin\/hook scope","tier":"notice","area":"CLI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/bare-and-safe-mode-flag-descriptions-clarify-pluginhook","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### --bare and --safe-mode flag descriptions clarify plugin\/hook scope\n\nHelp text for --bare and --safe-mode now clarifies they only affect plugins and settings-defined hooks, not built-in features\n\n**What**\n\nThe command-line help text for two startup flags was clarified:\n\n- `--bare` now explains that it only skips hooks (custom scripts that run automatically at certain points) defined in your settings or added by installed plugins; features built into Claude Code itself keep working.\n\n- `--safe-mode` now states that built-in tools and plugins both continue to work while safe mode disables other customizations.\n\n- The list of things `--safe-mode` disables now says \"installed plugins\" instead of just \"plugins\", to be more precise about scope.\n\n**Why**\n\nThese flags are meant for stripping down or troubleshooting your setup, and the clearer wording makes it easier to know exactly what still runs versus what gets turned off, without needing to test it by trial and error.\n\n- Area: CLI\n- Names: `--bare`, `--safe-mode`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}