Repository navigation
v1.5.3 — Token issuance UX fix
No need to manually upload this one — your v1.5.2 install will detect the update automatically (the GitHub auto-updater shipped in 1.5.2). Just click "Update Now" on the Plugins page.
Fix
The "Bind to WP user (optional)" field defaulted to 0, which means "anonymous user with no capabilities". Tokens issued with this default passed the MCP scope check but failed every WordPress capability check, making admin-scope tools (plugins, users, settings) appear broken even when correctly scoped.
Now
- The field is now a dropdown populated with suggested users (Administrator / Editor / Author roles), with the current admin pre-selected.
- An "Other — enter ID manually" option reveals the number input for edge cases or large user bases.
- "0 — anonymous" still exists as the last option (rendered in red), with a live warning banner when picked: "This token will have no WordPress user. Every capability-gated tool will fail."
- Label renamed from "Bind to WP user (optional)" → "Run as WP user" with clearer help text.
Existing tokens are unaffected.