Bug:After today's update, even with `image_generation = false` configured, requests sent by the application still include the `image_generation` tool.

Resolved 💬 2 comments Opened Jun 5, 2026 by zhongruan0522 Closed Jun 6, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.602.30954 · Released on June 5, 2026

What subscription do you have?

Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

After updating to the latest version of Codex today, requests sent by the application still include the image_generation tool, even though image_generation = false has been configured.

The configuration is as follows:
~~~
[features]
image_generation = false
~~~

This configuration is ineffective for the app but works for CodexCLI.

What steps can reproduce the bug?

Prepare an API that does not support image_generation, configure it as a small model integration, and set the following:
~~~
[features]
image_generation = false
~~~
Close the CodexAPP and restart it, ensuring it uses the configured API. When sending a message, the app throws an error: Image generation is not enabled for this group. However, when running CodexCLI, conversation proceeds normally.

What is the expected behavior?

The conversation proceeds normally instead of throwing the error "Image generation is not enabled for this group."

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #26448
  • #25974
  • #25981
  • #25982

Powered by Codex Action

etraut-openai contributor · 2 months ago

Feature flags are used when a feature is being developed. They are not intended to control stable features. Once a feature is stable, it is generally always on.