-
Notifications
You must be signed in to change notification settings - Fork 9.3k
"Model metadata for gpt-oss:20b not found" with ollama #14757
Description
What version of Codex CLI is running?
0.114.0
What subscription do you have?
None - I am using an Ollama provider
Which model were you using?
gpt-oss:20b
What platform is your computer?
Linux 6.18.17 x86_64 unknown (NixOS)
What terminal emulator and version are you using (if applicable)?
wezterm
What issue are you seeing?
When I try to interact with the Codex CLI, I see the warning message in the attached screenshot and quoted below. This was not a problem before using the 0.114.0 version of codex cli.
⚠ Model metadata for
gpt-oss:20bnot found. Defaulting to fallback metadata; this
can degrade performance and cause issues.
As the message notes, performance is degraded severely and it appears that when I try to interact with the agent after the message, that features like "plan mode" are not usable and the agent completely loses track of its goal.
Relevant config:
model = "gpt-oss:20b"
model_provider = "ollama"
[model_providers.ollama]
baseURL = "http://localhost:11434/v1"
name = "Ollama"
I have not found a workaround. I have found seemingly related issues (see list below), but none of the workarounds discussed there are working for me.
- Model metadata for
gpt-5-codexnot found. Defaulting to fallback metadata; this can degrade performance and cause issues #12100 (I have tried feeding a relevantmodel_catalog_jsonpath to the config) - ollama launch codex - ⚠ Model metadata for
gpt-oss:20bnot found. Defaulting to fallback metadata; this can degrade performance and cause issues. ollama/ollama#14752 (duplicate issue on the ollama repo) - find_model_by_namespaced_suffix rejects hyphens in namespace, breaking custom provider slugs like llm-gateway/gpt-5.4 #14276 (I have tried using a model with an un-hyphenated name)
What steps can reproduce the bug?
Open codex cli v0.114.0 configured to use gpt-oss:20b with ollama 0.17.7. Chat with the agent and see the message.
What is the expected behavior?
No warning message, agent stays on task.
Additional information
No response