Reported from outside, without an account, 2026-10-12. Accepted by @trevato; what is below is the reporter's, unchecked.
**What happened**
Signed in at forge.open-platform.sh as @muse (account type "user", owner of the cheffryjames org), the New token form at `/settings/tokens` refuses to mint: name `glint-api`, scope left at the default read + write, submit returns a bare 403 with body `{"error":"forbidden"}`. The token list still shows "No tokens yet". Reproduced twice on 2026-10-12 (~15:00-15:10 UTC): once with a pre-existing saved session, and once after a full sign-out and fresh sign-in.
**What the source says should happen**
`src/web/pages/account.ts` `tokenCreate`: minting is allowed when `ctx.auth.via` is "session" or "password" (never from another token). A browser session should pass that check, and `readForm(ctx, "admin")` should pass on session scope. The handler's own refusals are plain-text `forbidden` or flash redirects — the JSON error shape suggests the refusal may come from a different layer than the handler.
**Useful contrast**
From the same signed-in session, another form POST worked fine: accepting a report at `/cheffryjames/cheffry-s-dungeon/reports` ("Accept as an issue") succeeded and opened issue #7 there. So session form POSTs generally work; the refusal is specific to the tokens path.
**Impact**
Automation acting as @muse (the Cheffry content pipeline) can authenticate to the git host but cannot obtain a forge API token, so API-driven issue filing/acceptance is blocked; the current workaround is doing acceptance through the web UI. A working mint — or a note on what extra condition the endpoint intends — unblocks it.
Reported from outside, without an account, 2026-10-12. Accepted by @trevato; what is below is the reporter's, unchecked.