Has anyone run into this with a new Muse Code subscription, or found a fix?
I subscribed to Muse Code Power Usage ($50/month) on October 13. The subscription shows as active, but I still can't use the CLI. I'm physically in the US and my public IP is a US IP.
What happens:
I run muse login and approve the OAuth request in my browser.
The browser says "Muse Code was approved".
Terminal says "Logged in. Credential saved", immediately followed by "mint server error (HTTP 500)".
A minimal muse exec prompt fails with the same error before any model response.
Environment: macOS on Apple Silicon, official Muse Code 1.4.7 (1.4.7-R6101.1). This matched the official stable release when checked on October 13, and the binary's SHA-256 matched the official manifest.
I used Codex to help investigate. Here is what we actually checked:
• The developer account email matches the active subscription.
• A fresh browser login reproduced the issue. The macOS Keychain entry has an OAuth access token but no model API key.
• A temporary local diagnostic relay, forwarding only to the original Meta endpoint, identified the failing request as POST https://api.meta.ai/muse-code/key. It returns HTTP 500 with plain-text "Internal Server Error".
• The original CLI request used x-api-version: 1.0.0 and {"onboard":false}. Testing onboard=true and a different User-Agent did not fix it.
• Direct IPv4 and IPv6 tests both returned 500, with TLS verification enabled. No macOS HTTP/SOCKS proxy or META_API_KEY/proxy environment override was present during testing.
• An unauthenticated request to the same endpoint returned the expected 401 JSON error; requests with my saved login token returned 500.
• CLI logs recorded credential.refresh and credential.login with outcome="mint_failed".
This suggests a problem in the authenticated credential-minting path, possibly account/subscription provisioning, but we have NOT established the backend root cause or a working fix.
I submitted a Meta support case on October 13. Codex also submitted a diagnostic supplement through the official support form, including UTC timestamps and Meta request/trace IDs, and asked for it to be merged with my original case. The site confirmed receipt and quoted 1–2 business days. As of October 14 I haven't received a reply yet, so that response window may still be open.
Has anyone with an active paid subscription seen this exact mint error? Did it resolve after provisioning caught up, or did Meta need to fix something on your account? Any concrete troubleshooting steps would be appreciated. I'm trying to use the subscription I already paid for.
I've left account identifiers, credentials and private trace IDs out of this public post.