You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've confirmed the base_url in config.toml is not used for oss. As a workaround for now, you can go with the env variable "CODEX_OSS_BASE_URL" and it works without any issues: CODEX_OSS_BASE_URL="http://{your-host}/v1" codex
I think it is VLLM. In VLLM's guide for deploying GPT OSS it shows that Response API with Streaming does not support function calling. So if Codex, is calling that api path, then I think that would be the problem
Activity
seratch commentedon Aug 14, 2025
I've confirmed the base_url in config.toml is not used for oss. As a workaround for now, you can go with the env variable "CODEX_OSS_BASE_URL" and it works without any issues:
CODEX_OSS_BASE_URL="http://{your-host}/v1" codexBlackFrameAI commentedon Aug 17, 2025
A good workaround I have found for now is just start a local TCP forwarder: 127.0.0.1:11434 > xxx.xxx.xxx.xxx:PORT
Fix #2257 by allowing users to configure oss provider in config.toml
bartlettroscoe commentedon Sep 20, 2025
I think this is still an issue. Tool calling with
codex0.36.0 does not work with the gpt-oss-20b model served with vllm using their container:I can get
codexto call the model with "Hello" and other prompts, but as soon as the prompt triggers the usage of tools, codex just does nothing.But when I serve the gpt-oss-20b model with updated llama.cpp, everything works great.
So is the problem
codexor vLLM?jayteaftw commentedon Sep 22, 2025
@bartlettroscoe Its still and issue, just a separate one found here.
I think it is VLLM. In VLLM's guide for deploying GPT OSS it shows that
Response API with Streamingdoes not support function calling. So if Codex, is calling that api path, then I think that would be the problemFix openai#2257 by allowing users to configure oss provider in config…