codex-app-server-sdk
High-level async Python client for codex app-server.
It gives you a convenient conversation API over stdio or websocket without having to manage raw protocol events yourself.
Documentation: https://emsi.github.io/codex-app-server-sdk/
Upgrading to 0.4.0? Behavior changes require review. Read the 0.3.2 → 0.4.0 migration guide before upgrading. Stream-based approval responders must set
approval_mode="manual". Failed/interrupted turns now raise; cancellation, initialization, unanswered user questions, and custom transport expectations also change.
Highlights
- simple one-shot turns with
chat_once(...) - step-streaming turns with
chat(...)(thinking,exec,codex, etc.), non-delta - built-in thread/turn lifecycle handling
- thread-scoped config + forking via
ThreadHandle - inactivity timeout continuation for long-running turns
- turn cancellation with unread-step/event drain via
cancel(...) - collaboration mode overrides (
default/plan) viaTurnOverrides - human-in-the-loop user input handling (
item/tool/requestUserInput) - optional low-level
request(...)access when needed
Why use this client?
Protocol I/O and callbacks run directly on your application's asyncio event
loop, using asynchronous subprocess pipes or WebSockets. Thread handles share
one connection, and approvals can integrate with an async callback or a manual
UI response loop.
You control the Codex runtime: launch your chosen executable or connect to an
existing WebSocket server. The conversation API adds completed-step streaming,
resumable inactivity timeouts, and cancellation with unread-event recovery.
The Transport interface and raw request(...) method remain available for
application-specific integrations.
Compared with openai-codex
Both libraries use the Codex app-server protocol. Their integration choices differ:
| Area | codex-app-server-sdk |
openai-codex |
|---|---|---|
| Execution | Native asyncio client; asynchronous protocol I/O on your event loop |
Synchronous client with an async wrapper that offloads blocking operations to background threads |
| Transport | Public, replaceable Transport; built-in stdio and WebSocket support |
SDK-managed subprocess communicating through line-delimited JSON over stdio |
| Protocol access | Flexible dictionary-based RPC via request(...), plus high-level conversation models |
Extensive generated types, typed responses, and typed notifications |
| Runtime management | You supply and manage Codex; choose an executable or connect to an existing WebSocket server | Installs an exactly pinned Codex runtime dependency by default |
This client fits applications that need native async I/O, custom transports, connections to an existing server, or independent control over runtime upgrades. The official SDK offers broader generated type coverage and a reproducible runtime default. You are responsible for installing and updating Codex when using this client.
Comparison verified against the published
openai-codex 0.156.1
source and package metadata on 2026-09-23. The official SDK also supports a
CodexConfig(codex_bin=...) override
for selecting a different local executable.
Install
Install uv (if needed):
curl -LsSf https://astral.sh/uv/install.sh | sh
Install the package from PyPI:
uv add codex-app-server-sdk
Or pip-compatible install in the active environment:
uv pip install codex-app-server-sdk
Documentation
- Docs site: https://emsi.github.io/codex-app-server-sdk/
- PyPI: https://pypi.org/project/codex-app-server-sdk/
- Human-in-the-loop guide: https://emsi.github.io/codex-app-server-sdk/human-in-the-loop/
- Release procedure: RELEASE.md
- Upgrading from 0.3.2: 0.4.0 migration guide
- Release notes and migration guidance: CHANGELOG.md
Quick start
Stdio
import asyncio
from codex_app_server_sdk import CodexClient
async def main() -> None:
async with CodexClient.connect_stdio() as client:
result = await client.chat_once("Hello from Python")
print(result.final_text)
asyncio.run(main())
By default, stdio transport runs:
- command:
codex app-server
You can override via:
connect_stdio(command=[...])- environment variable:
CODEX_APP_SERVER_CMD
Websocket
import asyncio
from codex_app_server_sdk import CodexClient
async def main() -> None:
async with CodexClient.connect_websocket() as client:
result = await client.chat_once("Hello over websocket")
print(result.final_text)
asyncio.run(main())
Websocket defaults:
- URL:
CODEX_APP_SERVER_WS_URLorws://127.0.0.1:8765 - Bearer token:
CODEX_APP_SERVER_TOKEN(optional)
Continuation on inactivity timeout
Both high-level APIs support resuming the same running turn.
import asyncio
from codex_app_server_sdk import CodexClient, CodexTurnInactiveError
async def main() -> None:
async with CodexClient.connect_stdio(inactivity_timeout=120.0) as client:
continuation = None
while True:
try:
if continuation is None:
result = await client.chat_once("Do a longer task")
else:
result = await client.chat_once(continuation=continuation)
print(result.final_text)
break
except CodexTurnInactiveError as exc:
continuation = exc.continuation
idle = (
f"{exc.idle_seconds:.1f}s"
if exc.idle_seconds is not None
else "unknown"
)
print(
f"[warn] turn inactive for {idle}; resuming "
f"(thread_id={continuation.thread_id}, turn_id={continuation.turn_id})"
)
asyncio.run(main())
Advanced thread control (cwd/instructions/model/fork)
Use explicit thread handles when you need thread-scoped configuration.
import asyncio
from codex_app_server_sdk import CodexClient, ThreadConfig, TurnOverrides
async def main() -> None:
async with CodexClient.connect_stdio() as client:
thread = await client.start_thread(
ThreadConfig(
cwd="/home/me/project",
base_instructions="You are concise.",
developer_instructions="Prefer rg over grep.",
model="gpt-5",
)
)
result = await thread.chat_once("Summarize the repo layout.")
print(result.final_text)
await thread.update_defaults(ThreadConfig(model="gpt-5.1-codex-mini"))
forked = await thread.fork(
overrides=ThreadConfig(
developer_instructions="Focus on tests first.",
)
)
async for step in forked.chat(
"Run a quick diagnostics pass.",
turn_overrides=TurnOverrides(effort="low"),
):
print(step.step_type, step.text)
asyncio.run(main())
Configuration scopes and semantics
CodexClient: connection/session scope (transport, request routing, lifecycle).ThreadHandle+ThreadConfig: thread scope (cwd,baseInstructions,developerInstructions,model, etc.).TurnOverrides: per-turn scope (cwd,model,effort,summary, ...).
UNSET vs None
UNSET(default): omit field from request payload; keep server default/current value.None: send JSONnullexplicitly (where protocol allows) to reset/clear.
Example:
from codex_app_server_sdk import ThreadConfig, UNSET
cfg = ThreadConfig(
model=UNSET, # omit key
developer_instructions=None, # send explicit null
)
Continuation constraints
When resuming with continuation=..., do not pass extra turn-start arguments in
that same call. Specifically, do not pass: text, thread_id, user,
metadata, thread_config, or turn_overrides.
Apply thread changes via thread.update_defaults(...) or start a new/forked thread before continuing with a new turn.
Example clients
More complete examples are under examples/.
All thread_* examples print lifecycle progress checkpoints by default so long operations are visible.
Use --quiet on those scripts for minimal output.
Rich step-stream example (thinking/exec/codex blocks)
Recommended example for step-oriented API and continuation behavior.
Stdio:
uv run python examples/chat_steps_rich.py
Websocket:
uv run python examples/chat_steps_rich.py --transport websocket --url ws://127.0.0.1:8765
With extra payload summaries:
uv run python examples/chat_steps_rich.py --show-data
Cancel timed-out turns instead of auto-resume:
uv run python examples/chat_steps_rich.py --cancel-on-timeout
Common options:
--transport {stdio,websocket}--cmd "codex app-server"(stdio mode)--url ws://127.0.0.1:8765(websocket mode)--token "$CODEX_APP_SERVER_TOKEN"(websocket mode)--prompt "..."--user "..."--inactivity-timeout 120--show-data--cancel-on-timeout
Advanced thread config + fork example
uv run python examples/thread_config_and_fork.py \
--transport stdio \
--cwd . \
--base-instructions "Be concise." \
--developer-instructions "Prioritize correctness."
Websocket:
uv run python examples/thread_config_and_fork.py \
--transport websocket \
--url ws://127.0.0.1:8765
Quiet mode:
uv run python examples/thread_config_and_fork.py --quiet
Resume-by-id example
uv run python examples/thread_resume_by_id.py \
--transport stdio \
--thread-id <existing-thread-id> \
--prompt "Continue the previous conversation."
Quiet mode:
uv run python examples/thread_resume_by_id.py --thread-id <existing-thread-id> --quiet
Concurrent thread handles example
This example starts two new threads and runs turns concurrently on those fresh
ThreadHandles over one shared client connection (it does not call
thread/resume for the newly started threads).
uv run python examples/thread_concurrent_handles.py --transport stdio
Quiet mode:
uv run python examples/thread_concurrent_handles.py --quiet
Thread/model/config ops showcase
This example uses the newly exposed helper APIs:
thread/read,thread/list,thread/name/set,thread/archivemodel/listconfig/read- endpoint-aware summaries with explicit
<not-provided>/nullvalues - optional thread model update reporting with
--set-model config/readprintsorigin_entries: count of config keys that include provenance metadata (which layer/file provided that effective value)
uv run python examples/thread_ops_showcase.py \
--transport stdio \
--prompt "Give a 3-bullet summary." \
--thread-name "showcase-thread"
Websocket:
uv run python examples/thread_ops_showcase.py \
--transport websocket \
--url ws://127.0.0.1:8765
Show model update intent and before/after thread snapshot model visibility:
uv run python examples/thread_ops_showcase.py --set-model gpt-5.3-codex
With raw payload dumps:
uv run python examples/thread_ops_showcase.py --show-data
Quiet mode:
uv run python examples/thread_ops_showcase.py --quiet
Stdio example (multi-turn, one thread)
uv run python examples/chat_session_stdio.py
Custom command and prompts:
uv run python examples/chat_session_stdio.py \
--cmd "codex app-server" \
--prompt "First prompt" \
--prompt "Second prompt"
Websocket example (multi-turn, one thread)
uv run python examples/chat_session_websocket.py
With explicit endpoint/token:
uv run python examples/chat_session_websocket.py \
--url ws://127.0.0.1:8765 \
--token "$CODEX_APP_SERVER_TOKEN"
Or via environment:
export CODEX_APP_SERVER_WS_URL=ws://127.0.0.1:8765
export CODEX_APP_SERVER_TOKEN=your-token
uv run python examples/chat_session_websocket.py
API reference (quick)
CodexClient (src/codex_app_server_sdk/client.py)
connect_stdio(...): create a stdio-configured client (unstarted).connect_websocket(...): create a websocket-configured client (unstarted).start(): connect transport and start receive loop (idempotent).initialize(params=None, timeout=None): perform JSON-RPC initialize handshake with default-merged params (protocolVersion,clientInfo,capabilities) and return normalizedInitializeResult.request(method, params=None, timeout=None): low-level JSON-RPC request helper.start_thread(config=None): create thread and returnThreadHandle.resume_thread(thread_id, overrides=None): resume thread and returnThreadHandle.fork_thread(thread_id, overrides=None): fork thread and returnThreadHandle.set_thread_defaults(thread_id, overrides): apply thread-level overrides viathread/resume.read_thread(thread_id, include_turns=True): read one thread.list_threads(...): list threads with optional filters.set_thread_name(thread_id, name): rename thread.archive_thread(thread_id)/unarchive_thread(thread_id): archive lifecycle controls.rollback_thread(thread_id, num_turns=...): drop recent turns from thread history.compact_thread(thread_id): request context compaction.chat(...)(text=None, thread_id=None, user=None, metadata=None, thread_config=None, turn_overrides=None, inactivity_timeout=None, continuation=None): async iterator yielding completed non-delta step blocks.chat_once(...)(text=None, thread_id=None, user=None, metadata=None, thread_config=None, turn_overrides=None, inactivity_timeout=None, continuation=None): send one user message and wait for completed turn.cancel(continuation, timeout=None): interrupt a turn and return unread steps/events after terminal confirmation; retain the continuation if cancellation fails or times out.steer_turn(thread_id=..., expected_turn_id=..., input_items=...): steer active turn input.start_review(thread_id=..., target=..., delivery=None): run review mode.list_models(...): discover available models.exec_command(command, ...): run one command via server command API.read_config(...),read_config_requirements(),write_config_value(...),batch_write_config(...): config APIs.interrupt_turn(turn_id, thread_id=None, timeout=None): low-level interruption request; infer the thread for tracked turns or pass it explicitly.close(): cancel receive loop and close transport.
Transport and implementations (src/codex_app_server_sdk/transport.py)
Transport.connect/send/recv/close: abstract interface.StdioTransport: line-delimited JSON over subprocess stdin/stdout.WebSocketTransport: JSON messages over websocket frames.
Data models (src/codex_app_server_sdk/models.py)
InitializeResult: parsed initialize response (protocol_version,server_info,capabilities,raw).ConversationStep: completed step fromchat(...)(step_type,item_type,text,item_id,thread_id,turn_id,data).ChatResult: buffered turn output (thread_id,turn_id,final_text,raw_events,assistant_item_id,completion_source).ChatContinuation: continuation token for timed-out running turns (thread_id,turn_id,cursor,mode).CancelResult: cancellation result with unreadsteps/raw_eventsplus terminal flags.ThreadConfig: thread-level config forthread/start,thread/resume,thread/fork(cwd,base_instructions,developer_instructions,model, ...).TurnOverrides: per-turn overrides forwarded toturn/start(cwd,model,effort, ...).UNSET: sentinel for “omit this field from request payload.”ApprovalPolicy: literal type for approval policy values (untrusted,on-failure,on-request,never).
ThreadHandle (src/codex_app_server_sdk/client.py)
thread_id: bound thread id.defaults: local thread config snapshot.chat_once(...): convenience one-turn call bound to this thread.chat(...): step-streaming call bound to this thread.update_defaults(overrides): apply thread defaults between messages.fork(overrides=None): fork thread and get a new handle.read(include_turns=True): low-level thread/read helper.set_name(name),archive(),unarchive(),rollback(num_turns),compact(): thread lifecycle/history helpers.start_review(target, delivery=None): thread-bound review API.
Exceptions (src/codex_app_server_sdk/errors.py)
CodexError: base exception.CodexTransportError: transport/connectivity problems.CodexTimeoutError: request timeout (and base for timeout-related flow).CodexTurnInactiveError: per-turn inactivity timeout with resumablecontinuation.CodexProtocolError: protocol/JSON-RPC error (optionalcodeanddata).
Behavior notes
- This version does not expose token-delta streaming as a public API.
chat(...)provides async streaming of completed step blocks (non-delta) from liveitem/completednotifications only.chat(...)intentionally does not mergethread/readsnapshot items for the same turn, avoiding duplicate blocks when snapshot item IDs differ from live event item IDs.chat_once(...)resolves final text from completedagentMessageitems (item/completed), withthread/read(includeTurns=true)fallback.turn_timeoutis intentionally removed to avoid conflicting timeout semantics.- Turn waits are controlled by
inactivity_timeout(or unbounded whenNone). cancel(...)releases turn state only after a terminal event. RPC failures propagate; a confirmation timeout raisesCodexTurnInactiveErrorwith the original continuation.- Failed or interrupted turns raise
CodexProtocolErrorfrom both chat APIs, even if partial assistant text was received. - Use
approval_mode="manual"on either connection factory to answerapproval_requests()yourself. Without a callback, the default"auto"mode declines requests. - Advanced thread-level config/fork uses protocol v2 methods (
thread/start,thread/resume,thread/fork) exposed viaThreadHandleandThreadConfig. metadatais applied onturn/startpayloads for message turns; thread-level config uses schema-aligned fields on thread methods.- preferred lifecycle is
async with CodexClient.connect_*() as client:; manualstart()/close()remains available for advanced control. - The client uses modern thread/turn methods (
thread/start,thread/resume,turn/start,turn/interrupt). initializecurrently sendsprotocolVersion: "1"as handshake metadata.- Websocket transport targets
websockets(>=16,<17), usesadditional_headers, and disables compression by default (compression=None) for codex app-server compatibility. - After dependency changes, run
uv syncto refresh the virtual environment.
Initialize handshake (initialize())
initialize() performs the protocol handshake and returns InitializeResult.
chat_once(...)andchat(...)callinitialize()automatically on first use.- call
initialize()explicitly when you want to fail fast before first turn, inspect server metadata, or send custom init params.
Default initialize payload
When params=None, the client sends the following payload. The version
placeholder is replaced with the installed package version, also available as
codex_app_server_sdk.__version__:
{
"protocolVersion": "1",
"clientInfo": {
"name": "codex-app-server-sdk",
"version": "<installed SDK version>"
},
"capabilities": {
"optOutNotificationMethods": [
"codex/event/agent_message_content_delta",
"codex/event/reasoning_content_delta",
"codex/event/item_started",
"codex/event/item_completed",
"codex/event/task_started",
"codex/event/task_complete"
]
}
}
Custom init params (initialize(params=...))
Supported/customizable keys:
protocolVersion: strclientInfo: dict(commonlyname,version, plus optional extra fields)capabilities: dictcapabilities.optOutNotificationMethods: list[str]- any additional top-level keys are passed through unchanged
Merge rules:
- the payload starts from the default block above;
- caller
paramsare shallow-merged at top level; - if caller provides
capabilitiesas a dict and omitsoptOutNotificationMethods, defaults are auto-injected; - if caller provides
capabilities.optOutNotificationMethods, caller value is preserved; - if caller sets
capabilitiestoNoneor a non-dict value, no injection is applied.
InitializeResult fields
protocol_version: extracted fromprotocolVersionorprotocol_versionin server resultserver_info: extracted fromserverInfoorserver_infocapabilities: extracted fromcapabilitiesraw: full raw initialize result payload
Example: explicit initialize
The custom clientInfo.version below identifies your application, independently
of the SDK version.
import asyncio
from codex_app_server_sdk import CodexClient
async def main() -> None:
async with CodexClient.connect_stdio() as client:
init = await client.initialize(
{
"clientInfo": {
"name": "my-client",
"version": "0.3.0",
},
"capabilities": {
"optOutNotificationMethods": [
"codex/event/agent_message_content_delta"
]
},
}
)
print(init.protocol_version)
asyncio.run(main())
Release files for codex-app-server-sdk 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| codex_app_server_sdk-0.4.1.tar.gz | 179.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codex_app_server_sdk-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 240.2 kB
Release files / codex_app_server_sdk-0.4.1.tar.gz
| Download URL | codex_app_server_sdk-0.4.1.tar.gz |
|---|---|
| Size | 179.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4031187a8fb09048749eade9af1013723ddc7d9beb7e1eee5fc9f25ec777b729
|
|
BLAKE2b-256 checksum How to use checksums |
0f03a010f02ecca71430c72f82eb35b00cb69845cbf7007c855edb2b665aecf4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency logRelease files / codex_app_server_sdk-0.4.1-py3-none-any.whl
| Download URL | codex_app_server_sdk-0.4.1-py3-none-any.whl |
|---|---|
| Size | 61.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
55a1c10d94d6c43008ecf09dc677ac10fc9ed111f28b4b9e3de6f8135e374d8b
|
|
BLAKE2b-256 checksum How to use checksums |
9c79065f12e3cf8eb3212f46eef92b52124cddb0fdd7cb49e11a87cc991c919f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 23, 2026.
Transparency log