feat: add google-vertex-openapi provider with ADC authentication by leehack · Pull Request #10303 · anomalyco/opencode

leehack · 2026-01-23T23:22:37Z

Summary

Adds a new google-vertex-openapi provider that enables using third-party models (like GLM-4.7) on Google Vertex AI through the OpenAPI-compatible endpoint.

Fixes #10304

Changes

Provider Implementation (src/provider/provider.ts):

Replaced gcloud CLI subprocess approach with Application Default Credentials (ADC) using google-auth-library
- No subprocess overhead (performance improvement)
- Automatic token refresh (handled by library)
- Supports multiple credential sources (gcloud ADC, service account, etc.)
Added getModel function for consistency with other providers

Test Infrastructure (test/provider/provider.test.ts):

Mocked google-auth-library for testing support
Configuration:
- Environment variables: GOOGLE_CLOUD_PROJECT, GCP_PROJECT, GCLOUD_PROJECT (project)
- Environment variables: GOOGLE_CLOUD_LOCATION, VERTEX_LOCATION (location)
- Config options: provider.options.project, provider.options.location
Authentication:
- Works with gcloud auth application-default login (easiest for development)
- Supports GOOGLE_APPLICATION_CREDENTIALS for service accounts (production)

Verification

Typecheck: Passed
Tests: All passing (pre-existing failures unaffected)
Manual testing: Can configure provider and make requests to Vertex AI OpenAPI endpoint

Usage

{
  "provider": {
    "google-vertex-openapi": {
      "name": "Google Vertex AI (OpenAPI)",
      "npm": "@ai-sdk/openai-compatible",
      "api": "https://aiplatform.googleapis.com/v1beta1",
      "options": {
        "project": "my-project-id",
        "location": "global"
      },
      "models": {
        "glm-4.7": {
          "name": "GLM-4.7",
          "tool_call": true,
          "reasoning": true,
          "limit": {"context": 128000, "output": 8192}
        }
      }
    }
  }
}

Setup

# Using gcloud ADC (recommended for development)
gcloud auth application-default login
export GOOGLE_CLOUD_PROJECT=my-project-id

# OR using service account (recommended for production)
export GOOGLE_APPLICATION_CREDENTIALS=~/.config/google/vertex-ai-service-account.json
export GOOGLE_CLOUD_PROJECT=my-project-id

github-actions · 2026-01-23T23:22:50Z

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

