Use the image generation extension by default - #31596
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6547da9b41
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
9f34d5a to
5bf5947
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5bf5947975
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
5bf5947 to
dbd765f
Compare
## Why After #31596 routes all new image generation through the extension, the built-in hosted pipeline is unreachable and can be removed independently. ## What changed - Remove the hosted image generation tool spec and its code-mode/tool-search handling. - Remove live hosted image-generation stream persistence and the generated-image instruction injection it required. - Delete tests that only covered the removed live pipeline. - Keep protocol/history support for existing `ImageGenerationCall` rollout items, including replay, rollback, and renderable history behavior. ## Validation - `just test -p codex-core stream_events_utils` - `just test -p codex-core generated_image` - `just test -p codex-core image_generation_publication_preserves_extension_saved_path` - `just test -p codex-image-generation-extension` - `just test -p codex-tools` - Scoped Clippy fixes for `codex-core` and `codex-tools`
Why
Image generation should have one implementation path. This cutover makes the image generation extension the default everywhere while preserving the existing stable feature toggle and compatibility alias.
What changed
Feature::ImageGenerationexclusively gate extension-backed image generation and keepimagegenextas a legacy alias.requires_openai_authproviders.Validation
just test -p codex-featuresjust test -p codex-core image_generationjust test -p codex-mcp-server image_generation_extension_is_enabled_by_defaultcargo check -p codex-core-api -p codex-thread-manager-sample