[Bug]: Meta Muse OAuth Login | OAuth authentication failed. Check the OpenCodex account status and retry.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- authentication
Research direction
Start by reproducing the flow in the dashboard: Providers, then Add Provider, then Meta Muse Code (CLI) under Accounts, then Log In. Search the codebase for the message "OAuth authentication failed" to find where it is raised, and check the server-side logs, which the reporter did not provide. Also check whether the fix referenced in issue 5877 regressed. Done means the Meta Muse login completes without that error.
Written by the indexing model from the issue text.
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: https://github.com/lidge-jun/opencodex/issues/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 logs
Screenshots 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.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 7h 40m
- Merged PRs (30d)
- 668
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lidge-jun/opencodex
-
account-pool bug provider
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
account-pool enhancement needs-design proxy
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lidge-jun/opencodex#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
account-pool bug tools
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
bug(vertex): API-key requests ignore project/location and fail for Gemini 4 ArgonPossibly taken A pull request linked to this issue is open or already merged. Openbug provider
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
provider provider-compatibility
Difficulty 4/5 3-5 days Newbie friendliness 45/100
lidge-jun/opencodex#7255 · 2 comments ·
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
umami-software/umami#4637 ·
Maintainers usually reply within 3 days
-
Hotkeys fire when pressed with the Ctrl key, so browser shortcuts also trigger player actionsPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
muxinc/media-chrome#1332 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
polarsource/polar#15580 ·
Maintainers usually reply within 1 day
-
accepted bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
pingdotgg/t3code#20931 · 1 comment ·
Maintainers usually reply within 1 day
-
bug/1-unconfirmed kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day