Alpha· Major · Confirmed
Name sessions directly with `/new` and `/clear`
Slash commands can name new sessions, while Windows navigation, sandbox proxies, and managed-policy behavior become more robust.
The most visible change lets terminal users name a session at creation time. The same prerelease comparison fixes Windows TUI navigation, hardens managed proxy setup for sandboxed commands, and tightens exact-value managed configuration.
Alpha release context: 4 official tags were published that UTC day (rust-v0.145.0-alpha.30, rust-v0.146.0-alpha.1, rust-v0.146.0-alpha.2, rust-v0.146.0-alpha.3). The full comparison contains 99 commits and at least 300 changed files.
Evidence
The `/new` and `/clear` commands accept optional session names.Why it matters: Terminal users can create a fresh session with a meaningful name in one command.
Direct evidence · Confirmed
Supporting sources
- Allow naming sessions with `/new` and `/clear` (#34605) commit · Official
- rust-v0.145.0-alpha.29 to rust-v0.146.0-alpha.3 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Managed proxy setup is hardened for sandboxed executions.Why it matters: Sandboxed commands are less likely to bypass or misapply the proxy configuration imposed by a managed environment.
Direct evidence · Confirmed
Supporting sources
- Harden managed proxy setup for sandboxed executions (#34641) commit · Official
- rust-v0.145.0-alpha.29 to rust-v0.146.0-alpha.3 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Managed configuration enforces exact-value requirements.Why it matters: Administrators can require a setting to match an approved value rather than merely requiring that the setting exist.
Direct evidence · Confirmed
Supporting sources
- Enforce exact values from managed config requirements (#34597) commit · Official
- rust-v0.145.0-alpha.29 to rust-v0.146.0-alpha.3 comparison tag-compare · Official
Conflicting sources
No conflicting sources recorded.
Availability
Availability note: these sources establish repository and CLI release 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. |