Key points
- Version 0.167.2 sends tool updates incrementally by default on Vertex AI.
- Developers can disable this feature using a specific config.toml flag.
- The change is linked to internal issue references #60617 and #60848.
OpenAI has released version 0.167.2 of its Codex agent, introducing a default change for deployments on Google Cloud Vertex AI.confirmed This update modifies how the system handles tool updates during operation.This update changes how the AI agent sends information to Google Cloud by default.The 0.167.2 release alters the default tool update transmission protocol for Vertex AI integrations.
The evidence
According to the official release notes, Codex now sends tool updates incrementally by default when running on Vertex AI.reported The documentation explicitly links this change to internal issue numbers #60617 and #60848. No further details on the previous default behaviour are provided in the release text.
The decision
The release provides a mechanism for users who prefer to opt out of the new default. To revert to the previous method, developers must set the `incremental_tools_legacy_gcp` flag to false. This setting must be placed under the `[features]` section within the `config.toml` file.
What the evidence means
The documentation presents the incremental update as a new feature without explaining the technical rationale. The availability of a legacy toggle indicates that the previous method remains supported for those who require it. The change is specific to the Vertex AI environment, as indicated by the flag name.
What builders can do with it
Developers deploying Codex on Vertex AI can use the new default incremental tool updates. For systems that require the previous update mechanism, builders can maintain stability by adjusting the `config.toml` file. This allows teams to select the update strategy that fits their integration requirements. The source does not specify performance differences between the two methods.
Why it matters
- Teams using Vertex AI can expect a change in default behaviour, requiring verification of existing tool update workflows.
- The ability to toggle the feature via `config.toml` allows for controlled migration rather than forced adoption.
- Reference to specific issue numbers (#60617, #60848) provides traceability for debugging or understanding the rationale behind the change.
- The change is specific to Google Cloud Vertex AI, meaning deployments on other platforms remain unaffected by this default shift.
Topics: OpenAI, Codex, Vertex AI, configuration, tool updates
Updated
Then / now / next
Previous versions of Codex did not default to incremental tool updates on Vertex AI.
Version 0.167.2 sends tool updates incrementally by default on Google Cloud Vertex AI.
Developers should monitor for further refinements to this feature in subsequent releases.
Story timeline
- Then Previous versions of Codex did not default to incremental tool updates on Vertex AI.
- 11 Nov 2026 0.167.2
- Now Version 0.167.2 sends tool updates incrementally by default on Google Cloud Vertex AI.
- Next Developers should monitor for further refinements to this feature in subsequent releases.
The strongest doubt
Counterpoint from the sources
The release notes do not specify the performance or reliability benefits of incremental updates, leaving the rationale for the default change implicit.
For readers
Developers
- Update config.toml if legacy tool update behaviour is required for existing Vertex AI deployments.
- Verify that incremental updates function correctly with current tool integrations.
Policy
- Monitor how default changes in AI agent behaviour impact compliance and audit trails.
- Review vendor documentation for transparency on issue tracking and change management.
Business
- Assess whether the new default update method aligns with operational efficiency goals.
- Ensure IT teams are aware of the configuration option to revert changes if necessary.
Ask the article
Local keyword search of this article; no generated answers.Which of these is confirmed?
Check the answer
OpenAI has released version 0.167.2 of its Codex agent, introducing a default change for deployments on Google Cloud Vertex AI.
The matched primary source and announcement wording support the confirmed label.
Did this article give you the evidence you needed?
Your choice stays on this device. No public tally.Terms in this story
incremental tool updates
A method of sending tool updates in smaller, sequential chunks rather than as a single large payload.
config.toml
A configuration file format used to store settings and preferences for the application.
Vertex AI
Google Cloud's platform for building and deploying machine learning models and AI applications.
Questions readers ask
How do I disable incremental tool updates in Codex 0.167.2?
Set `incremental_tools_legacy_gcp = false` under the `[features]` section in your `config.toml` file.
Does this change affect all cloud providers?
No, the default incremental update behaviour is specific to Google Cloud Vertex AI deployments.
Which version introduces this change?
The change was introduced in OpenAI Codex version 0.167.2.
Connected stories
Reading receipt
- Version 0.167.2 sends tool updates incrementally by default on Vertex AI.
- Developers can disable this feature using a specific config.toml flag.
- The change is linked to internal issue references #60617 and #60848.
Still open: What specific performance or stability issues did incremental updates resolve?
Still open: Will this default behaviour be extended to other cloud platforms in future releases?