Skip to content

NO API KEY #50885

Closed
Closed

Description

@ToniMCano

Description

I subscribed to OpenCode Go today.
My Go subscription is active, but the console does not show any personal API key or any option to create/copy one.
/connect → OpenCode Go requires an API key.
The Keys page only allows creating Service Accounts, and those do not generate the Go API key described in the documentation.
I'm using OpenCode v2.0.15 on Windows 11.
How can I obtain the API key associated with my Go subscription?

Plugins

No response

OpenCode version

V.2.0.15

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

No response

Activity

  1. FriendChicken commented on Sep 26, 2026

    @FriendChicken

    I have the same issue... Did you solve it? Or is it a bug that persists?

  2. Voolan commented on Sep 27, 2026

    @Voolan

    @ToniMCano @ndarilek You can create an API key like this:

    On the main page (https://opencode.ai/console), go to the Keys tab → create a Service Account (if you don't already have one) → click on the Service Account you created → then click Add API Key.

    Also, if you get an error when using Chinese AI models, go to Settings → Privacy in the same console (https://opencode.ai/console) and set the region to Global.

    I also recommend enabling “Allow paid endpoints that train on request data” if you plan to use models such as Muse Spark Contribution.

  3. leeashine commented on Sep 28, 2026

    @leeashine

    I'm having the same issue.

  4. ryanmeowy commented on Sep 29, 2026

    @ryanmeowy

    @Voolan
    Thanks. I’ve already tried this exact flow.
    I created a Service Account and added an API key under it, but when I use that key with Claude Code, I get:
    402 Upstream request failed: Insufficient account funds
    My Go subscription is active, and Go models work normally inside OpenCode CLI, e.g. opencode-go/minimax-m3.
    So it looks like the Service Account API key is using the Console pay-as-you-go balance rather than the Go subscription quota.
    Is there a separate Go API key, or a way to make the Service Account key use my Go subscription entitlement?

  5. vaprdev commented on Oct 1, 2026

    @vaprdev
    Contributor

    hey, this is a bit confusing and we can improve it for sure, but you should be able to /connect inside v2 and then choose opencode. make sure you select the workspace with go on the auth screen in the browser. then models (including go ones) should load for you.

    it's important that you select a go model if you want to use your plan: any other model (besides free and byok) will default to trying to use your org credit. sometimes there'll be multiple instances of a model, so make sure you select the go one.

    you should also be able to use an api key for that workspace as well:

    • create a service account
    • /connect -> opencode go
    • insert that api key

    all api keys are under service accounts, so there's no separate "go" one to create

  6. buloxdev commented on Oct 1, 2026

    @buloxdev

    I'm still having the same issue, there is not a way to connect my Go Sub

  7. rocky-zh commented on Oct 2, 2026

    @rocky-zh

    I'm still having the same issue, there is not a way to connect my Go Sub

  8. bkruse commented on Oct 3, 2026

    @bkruse

    I ran into this same issue and I was able to fix it. I suspect this will happen to many customers that have been using the free OpenCode models and then purchased an OpenCode Go subscription.

    I followed the v2 instructions on how to connect and then I used /models to select a model that seemed to be part the OpenCode Go plan but did not have OpenCode Go in its name. I used /models again to switch to models with OpenCode Go in the name and the problem resolved.

    Like @vaprdev mentions, this is super confusing and easy to miss and I'd highly recommend fixing this because I almost canceled my brand new subscription and demanded a refund. Based on my issues search, this seems to be a common problem new customers encounter.

  9. aaronksaunders commented on Oct 3, 2026

    @aaronksaunders
  10. itonoz commented on Oct 17, 2026

    @itonoz

    Same problem, can't create API keys, there is no Keys tab in the console.

  11. marked Invalid API Key #50991 as a duplicate of this issue on Oct 20, 2026
  12. marked Invalid API key #44433 as a duplicate of this issue on Oct 20, 2026
  13. marked missing api key #44288 as a duplicate of this issue on Oct 20, 2026
  14. marked api key missing #51388 as a duplicate of this issue on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions