mirror of
https://github.com/openai/codex.git
synced 2026-09-09 15:58:47 +00:00
555b82afa9
## Why Device-authenticated verification needs an app response outside automated approval and review. Previously, MCP user-verification requests were always cancelled. ## What changed - Add typed `openai/userVerification` elicitations carrying a title, description, and challenge through core and app-server. - Route verification to one connection enabled by trusted host activation. Restrict responses to that owner, exclude requests from replay, and cancel on disconnect or authentication changes, including account switches away and back. - Return proofs in `content`, discard response metadata, and cancel malformed acceptances. Suppress verification response logging and analytics, and send only a generic verification notice to realtime. - Keep the mode experimental and exclude it from stable schema exports. Capability advertisement remains disabled, and the TUI cancels verification requests. ## Testing Add coverage for owner isolation, disconnect and authentication races, proof response handling, automated-review bypass, inactive-host cancellation, stable schema filtering, and realtime payload exclusion. Update the MCP integration test to verify that an activated request holds the tool until the client responds. GitOrigin-RevId: c8c7b6691a3f7756682bbcca9def1df0d1feb906
codex-protocol
This crate defines the "types" for the protocol used by Codex CLI, which includes both "internal types" for communication between codex-core and codex-tui, as well as "external types" used with codex app-server.
This crate should have minimal dependencies.
Ideally, we should avoid "material business logic" in this crate, as we can always introduce Ext-style traits to add functionality to types in other crates.