Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Codex CLI 0.167.1 was published as a stable release at 21:32 UTC on November 10, 2026; incremental_tools_legacy remains under development and disabled by default.
- For regular Responses, the new gate applies to the amazon-bedrock and amazon-bedrock-runtime provider IDs; Responses Lite keeps its separate incremental_tools feature.
- Tool names, parameters and other catalog declarations can update incrementally in conversation history while existing input prefixes and compaction handling are preserved.
- Hosted web_search stays in top-level tools, outside additional_tools history declarations; the change provides no measured performance or cost savings.
0.167.1 is released, with the new option still off by default
Codex CLI 0.167.1 was published as a stable release at 21:32 UTC on November 10, 2026. It adds incremental_tools_legacy for the regular Responses path, but the code still marks the feature UnderDevelopment and sets its default to false.
This is relevant to developers using Codex through Amazon Bedrock who need to handle changes to their tool catalog: the tool names, parameters and other declarations sent to a model. The change concerns how those declarations evolve during a conversation; a stable release alone does not establish that a particular account or client has enabled it.
Check for one of the two supported Bedrock provider IDs
A provider ID identifies the model service within Codex. In the final code, regular Responses selects the incremental_tools_legacy feature only when model_provider_id exactly matches amazon-bedrock or amazon-bedrock-runtime, then checks whether that feature is enabled.
Responses Lite follows a separate branch and continues to use incremental_tools. These are independent feature settings, so enabling one does not establish the state of the other; even with a matching Bedrock ID, the new option requires an explicit opt-in.
Catalog changes enter history while existing input prefixes are preserved
On the path where the feature is enabled, tool declarations and later catalog changes can appear as additional_tools in conversation history while existing input prefixes are preserved. When a model changes or tools are removed or restored, check that the catalog visible to the model matches the tools currently available.
Compaction condenses a long conversation into a shorter context. This change also handles tool catalog state during remote compaction; added upstream scenarios and snapshots cover model changes and MCP tool removal and restoration, but those repository records do not replace verification in your environment.
Hosted web_search remains in top-level tools
With incremental catalog declarations, hosted web_search is still sent in the top-level Responses tools configuration rather than additional_tools history declarations. Both regular requests and remote compaction requests preserve this boundary.
Inspect the catalog history and top-level tool configuration together. An absent web_search entry in additional_tools does not establish that search configuration was lost; actual search availability still depends on the service support and permissions in use.
Verify the running version, provider ID and feature state
Start with the Codex CLI version actually running, then check the effective provider ID and incremental_tools_legacy setting. A release number identifies a code version; it does not establish which configuration branch is active.
For an evaluation, use an isolated environment you control to inspect requests before and after a tool catalog change: do updates appear in history, and does hosted web_search remain at the top level? Compare those observations with the official code for that version before deciding to use this under-development option.
The sources provide no measured latency, cache-hit, token-use or cost savings, and do not establish that your client has upgraded or your account can access a particular model. Verify model access, regional availability, billing and quotas under the actual service terms.
Sources
Frequently Asked Questions
Why does a custom Responses-compatible endpoint not establish eligibility for this path?
The code checks an exact provider ID, not an endpoint’s claim of API compatibility. A custom alias or compatible endpoint alone proves neither a match to the two Bedrock IDs nor that the default-off legacy feature is enabled.
Does a changed tool declaration prove that an MCP server was installed and started?
No. It shows that the visible tool catalog in request history changed, not that a server was installed, is running, or completed a tool call; verify those states separately in your own environment.