{"version":"2.1.280","anchor":"safe-mode-banner-clarifies-that-built-in-plugins-keep-workin","canonical_anchor":"safe-mode-banner-clarifies-that-built-in-plugins-keep-workin","heading":"Safe-mode banner clarifies that built-in plugins keep working","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/safe-mode-banner-clarifies-that-built-in-plugins-keep-workin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Safe-mode banner clarifies that built-in plugins keep working\n\nSafe-mode messages now clarify that built-in plugins keep working while installed plugins are disabled\n\n**What**\n\nThe warning text shown in the plugin-settings screen when safe mode is on has been rewritten. It now says more clearly that:\n\n- Only *installed* plugins are disabled for the session\n\n- Changes made to installed plugins while in safe mode still save, but won't take effect until safe mode is turned off\n\n- Built-in plugins (the ones that ship with Claude Code) are unaffected and keep working\n\nThe related message shown when plugin hooks (custom scripts plugins can run at certain points) are skipped during safe mode was reworded the same way, confirming that built-in plugins continue to load and run even in safe mode.\n\n**Why**\n\nSafe mode is meant to temporarily disable plugins you've installed, not the built-in functionality Claude Code ships with. The earlier wording could leave that ambiguous; the new text makes clear which plugins are actually turned off and what happens to unsaved or pending changes, so there's less confusion about what still works while safe mode is active.\n\n- Area: Elsewhere\n- Names: `--safe-mode`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}