Files

Gabriel Peal 1d76ba5ebe [App Server] Allow fetching or resuming a conversation summary from the conversation id (#5890 )

This PR adds an option to app server to allow conversation summaries to
be fetched from just the conversation id rather than rollout path for
convenience at the cost of some latency to discover the rollout path.

This convenience is non-trivial as it allows app servers to simply
maintain conversation ids rather than rollout paths and the associated
platform (Windows) handling associated with storing and encoding them
correctly.

2025-10-28 20:17:22 -04:00

src

[App Server] Allow fetching or resuming a conversation summary from the conversation id (#5890 )

2025-10-28 20:17:22 -04:00

tests

[App Server] Allow fetching or resuming a conversation summary from the conversation id (#5890 )

2025-10-28 20:17:22 -04:00

Cargo.toml

Add feedback upload request handling (#5682 )

2025-10-27 05:53:39 +00:00

README.md

docs: add barebones README for codex-app-server crate (#4671 )

2025-10-03 09:26:44 -07:00

README.md

codex-app-server

codex app-server is the harness Codex uses to power rich interfaces such as the Codex VS Code extension. The message schema is currently unstable, but those who wish to build experimental UIs on top of Codex may find it valuable.

Protocol

Similar to MCP, codex app-server supports bidirectional communication, streaming JSONL over stdio. The protocol is JSON-RPC 2.0, though the "jsonrpc":"2.0" header is omitted.

Message Schema

Currently, you can dump a TypeScript version of the schema using codex generate-ts. It is specific to the version of Codex you used to run generate-ts, so the two are guaranteed to be compatible.

codex generate-ts --out DIR