Models through Vertex AI

[lyonsun]

Hi,

I am trying to set up using different models via Vertex AI

return {
  "yetone/avante.nvim",
  event = "VeryLazy",
  version = false, -- Never set this value to "*"! Never!
  opts = {
    provider = "vertex",
    providers = {
      vertex_claude = {
        model = "claude-sonnet-4@20250514",
      },
      vertex = {
        model = "gemini-2.5-pro-preview-05-06",
      },
    },
  },

-- truncated

}

Claude works fine, but with gemini I am continuously getting this error:

Error: {
  code = 400,
  details = { {
      ["@type"] = "type.googleapis.com/google.rpc.BadRequest",
      fieldViolations = { {
          description = 'Invalid JSON payload received. Unknown name "generationConfig": Proto field is not repeating, cannot start list.'
        } }
    } },
  message = 'Invalid JSON payload received. Unknown name "generationConfig": Proto field is not repeating, cannot start list.',
  status = "INVALID_ARGUMENT"
}

Does anyone know how to solve this?

[twmht]

i am facing the same issue, any update?

[lyonsun]

At last, I had to export these two environment variables in ~/.zshrc file:

export GOOGLE_CLOUD_PROJECT=<your-gcp-project-id>
export GOOGLE_CLOUD_LOCATION=<your-gcp-location>

after digging into the code for vertex provider:

avante.nvim/lua/avante/providers/vertex.lua

Lines 52 to 53 in a27b821

	local project_id = vim.fn.getenv("GOOGLE_CLOUD_PROJECT") or parse_cmd("cmd:gcloud config get-value project")
	local location = vim.fn.getenv("GOOGLE_CLOUD_LOCATION") -- same as gemini-cli

I don't quite understand why it didn't follow the same convention and use the same PROJECT_ID & LOCATION env vars as defined for claude through vertex_claude:

avante.nvim/lua/avante/providers/vertex_claude.lua

Lines 26 to 27 in a27b821

	local location = vim.fn.getenv("LOCATION")
	local project_id = vim.fn.getenv("PROJECT_ID")

It could be just that it is following the env var convention for gemini cli as mentioned in the comment in the above code snippet, I still think it would be nice if these two provider configurations are aligned with the name of the environment variables used though.

I could open a PR for such alignment, but not sure if this would result in breaking someone else's working system and cause some confusions.