{"version":"2.1.267","anchor":"builtin-plugin-registration-now-runs-unconditionally-plus-a","canonical_anchor":"builtin-plugin-registration-now-runs-unconditionally-plus-a","heading":"Builtin plugin registration now runs unconditionally, plus again for non-local-agent entrypoints","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/builtin-plugin-registration-now-runs-unconditionally-plus-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Builtin plugin registration now runs unconditionally, plus again for non-local-agent entrypoints\n\nBuilt-in plugins now register unconditionally at startup, in addition to existing conditional registration\n\n**Unclear.** What practical difference this makes for a user, beyond registration now happening unconditionally as well as conditionally, is not stated.\n\n**What**\n\nClaude Code's built-in plugins are now registered once unconditionally as part of its startup check, in addition to the existing registration that happens when `CLAUDE_CODE_ENTRYPOINT` is not set to `local-agent`.\n\n**Why**\n\nThis is internal startup plumbing. The finding doesn't specify a user-visible effect, but it suggests built-in plugins are now registered more consistently regardless of entrypoint.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}