Alpha· Major · Confirmed
MCP startup stops blocking unrelated work
Codex 0.147 alpha.2 keeps tools and queued input moving during MCP startup, bounds server discovery, improves thread organization and remote file handling, and tightens network policy; 0.146 also receives two targeted hotfixes.
The headline change is less waiting around MCP startup. Unrelated tools can run while optional servers initialize, and terminal input queued during that startup is retained instead of being held behind the same readiness boundary.
Discovery is more defensive as well. Namespace descriptions and catalog pagination now have explicit limits for pages, items, cursor size, and elapsed time, while authentication can report an unknown state rather than collapsing uncertainty into a yes-or-no answer.
Conversation organization continues to mature: manual section ordering is persisted, and forked chats can be named from the terminal. MCP file uploads now use paths native to the active environment, cloud-managed server definitions can reach the CLI, and stdio app-server processes exit with their client connection.
Network policy gets a fail-closed correction. If Codex cannot apply a requested network allow amendment, the sandbox retains denied access instead of risking a broader permission state.
A separate 0.146 hotfix line also landed. Alpha 9.1 adds managed control over in-app updates, and alpha 9.2 makes the R2 publisher accept the second numeric suffix used by alpha hotfix versions.
Release context: the rust-v0.147.0-alpha.1 to rust-v0.147.0-alpha.2 comparison contains 33 commits and lists 287 changed files. The two 0.146 hotfix comparisons contain two commits each, including their release commits, and are presented separately because they do not form the next step of the 0.147 line.
Evidence
MCP startup no longer blocks unrelated tools or queued terminal input.Why it matters: Developers can keep working while optional MCP servers initialize instead of waiting for every server before unrelated actions can proceed.
Direct evidence · Confirmed
Supporting sources
- Let unrelated tools run while MCP servers start commit · Official
- Fix TUI input queue during MCP startup commit · Official
- rust-v0.147.0-alpha.1 to rust-v0.147.0-alpha.2 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
MCP discovery now has explicit size, pagination, cursor, and timeout limits.Why it matters: Runaway or malformed catalogs are less likely to consume unbounded work, and clients can distinguish an unknown authentication state from a definite answer.
Direct evidence · Confirmed
Supporting sources
- Bound MCP namespace descriptions commit · Official
- Add limits to MCP catalog pagination commit · Official
- Distinguish unknown MCP authentication status commit · Official
- rust-v0.147.0-alpha.1 to rust-v0.147.0-alpha.2 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Thread sections retain manual ordering, and forked chats can be named from the terminal.Why it matters: Conversation organization becomes more intentional: section order survives reloads and a fork can receive a useful name as it is created.
Direct evidence · Confirmed
Supporting sources
- Add persisted manual ordering for thread sections commit · Official
- Support naming forked chats from the TUI commit · Official
- rust-v0.147.0-alpha.1 to rust-v0.147.0-alpha.2 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
MCP file uploads use environment-native paths, and the CLI can load cloud-managed servers.Why it matters: Files are handed to servers in the path format of the active environment, while managed server definitions can reach the CLI without duplicate local setup.
Direct evidence · Confirmed
Supporting sources
- Use environment-native paths for MCP file uploads commit · Official
- Load cloud-managed servers in the MCP CLI commit · Official
- Exit the stdio app-server when its connection closes commit · Official
- rust-v0.147.0-alpha.1 to rust-v0.147.0-alpha.2 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
A failed network allow amendment now leaves network access denied.Why it matters: If Codex cannot apply the requested exception, it keeps the restrictive state instead of accidentally permitting broader access.
Direct evidence · Confirmed
Supporting sources
- Deny network access when an allow amendment fails commit · Official
- rust-v0.147.0-alpha.1 to rust-v0.147.0-alpha.2 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
The 0.146 alpha hotfixes add managed in-app update policy and repair hotfix publishing.Why it matters: Administrators can disable the canonical in-app update feature through managed requirements, and release tooling now accepts a second numeric alpha-hotfix suffix.
Direct evidence · Confirmed
Supporting sources
- Add managed in-app updates feature commit · Official
- Allow alpha hotfix versions in R2 releases commit · Official
- rust-v0.146.0-alpha.9 to rust-v0.146.0-alpha.9.1 comparison tag-compare · Official
- rust-v0.146.0-alpha.9.1 to rust-v0.146.0-alpha.9.2 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Availability
Availability note: the sources establish repository and CLI prerelease activity for the listed versions. They do not, by themselves, prove that the same changes were live in Codex Desktop.
Availability by surface
| Surface | Status | Claim-level evidence |
|---|---|---|
| CLI | Prerelease · Documented · General |
|
| Desktop | Unknown · Unknown · Unknown |
|
| IDE | Unknown | No central-claim assertion recorded. |
| Cloud | Unknown | No central-claim assertion recorded. |
| Mobile | Unknown | No central-claim assertion recorded. |