Repository navigation
[Bug]: Meta Muse OAuth Login | OAuth authentication failed. Check the OpenCodex account status and retry. #7112
Description
Client or integration
OpenCodex dashboard
Area
Authentication and account pool
Summary
When trying to add the account provider, Meta Muse Code (CLI), the oauth fails right after checking on the warning regarding the risk and continue with oauth with this error:
OAuth authentication failed. Check the OpenCodex account status and retry.
While this error happens, I am also served with this popup:
but even providing the password and doing always allow does not resolve any of this.
I found a PR that says this was resolved: #5877
However, I'm still encountering this on latest
Reproduction
- Go to Hub ocx web gui dashboard
- click on Providers
- Click on + Add Provider
- Search for 'meta'
- Choose "Meta Muse Code (CLI)" under ACCOUNTS option
- Click on "Log In"
- Accept the OAuth risk warning and click "Continue with OAuth"
- Error appears on the web dashboard:
Version
v.2.86.0
Operating system
macOS 27.0.1
Provider and model
meta/*
Logs or error output
let me know where i should grab logsScreenshots and supporting files
No response
Redacted configuration
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
Activity
[-]Meta Muse OAuth Login | OAuth authentication failed. Check the OpenCodex account status and retry.[/-][+][Bug] Meta Muse OAuth Login | OAuth authentication failed. Check the OpenCodex account status and retry.[/+][-][Bug] Meta Muse OAuth Login | OAuth authentication failed. Check the OpenCodex account status and retry.[/-][+][Bug]: Meta Muse OAuth Login | OAuth authentication failed. Check the OpenCodex account status and retry.[/+]Ingwannu commentedon Oct 16, 2026
Fixed on
devby #7145, commita738a5ee733a628815bdc094da99c88e34a00058.Muse Keychain import now allows a cancellable 120-second approval window, preserves fixed actionable diagnostics, and offers explicit existing-key paste recovery. It does not change Keychain ACLs or silently mint another grant.
I checked that the merge commit is an ancestor of current inspected
dev@4ae49360b7and that its implementation is present. Regression commands and results are recorded in #7145; I did not rerun those tests in this triage pass. The reporter’s actual Keychain state has not been exercised; if it still fails on a build containing this commit, report only the safe displayed reason/status, versions, whether the dashboard is remote, and prompt duration. Do not post Keychain contents or tokens.Closing as completed on the integration branch. This is not a claim that the fix has reached an npm/desktop release; please use a build containing the commit when checking the result.
nathanlisabio commentedon Oct 16, 2026
confirmed working, thx