Patch alpha release (0.151.0-alpha.9 → 0.151.0-alpha.10) with rollout reading improvements, client message chunking, and removal of a config key and escalate-related env var.
Changelog
[changed] Client messaging now surfaces chunked result events instead of a single combined message result event, so large client message payloads can be handled incrementally.
[new] Rollout handling includes a seekable reader path for more flexible reading of stored session rollouts.
[new] A writerlegacy_rollout_conversion_failed notification is emitted when legacy rollout conversion does not succeed.
[new] Config bundle responses are modeled as a dedicated typed payload (ConfigBundleResponse).
[removed] The exclude_slash_tmp config key is no longer supported.
[removed] The CODEX_ESCALATE_SOCKETMESSAGE environment variable is no longer recognized.
[removed] The cloud requirements TOML bundle data model is dropped in favor of the newer config-bundle response shape.
[changed] Hook handler configuration distinguishes agent and prompt hook handlers more explicitly.
[changed] Filesystem path handling adds a glob-pattern path form in place of the previous special-path variant.
[changed] Realtime thread start transport no longer uses the WebRTC transport option; an existing-call transport is used instead.
[changed] Tool-call summary messaging prefers a wait-agent style summary over the previous terminal message form.
[changed] Version metadata now reports 0.151.0-alpha.10 (rust-v0.151.0-alpha.10).
Under the hood
Rollout I/O gains a dedicated seekable reader subsystem to support non-linear access when loading or converting rollouts.
Account/login and host-to-client handshake/event enums were tightened (API-key thread init, handshake-rejected yield, and related client event naming), aligning internal protocol variants with the chunked client-message path.
Trace and delegate tooling internals were reshaped (code-mode response traces, code-cell started events, invoke-tool delegate requests) as part of the same protocol cleanup.
MCP elicitation request modeling shifts away from a URL-oriented high-risk form toward a form-oriented variant.
Upgrade notes
Remove any remaining exclude_slash_tmp settings from config; they will no longer apply.
Drop CODEX_ESCALATE_SOCKETMESSAGE from environments or scripts; it is no longer read.
If you integrate against client message result events, switch to the chunked client message result event stream.
Callers that depended on the cloud requirements TOML bundle shape should move to ConfigBundleResponse.
Realtime start flows that assumed a WebRTC transport should use the existing-call transport instead.
content/
Browse captured content/
Same tree as codex-cli/latest/content for this version. Open the full browser for sidebar navigation between docs and other files.
