Prerelease (0.154.0-alpha.3 → 0.154.0-alpha.6) focused on managed Git worktree sessions, removal of the standalone mcp-server command, and richer exec-server remote transport/auth options.
Changelog
[new] Run a session in a managed Git worktree with the global --worktree flag (also on exec, resume, fork, queue, archive/delete/unarchive flows, and related paths). Shell completions describe this as starting the session in a new managed worktree; the TUI includes worktree startup and browsing support, and /worktree is available as a slash command.
[new]exec-server remote connectivity gains --remote-transport with noise and direct modes, plus optional AWS SigV4 signing via --aws-sigv4, --aws-profile, --aws-region, and --aws-service (mutually coordinated with agent-identity auth where applicable).
[new]User verification support lands across app-server, MCP, and related clients (enroll / status / verify / delete-style flows and elicitation), so hosts can prove or check verified access when a server requests it.
[changed]Guardian automatic review continues to evolve: runtime, decision handling, reviewer configuration, and review-session context are reworked, and assessment/config payloads carry more detail for approve-for-me style review.
[changed] TUI polish: async question UI in the bottom pane, updated feedback notes, assistant directives, file citations in markdown rendering, experimental-feature and model-default session helpers, and related chat composer/rendering fixes.
[new] Config key exclude_slash_tmp for controlling slash-tmp exclusion behavior.
[removed] The codex mcp-server subcommand (start Codex as an MCP server over stdio) is gone, along with its crate and interface doc. External MCP server management remains under codex mcp.
[changed] Bash, fish, and zsh completions updated for --worktree, exec-server remote/AWS flags, and the mcp-server removal.
Under the hood
New worktree and attachment-store workspace crates underpin managed worktrees and attachment handling.
MCP surface area shifts toward codex-mcp (auth-change handling, client tool catalog, user-verification elicitation) after dropping the old in-tree mcp-server implementation.
Exec-server adds direct remote paths and client telemetry; app-server and CLI pick up verification/auth helpers.
Session/core pieces expand (for example reasoning-effort handling, retained context, thread metadata/compatibility fields) and Guardian V2 config/events grow additional fields.
Hook configuration distinguishes command vs prompt handlers more clearly; browser-use requirement and keymap-related config shapes were extended.
Dependency refresh: futures/bytes, rcgen/yasna, toml_parser, and log, among others.
Internal agents/docs guidance no longer points at maintaining app-server/README.md as the primary API doc hook; schema fixture regeneration remains the expected workflow when API shapes change.
Upgrade notes
If you still launch codex mcp-server, switch off that entrypoint—this alpha no longer ships it. Prefer hosting or connecting via the supported MCP client/codex mcp management flows instead of the removed stdio server command.
Regenerate or refresh shell completions so --worktree and the exec-server transport/SigV4 flags complete correctly and mcp-server disappears from help.
For remote exec-server registration, choose --remote-transport noise|direct explicitly when needed, and configure AWS SigV4 flags if your environment expects signed Direct/WebSocket handshakes rather than agent-identity auth alone.
Try --worktree (or /worktree) only in Git checkouts where creating a managed linked worktree is acceptable for the session’s working tree.
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.
