{"version":"2.1.223","anchor":"plugin-and-skill-search-requests-a-new-user-plugins-oauth-sc","canonical_anchor":"plugin-and-skill-search-requests-a-new-user-plugins-oauth-sc","heading":"Plugin and skill search requests a new user:plugins OAuth scope","tier":"soon","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/plugin-and-skill-search-requests-a-new-user-plugins-oauth-sc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Plugin and skill search requests a new `user:plugins` OAuth scope\n\nSigning in can request an extra permission for plugin search, though search itself remains policy-gated.\n\n**What**\n\nA scope-expansion path can refresh the claude.ai token to obtain a new `user:plugins` scope before the plugin search route is called, but search itself is still behind an existing policy gate.\n\n**Details**\n\n- The claude.ai project scope list gained `user:plugins`.\n- The expansion logs under `[plugins-scope]` and reports `plugins_scope_expansion` outcomes including `save_failed` and `expand_failed`, the latter with detail \"refresh succeeded but user:plugins not granted\".\n- It bails out for custom OAuth clients, non-claude.ai providers, and when nonessential traffic is disabled.\n- The search route remains gated on the `allow_plugin_skill_search` policy.\n\n**Evidence**\n\n`refresh succeeded but user:plugins not granted`\n\n- Area: Plugins\n- Names: `allow_plugin_skill_search`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}