{"version":"2.1.273","anchor":"new-oauth-scope-userplugins-gated-by-plugins-scope-regist","canonical_anchor":"new-oauth-scope-userplugins-gated-by-plugins-scope-regist","heading":"New OAuth scope user:plugins gated by PLUGINS_SCOPE_REGISTERED","tier":"soon","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-oauth-scope-userplugins-gated-by-plugins-scope-regist","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### New OAuth scope `user:plugins` gated by PLUGINS_SCOPE_REGISTERED\n\nA new OAuth scope, user:plugins, is requested for accounts with plugin access registered\n\n**What**\n\nWhen Claude Code logs in, it can now request an additional permission scope called `user:plugins` as part of OAuth (the login flow that grants Claude Code permission to act on your behalf). This scope is only added when a setting called `PLUGINS_SCOPE_REGISTERED` is turned on for the login configuration being used. The default and production login configurations now have this turned on, while configurations that use a custom client ID or an environment-variable override for the client ID do not.\n\n**Why**\n\nThis lets most users' logins pick up permission for a plugins-related feature automatically, while custom or overridden login setups are left unaffected until they're updated too.\n\n- Area: Auth\n- Names: `user:plugins`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}