Signing in can request an extra permission for plugin search, though search itself remains policy-gated.
A user:plugins scope expansion path exists, but the plugin search route still requires the allow_plugin_skill_search policy.
What's wrong with this entry?
A 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.
- The claude.ai project scope list gained
user:plugins. - The expansion logs under
[plugins-scope]and reportsplugins_scope_expansionoutcomes includingsave_failedandexpand_failed, the latter with detail "refresh succeeded but user:plugins not granted". - It bails out for custom OAuth clients, non-claude.ai providers, and when nonessential traffic is disabled.
- The search route remains gated on the
allow_plugin_skill_searchpolicy.
refresh succeeded but user:plugins not granted
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.