Alpha· Notable · Confirmed
Pin important threads and keep interrupted prompts
App clients gain persistent thread pinning, while interrupted MCP startup keeps user input and request handling becomes more efficient.
This alpha adds a durable pin state for app-server threads, including list filtering and persistence across reconciliation and archive transitions. It also fixes a cancellation edge case that could lose the user's prompt while MCP tools were still starting.
Under the hood, Responses request construction now avoids rebuilding tool definitions as generic JSON and cloning full incremental prefixes. The in-process app server also performs a bounded analytics flush before shutdown so completed-turn and accepted-line events are less likely to be dropped.
Alpha release context: rust-v0.146.0-alpha.4 contains 8 commits and 127 changed files compared with rust-v0.146.0-alpha.3.
Evidence
App-server threads can be pinned and filtered by pin state.Why it matters: Clients can keep important conversations easy to find, and the pinned state survives reconciliation, archive transitions, and restarts.
Direct evidence · Confirmed
Supporting sources
- Add persisted thread pinning to the app server (#34840) commit · Official
- rust-v0.146.0-alpha.3 to rust-v0.146.0-alpha.4 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Prompts remain in conversation history when MCP startup is interrupted.Why it matters: Stopping a turn while MCP tools are still starting should no longer make the submitted prompt disappear from the recorded conversation.
Direct evidence · Confirmed
Supporting sources
- Preserve user input when MCP startup is interrupted (#34839) commit · Official
- rust-v0.146.0-alpha.3 to rust-v0.146.0-alpha.4 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Responses request construction avoids unnecessary JSON rebuilding and prefix cloning.Why it matters: HTTP and WebSocket request preparation should use less memory and copying, especially when tool definitions or incremental request histories are large.
Direct evidence · Confirmed
Supporting sources
- Reduce cloning when building Responses requests (#34825) commit · Official
- rust-v0.146.0-alpha.3 to rust-v0.146.0-alpha.4 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
The in-process app server flushes queued analytics before shutdown.Why it matters: Completed-turn and accepted-line events are less likely to be dropped when the embedded app-server runtime closes.
Direct evidence · Confirmed
Supporting sources
- Flush analytics before in-process app server shutdown (#34831) commit · Official
- rust-v0.146.0-alpha.3 to rust-v0.146.0-alpha.4 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Availability
Availability note: these sources establish repository and CLI prerelease activity. 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. |