anomalyco / anomalyco/opencode
OpenCode Go API Key Invalid Across All Models
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Description
OpenCode Go API key is invalid across all models.
I logged into the OpenCode website normally and copied a newly generated OpenCode Go API key directly from the official web page.
After connecting OpenCode Go with this key, every OpenCode Go model fails with the same error:
"API key is invalid"
I tested multiple different models and all of them return the same error, so this does not appear to be a model-specific issue.
I have also generated/copied a fresh API key from the OpenCode website, but the problem still persists.
Could you please check whether there is any problem with my OpenCode Go account, workspace, subscription, API access, or account status?
If possible, please perform a manual review of my account/API access.
Plugins
None
OpenCode version
1.18.21
Steps to reproduce
- Log in to the OpenCode website.
- Copy a newly generated OpenCode Go API key.
- Open OpenCode.
- Run /connect.
- Select OpenCode Go.
- Paste the newly generated API key.
- Select any OpenCode Go model.
- Send a normal prompt.
- The request fails with: "API key is invalid".
- Switching to other OpenCode Go models results in the same error.
Screenshot and/or share link
Operating System
windows11
Terminal
windows
Contributor guide
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.
Research direction
No source file or test is named in the report. Start by reproducing the /connect flow with OpenCode 1.18.21 on Windows 11 across the reported OpenCode Go models; done means determining whether the same invalid-key response is reproducible and whether it is an account or API-access problem rather than a model-specific failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100