Open an issue describing the bug/feature (if one doesn't exist)
Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

github-actions · 2026-01-23T23:23:15Z

The following comment was made by an LLM, it may be inaccurate:

Potential Duplicate Found:

PR feat: add Google Vertex AI service account JSON authentication #6287: "feat: add Google Vertex AI service account JSON authentication"
- feat: add Google Vertex AI service account JSON authentication #6287
- This PR is also related to Google Vertex AI authentication. It may address similar functionality for service account authentication, which overlaps with the ADC authentication approach in PR feat: add google-vertex-openapi provider with ADC authentication #10303.

The other Google Vertex-related PRs (#9568, #6860, #5422, #5166) appear to be focused on different aspects (model resolution, token stats, cache configuration, naming conventions) rather than authentication implementation.

…port

NimaAra · 2026-01-29T22:36:13Z

Can we get this merged please?

bluet · 2026-01-30T08:25:36Z

Hey @leehack, great work on this! I was working on a similar solution (now closed #10742) and your approach of extending the existing google-vertex provider with protocol: "openapi" is cleaner than creating a separate provider.

I've also been coordinating with @rekram1-node on models.dev PR #716 for the model definitions. He mentioned consolidating all google-vertex models under a single provider, which aligns perfectly with your implementation here.

Happy to help test this PR if needed - I have a GCP project with GLM-4.7 access via Vertex AI Model Garden.

One small observation: The baseURL uses v1beta1 - just confirming this works with the OpenAPI-compatible endpoint? In my testing, I was using v1 for partner models. Let me know if you'd like me to verify.

leehack · 2026-01-30T10:25:11Z

Hey @leehack, great work on this! I was working on a similar solution (now closed #10742) and your approach of extending the existing google-vertex provider with protocol: "openapi" is cleaner than creating a separate provider.

I've also been coordinating with @rekram1-node on models.dev PR #716 for the model definitions. He mentioned consolidating all google-vertex models under a single provider, which aligns perfectly with your implementation here.

Happy to help test this PR if needed - I have a GCP project with GLM-4.7 access via Vertex AI Model Garden.

One small observation: The baseURL uses v1beta1 - just confirming this works with the OpenAPI-compatible endpoint? In my testing, I was using v1 for partner models. Let me know if you'd like me to verify.

Awesome!
Yes, I'm testing with the glm 4.7 model with the Vertex AI model Garden. I've only tested glm 4.7 with the v1beta1 endpoint. Feel free to test and let me know if you think we should better use the v1 endpoint.

bluet · 2026-02-02T18:19:49Z

Test Results: v1 vs v1beta1 Endpoints

I tested both API versions with GLM-4.7. Both work!

Results

Endpoint	Status
`/v1/.../openapi/chat/completions`	✅ Works
`/v1beta1/.../openapi/chat/completions`	✅ Works

Conclusion

Your current implementation using v1beta1 is fine - both versions work identically for the OpenAPI-compatible endpoint. No changes needed.

The correct model ID format is <publisher>/<model-id>, e.g., zai-org/glm-4.7-maas.

Documentation Reference

GLM 4.7 Model Card
Model ID: glm-4.7-maas
Publisher: zai-org
Region: global only

bluet · 2026-02-02T18:26:22Z

Follow-up: Recommendation to use `/v1/` instead of `/v1beta1/`

After researching Google's API versioning policy, I'd suggest using /v1/ instead of /v1beta1/ for better production stability.

Why `/v1/` is preferable:

Aspect	`/v1/` (Stable)	`/v1beta1/` (Beta)
SLA	✅ Covered	❌ No guarantees
Breaking Changes	❌ Not allowed	⚠️ Allowed after deprecation
Deprecation Notice	Min 1 year	~180 days (not guaranteed)
Production Use	✅ Recommended	⚠️ Test environments

Reference: Google's Official Policy

From AIP-181 and Google Cloud Launch Stages:

Beta: No SLAs or technical support obligations unless specified
Stable (v1): Fully-supported, covered by SLA, no breaking changes

Suggested Change

In the loader's baseURL construction:

- `https://${location}-aiplatform.googleapis.com/v1beta1/projects/...`
+ `https://${location}-aiplatform.googleapis.com/v1/projects/...`

Both work identically for the OpenAPI-compatible endpoint (I tested both), but /v1/ provides stronger stability guarantees for production use.

bluet

according to google vertex docs, /v1beta1/ url path is for beta testing purpose. better to use /v1/ for stability.

packages/opencode/src/provider/provider.ts

Co-authored-by: BlueT - Matthew Lien - 練喆明 <BlueT@BlueT.org>

leehack · 2026-02-03T13:42:07Z

according to google vertex docs, /v1beta1/ url path is for beta testing purpose. better to use /v1/ for stability.

Thanks @bluet for the test and suggestion. I updated the url as you suggested.

…ni in production while allowing custom proxies and localhost testing

leehack · 2026-02-03T15:15:05Z

Fixed the test failures and ensured compatibility with proxy servers.

NimaAra · 2026-02-05T20:25:55Z

Is this ever going to be merged?

github-actions bot added the needs:issue label Jan 23, 2026

github-actions bot removed the needs:issue label Jan 23, 2026

This was referenced Jan 26, 2026

feat(provider): add google-vertex-openai for Vertex AI partner models #10742

Closed

feat: added Google OAuth #11116

Closed

leehack added 3 commits January 29, 2026 09:51

fix(provider): add google-vertex-openapi provider for GLM-4 model sup…

f8d1fc3

…port

refactor: use ADC with google-auth-library instead of gcloud subprocess

c4e4b33

Consolidate the provider into google-vertex

5aba6e0

leehack force-pushed the fix/vertex-glm-openapi branch from 377d80e to 5aba6e0 Compare January 29, 2026 18:46

NimaAra mentioned this pull request Jan 29, 2026

Unable to access GLM 4.7 on Google Vertex AI #9909

Open

thdxr force-pushed the dev branch from cbab81f to 2d3c7a0 Compare January 30, 2026 04:49

opencode-agent bot force-pushed the dev branch from 00637c0 to 71e0ba2 Compare January 30, 2026 14:32

thdxr force-pushed the dev branch 4 times, most recently from f1ae801 to 08fa7f7 Compare January 30, 2026 14:37

bluet reviewed Feb 2, 2026

View reviewed changes

packages/opencode/src/provider/provider.ts Outdated Show resolved Hide resolved

packages/opencode/src/provider/provider.ts Outdated Show resolved Hide resolved

Apply suggestions from code review

7b520a0

Co-authored-by: BlueT - Matthew Lien - 練喆明 <BlueT@BlueT.org>

leehack and others added 2 commits February 3, 2026 08:43

Merge branch 'dev' into fix/vertex-glm-openapi

3d0268d

fix(provider): surgically sanitize Google SDK options to restore Gemi…

2bd9b14

…ni in production while allowing custom proxies and localhost testing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add google-vertex-openapi provider with ADC authentication#10303

feat: add google-vertex-openapi provider with ADC authentication#10303
leehack wants to merge 6 commits intoanomalyco:devfrom
leehack:fix/vertex-glm-openapi

leehack commented Jan 23, 2026 •

edited

Loading

Uh oh!

github-actions bot commented Jan 23, 2026

Uh oh!

github-actions bot commented Jan 23, 2026

Uh oh!

NimaAra commented Jan 29, 2026

Uh oh!

bluet commented Jan 30, 2026

Uh oh!

leehack commented Jan 30, 2026

Uh oh!

bluet commented Feb 2, 2026

Uh oh!

bluet commented Feb 2, 2026

Uh oh!

bluet left a comment

Uh oh!

Uh oh!

Uh oh!

leehack commented Feb 3, 2026

Uh oh!

leehack commented Feb 3, 2026

Uh oh!

NimaAra commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

leehack commented Jan 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Verification

Usage

Setup

Uh oh!

github-actions bot commented Jan 23, 2026

Uh oh!

github-actions bot commented Jan 23, 2026

Uh oh!

NimaAra commented Jan 29, 2026

Uh oh!

bluet commented Jan 30, 2026

Uh oh!

leehack commented Jan 30, 2026

Uh oh!

bluet commented Feb 2, 2026

Test Results: v1 vs v1beta1 Endpoints

Results

Conclusion

Documentation Reference

Uh oh!

bluet commented Feb 2, 2026

Follow-up: Recommendation to use /v1/ instead of /v1beta1/

Why /v1/ is preferable:

Reference: Google's Official Policy

Suggested Change

Uh oh!

bluet left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

leehack commented Feb 3, 2026

Uh oh!

leehack commented Feb 3, 2026

Uh oh!

NimaAra commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

leehack commented Jan 23, 2026 •

edited

Loading

Follow-up: Recommendation to use `/v1/` instead of `/v1beta1/`

Why `/v1/` is preferable: