anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Bug: Shared state between google-vertex and google-vertex-anthropic providers causes auth conflict #4547

New Issue
Closed
opened 2026-02-16 17:44:33 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 17:44:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @Skeptomenos on GitHub (Jan 9, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

When using the same API key for both google-vertex and google-vertex-anthropic providers, only the last authenticated provider works. The other provider fails, even though both are correctly configured in auth.json.

Steps to Reproduce

  1. Run opencode auth login and authenticate google-vertex with a Vertex AI API key
  2. Run opencode auth login and authenticate google-vertex-anthropic with the same API key
  3. Try to use a Gemini model via google-vertex → Fails
  4. Claude models via google-vertex-anthropic → Works

If you reverse the order (authenticate google-vertex-anthropic first, then google-vertex):

  • Gemini via google-vertex → Works
  • Claude via google-vertex-anthropic → Fails with error like: 
    Publisher Model `projects/<project>/locations/global/publishers/google/models/claude-opus-4-5@20251101` not found.

Expected Behavior

Both providers should work independently. The same API key should be usable for both Gemini and Claude models on Vertex AI, as they are separate provider configurations.

Actual Behavior

Whichever provider is authenticated last wins. The other provider breaks, suggesting shared global state between the two providers.

Environment

  • auth.json correctly stores separate entries for each provider:
{
  "google-vertex-anthropic": {
    "type": "api",
    "key": "AIzaSy..."
  },
  "google-vertex": {
    "type": "api",
    "key": "AIzaSy..."
  }
}

Analysis

The issue appears to be that OpenCode (or the underlying @ai-sdk/google-vertex SDK) initializes a shared singleton client when an API key is provided. The last authentication overwrites this shared state, breaking the previously authenticated provider.

Each provider should have its own isolated SDK instance to prevent this conflict.

Workaround

Currently, users must either:

  1. Only use one of the two built-in Vertex providers
  2. Use a custom provider definition for one of them (e.g., define its-vertex-anthropic separately)
  3. Use ADC (Application Default Credentials) instead of API keys

Additional Context

  • The same API key works for both Gemini and Claude when tested individually
  • The issue is specifically about shared runtime state, not the stored credentials
Originally created by @Skeptomenos on GitHub (Jan 9, 2026). Originally assigned to: @rekram1-node on GitHub. ## Description When using the same API key for both `google-vertex` and `google-vertex-anthropic` providers, only the **last authenticated provider works**. The other provider fails, even though both are correctly configured in `auth.json`. ## Steps to Reproduce 1. Run `opencode auth login` and authenticate `google-vertex` with a Vertex AI API key 2. Run `opencode auth login` and authenticate `google-vertex-anthropic` with the **same** API key 3. Try to use a Gemini model via `google-vertex` → **Fails** 4. Claude models via `google-vertex-anthropic` → Works If you reverse the order (authenticate `google-vertex-anthropic` first, then `google-vertex`): - Gemini via `google-vertex` → Works - Claude via `google-vertex-anthropic` → **Fails** with error like: ``` Publisher Model `projects/<project>/locations/global/publishers/google/models/claude-opus-4-5@20251101` not found. ``` ## Expected Behavior Both providers should work independently. The same API key should be usable for both Gemini and Claude models on Vertex AI, as they are separate provider configurations. ## Actual Behavior Whichever provider is authenticated **last** wins. The other provider breaks, suggesting shared global state between the two providers. ## Environment - `auth.json` correctly stores separate entries for each provider: ```json { "google-vertex-anthropic": { "type": "api", "key": "AIzaSy..." }, "google-vertex": { "type": "api", "key": "AIzaSy..." } } ``` ## Analysis The issue appears to be that OpenCode (or the underlying `@ai-sdk/google-vertex` SDK) initializes a **shared singleton client** when an API key is provided. The last authentication overwrites this shared state, breaking the previously authenticated provider. Each provider should have its own isolated SDK instance to prevent this conflict. ## Workaround Currently, users must either: 1. Only use one of the two built-in Vertex providers 2. Use a custom provider definition for one of them (e.g., define `its-vertex-anthropic` separately) 3. Use ADC (Application Default Credentials) instead of API keys ## Additional Context - The same API key works for both Gemini and Claude when tested individually - The issue is specifically about shared runtime state, not the stored credentials
yindo closed this issue 2026-02-16 17:44:33 -05:00
yindo commented 2026-02-16 17:44:33 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 9, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #6261: bug: multiple plugins registering auth for the same provider silently overwrite each other (similar shared state/auth conflict issue)
  • #6217: Have multiple instances of the same provider (related feature request for multiple provider instances)
  • #5391: [FEATURE]: multiple auth profiles per provider (related feature discussion)
  • #5748: Proposal: Provider Auth v2 (broader auth system redesign that may address this issue)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 9, 2026): This issue might be a duplicate of existing issues. Please check: - #6261: bug: multiple plugins registering auth for the same provider silently overwrite each other (similar shared state/auth conflict issue) - #6217: Have multiple instances of the same provider (related feature request for multiple provider instances) - #5391: [FEATURE]: multiple auth profiles per provider (related feature discussion) - #5748: Proposal: Provider Auth v2 (broader auth system redesign that may address this issue) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:44:33 -05:00
Author
Owner
Copy Link
Copy Source

@aKardasz commented on GitHub (Jan 12, 2026):

I am running into this as well which is a bummer because I can't let opencode do its thing between multiple models like opus for most then Gemini for UI etc. this impacts using Google credentials auth for me as well.

@aKardasz commented on GitHub (Jan 12, 2026): I am running into this as well which is a bummer because I can't let opencode do its thing between multiple models like opus for most then Gemini for UI etc. this impacts using Google credentials auth for me as well.
yindo commented 2026-02-16 17:44:33 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Jan 12, 2026):

hmm okay ill look into this

@rekram1-node commented on GitHub (Jan 12, 2026): hmm okay ill look into this
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4547
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?