Gemini catalogs omit gemini-4-argon and gemini-3.8-flash

Open Beginner friendly
#3,524 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@jayunit100 is already working on this.

Since Nov 4, 2026.

  • #3525 by @jayunit100 — open
  • #3536 by @lakshyab20 — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
ai

Research direction

Read go/core/internal/service/model/discovery.go and locate the Gemini and GeminiVertexAI catalog entries. Add gemini-4-argon and gemini-3.8-flash to both with FunctionCalling: true, keeping existing rows. Add or run a local catalog test asserting both providers contain both IDs; a live call requires a Google key.

Written by the indexing model from the issue text.

Description

Omitting gemini-4-argon and gemini-3.8-flash from the Gemini and Vertex Gemini catalogs reduces the ability to select a current Gemini model.

Both pickers in go/core/internal/service/model/discovery.go stop at early Gemini 3 names and still suggest the Gemini 2.5 family. Google's Gemini API model list publishes gemini-4-argon and gemini-3.8-flash, and both support function calling. Source: https://ai.google.dev/gemini-api/docs/models

Suggested change: add those two IDs to Gemini and GeminiVertexAI, with FunctionCalling: true. Leave the existing 2.5 and early Gemini 3 rows in place. This is separate from the Bedrock Grok catalog in #3514.

A local catalog test can assert both providers contain the two IDs. A live Gemini call still needs a Google key.

Dominant language
Go
Stars
4.1k
Forks
871
Avg merge
1d 8h
Merged PRs (30d)
183

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from kagent-dev/kagent

All issues in kagent-dev/kagent

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.