What happened
After configuring the google-gemini provider, the model picker offers exactly two models:
gemini-3-1-pro-preview
gemini-3-6-flash
In Settings, the provider's "Available to add" list is empty, so there is no way to reach any other Gemini model from the UI.
Why
Three things combine:
-
The shipped catalog has only two Gemini entries. packages/trueforge/catalog/model-catalog.yaml:128 lists 2 models for google-gemini, where comparable providers get more — openai 5, anthropic 6, together 7.
-
The UI can only add models already in the catalog. ModelSettings.tsx:312 builds the "Available to add" list as catalogModels.filter(...), so for Gemini it is empty once both catalog models are configured.
-
The configure form has no model field. ConfigureModelProviderForm.tsx collects only API key and base URL for well-known providers. Only the custom type has a model editor (CustomModelProviderForm.tsx).
This is a catalog/UI limit, not an API limit
The API already accepts any model ID: ConfiguredModelSchema (packages/trueforge/src/schemas/modelProvider.ts:32) takes model_id as a free-form string with no allowlist, and GET /models flattens whatever the stored manifest holds. The backend would serve any Gemini model — the catalog just does not list them.
Workarounds
- Point
MODEL_CATALOG_PATH at a custom YAML to replace the shipped catalog (packages/trueforge/src/catalog/ModelCatalog.ts:23).
- Or define a
custom provider, which does expose a model editor.
Both mean giving up the built-in Gemini provider entry.
Suggested fix
Either would resolve this:
- Expand the
google-gemini catalog entries to cover the current lineup, bringing it in line with openai/anthropic.
- Or allow well-known providers to accept a free-text
model_id in the UI, as custom already does. This also stops the catalog needing an update every time a provider ships a new model.
Environment
- Commit
1ec19f0f (main), server 0.2.0-rc.2
- Running locally via
docker compose up --build
What happened
After configuring the
google-geminiprovider, the model picker offers exactly two models:gemini-3-1-pro-previewgemini-3-6-flashIn Settings, the provider's "Available to add" list is empty, so there is no way to reach any other Gemini model from the UI.
Why
Three things combine:
The shipped catalog has only two Gemini entries.
packages/trueforge/catalog/model-catalog.yaml:128lists 2 models forgoogle-gemini, where comparable providers get more —openai5,anthropic6,together7.The UI can only add models already in the catalog.
ModelSettings.tsx:312builds the "Available to add" list ascatalogModels.filter(...), so for Gemini it is empty once both catalog models are configured.The configure form has no model field.
ConfigureModelProviderForm.tsxcollects only API key and base URL for well-known providers. Only thecustomtype has a model editor (CustomModelProviderForm.tsx).This is a catalog/UI limit, not an API limit
The API already accepts any model ID:
ConfiguredModelSchema(packages/trueforge/src/schemas/modelProvider.ts:32) takesmodel_idas a free-form string with no allowlist, andGET /modelsflattens whatever the stored manifest holds. The backend would serve any Gemini model — the catalog just does not list them.Workarounds
MODEL_CATALOG_PATHat a custom YAML to replace the shipped catalog (packages/trueforge/src/catalog/ModelCatalog.ts:23).customprovider, which does expose a model editor.Both mean giving up the built-in Gemini provider entry.
Suggested fix
Either would resolve this:
google-geminicatalog entries to cover the current lineup, bringing it in line withopenai/anthropic.model_idin the UI, ascustomalready does. This also stops the catalog needing an update every time a provider ships a new model.Environment
1ec19f0f(main), server0.2.0-rc.2docker compose up --build