## Why Automatic mailbox wakes can start new turns while the app-server is draining or has paused turn admission. Native child results still need to reach the parent during drain so they can survive a daemon restart. ## What changed - Require a turn admission permit for ordinary automatic mailbox wakes and hold it through turn registration. Retry queued work when a temporary pause ends. Explicit follow-ups and native child results can still wake the parent during drain. - Let `thread/inject_items` queue plain-text agent messages for native child threads when native tools are enabled. Injected mail follows the ordinary wake rules. - Extract the remote app-server client, shared event and request types, and WebSocket compression into `codex-app-server-remote-client` so callers can use them without linking the app-server runtime. ## Testing Cover delivery of queued mail when admission reopens, injection into native child threads, and recovery of a child result after a daemon restart. GitOrigin-RevId: 4c5ceeca8829c2612cc2b6b74c03d0c7677a9244
codex-app-server-client
Shared in-process app-server client used by conversational CLI surfaces:
codex-execcodex-tui
Purpose
This crate centralizes startup and lifecycle management for an in-process
codex-app-server runtime, so CLI clients do not need to duplicate:
- app-server bootstrap and initialize handshake
- in-memory request/event transport wiring
- lifecycle orchestration around caller-provided startup identity
- graceful shutdown behavior
Startup identity
Callers pass both the app-server SessionSource and the initialize
client_info.name explicitly when starting the facade.
That keeps thread metadata (for example in thread/list and thread/read)
aligned with the originating runtime without baking TUI/exec-specific policy
into the shared client layer.
Transport model
The in-process path uses typed channels:
- client -> server:
ClientRequest/ClientNotification - server -> client:
InProcessServerEventServerRequestServerNotificationLegacyNotification
JSON serialization is still used at external transport boundaries (stdio/websocket), but the in-process hot path is typed.
Typed requests still receive app-server responses through the JSON-RPC result envelope internally. That is intentional: the in-process path is meant to preserve app-server semantics while removing the process boundary, not to introduce a second response contract.
Bootstrap behavior
The client facade starts an already-initialized in-process runtime, but thread bootstrap still follows normal app-server flow:
- caller sends
thread/startorthread/resume - app-server returns the immediate typed response
- richer session metadata may arrive later as a
SessionConfiguredlegacy event
Surfaces such as TUI and exec may therefore need a short bootstrap phase where they reconcile startup response data with later events.
Backpressure and shutdown
- Command queues and the embedded runtime remain bounded, using
DEFAULT_IN_PROCESS_CHANNEL_CAPACITYby default. - The facade's local consumer event queue is unbounded and preserves notification order. This keeps the worker draining the bounded runtime while a caller waits for a request, preventing unread notifications from blocking its response.
shutdown()performs a bounded graceful shutdown and then aborts if timeout is exceeded.