Unable to access GLM 4.7 on Google Vertex AI

[NimaAra]

Description

I have the following provider set in my config which allows me to successfully access gemini models:

...
"provider": {
    "google-vertex": {
      "options": {
        "location": "global",
        "project": "my-project-id"
      },
      "models": {
        "zai-org/glm-4.7-maas": {
          "name": "GLM 4.7 (Vertex AI)"
        },
        "gemini-3-pro-preview": {
          "name": "Gemini 3 Pro (Vertex AI)",
          "options": {
            "temperature": 1.0,
            "generationConfig": {
              "thinkingConfig": {
                "thinkingLevel": "high"
              }
            }
          }
        }
...

However, I am not able to access GLM 4.7 and I get the "Not Found" toast in opencode.

I have validated the GLM 4.7 access in the GCP shell by executing:

curl \
  -X POST \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  -H "Content-Type: application/json" https://${ENDPOINT}/v1/projects/${PROJECT_ID}/locations/${REGION}/endpoints/openapi/chat/completions \
  -d '{"model":"zai-org/glm-4.7-maas", "stream":true, "messages":[{"role": "user", "content": "Summer travel plan to Paris"}]}'

What am I missing?

Plugins

none

OpenCode version

1.1.30

Steps to reproduce

1. Add provider (as provided)
2. Choose GLM 4.7 as the model
3. Send prompt

Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal

[github-actions]

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

• Google Vertex Not Found #3940: Google Vertex Not Found - Similar 'Not Found' error when using Google Vertex provider
• [BUG]: Google Auth Gemini 3 models return 404 "Requested entity was not found" error #6454: [BUG]: Google Auth Gemini 3 models return 404 "Requested entity was not found" error - Related to Vertex provider configuration issues
• opencode not picking up Google Vertex AI service account json #6280: opencode not picking up Google Vertex AI service account json - Related to Vertex provider setup issues
• Bug: Shared state between google-vertex and google-vertex-anthropic providers causes auth conflict #7514: Bug: Shared state between google-vertex and google-vertex-anthropic providers causes auth conflict - May relate to provider configuration issues
• How to configure google vertex with desktop app? #5711: How to configure google vertex with desktop app? - Related configuration troubleshooting

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

[NimaAra]

I have also tried setting the following env vars as per doc to no avail:

GOOGLE_CLOUD_PROJECT=my-project-id
VERTEX_LOCATION=global

[foontinz]

I think its related to the issue that vercel's ai sdk does not support custom publishers on vertex. Here is my PR to them vercel/ai#12015 .

[NimaAra]

This is great, thank you for submitting the PR. Now it's a waiting game.

[NimaAra]

Any update on this please?

[NimaAra]

Looks like #10303 addresses this issue.