Unlocking the Codex harness: how we released the App Server

Tue, Apr 7 · 10:32 PM UTC 2 min read

Compiled by KHAO Editorial — aggregated from 1 outlet. See llms.txt for citation guidance.

★ Tier-1 Source

Diagram titled “App server process flow.” A client sends JSON-RPC messages to a stdio reader, which dispatches requests to a Codex message processor. The processor interacts with a thread manager and core thread via lookup threads, thread handles, submitted requests, and events/updates, then returns.

By Celia Chen, Member of the Technical Staff.

Key facts

The Codex App Server, a client-friendly, bidirectional JSON-RPC 1 API
A worker provisions a container with the checked-out workspace, launches the App Server binary inside it, and maintains a long-lived JSON-RPC over stdio 2 channel
Instead, they introduced a JSON-RPC protocol that mirrored the TUI loop, which became the unofficial first version of the App Server
Now that the App Server exists, they plan to refactor the TUI to use it so it behaves like any other client: launch an App Server child process, speak JSON-RPC over stdio, and render the same streaming

Summary

OpenAI’s coding agent Codex exists across many different surfaces: the web app , the CLI , the IDE extension , and the new Codex macOS app. In this post, they'll introduce the Codex App Server; they'll share their learnings so far on the best ways to bring Codex’s capabilities into your product to help your users supercharge their workflows. Before diving into architecture, it’s helpful to know the App Server’s backstory. Codex CLI started as a TUI (terminal user interface), meaning Codex is accessed through the terminal. Instead, they introduced a JSON-RPC protocol that mirrored the TUI loop, which became the unofficial first version of the App Server.

Read full article at OpenAI →

#codex