## Why The SDK package root should be the ergonomic public client API, not a dump of every generated app-server schema type. Generated models still need a supported import path, but callers should be able to tell which names are high-level SDK entrypoints and which names are protocol value models. ## What - Define a curated root `__all__` for clients, handles, input helpers, retry helpers, config, and public errors. - Add a `types` module as the supported home for generated app-server response, event, enum, and helper models. - Update docs and examples to import protocol/value models from the type module. - Add tests that lock root exports, type-module exports, star-import behavior, and example import hygiene. ## Stack 1. #21891 `[1/8]` Pin Python SDK runtime dependency 2. #21893 `[2/8]` Generate Python SDK types from pinned runtime 3. #21895 `[3/8]` Run Python SDK tests in CI 4. This PR `[4/8]` Define Python SDK public API surface 5. #21905 `[5/8]` Rename Python SDK package to `openai-codex` 6. #21910 `[6/8]` Add high-level Python SDK approval mode 7. #22014 `[7/8]` Add Python SDK app-server integration harness 8. #22021 `[8/8]` Add Python SDK Ruff formatting ## Verification - Added public API signature tests for root exports, `types` exports, and example imports. --------- Co-authored-by: Codex <noreply@openai.com>
3.7 KiB
FAQ
Thread vs turn
- A
Threadis conversation state. - A
Turnis one model execution inside that thread. - Multi-turn chat means multiple turns on the same
Thread.
run() vs stream()
TurnHandle.run()/AsyncTurnHandle.run()is the easiest path. It consumes events until completion and returns the public app-serverTurnmodel fromcodex_app_server.types.TurnHandle.stream()/AsyncTurnHandle.stream()yields raw notifications (Notification) so you can react event-by-event.
Choose run() for most apps. Choose stream() for progress UIs, custom timeout logic, or custom parsing.
Sync vs async clients
Codexis the sync public API.AsyncCodexis an async replica of the same public API shape.- Prefer
async with AsyncCodex()for async code. It is the standard path for explicit startup/shutdown, andAsyncCodexinitializes lazily on context entry or first awaited API use.
If your app is not already async, stay with Codex.
Public kwargs are snake_case
Public API keyword names are snake_case. The SDK still maps them to wire camelCase under the hood.
If you are migrating older code, update these names:
approvalPolicy->approval_policybaseInstructions->base_instructionsdeveloperInstructions->developer_instructionsmodelProvider->model_providermodelProviders->model_providerssortKey->sort_keysourceKinds->source_kindsoutputSchema->output_schemasandboxPolicy->sandbox_policy
Why only thread_start(...) and thread_resume(...)?
The public API keeps only explicit lifecycle calls:
thread_start(...)to create new threadsthread_resume(thread_id, ...)to continue existing threads
This avoids duplicate ways to do the same operation and keeps behavior explicit.
Why does constructor fail?
Codex() is eager: it starts transport and calls initialize in __init__.
Common causes:
- published runtime package (
openai-codex-cli-bin) is not installed - local
codex_binoverride points to a missing file - local auth/session is missing
- incompatible/old app-server
Maintainers stage releases by building the SDK once and the runtime once per
platform with the same pinned runtime version. Publish openai-codex-cli-bin
as platform wheels only; do not publish an sdist:
cd sdk/python
python scripts/update_sdk_artifacts.py generate-types
python scripts/update_sdk_artifacts.py \
stage-sdk \
/tmp/codex-python-release/openai-codex-app-server-sdk \
--codex-version <codex-release-tag-or-pep440-version>
python scripts/update_sdk_artifacts.py \
stage-runtime \
/tmp/codex-python-release/openai-codex-cli-bin \
/path/to/codex \
--codex-version <codex-release-tag-or-pep440-version>
If you are packaging a binary for a different target than the Python build
host, pass --platform-tag ... to stage-runtime. The intended one-off matrix
is macosx_11_0_arm64, macosx_10_9_x86_64, musllinux_1_1_aarch64,
musllinux_1_1_x86_64, win_arm64, and win_amd64.
Why does a turn "hang"?
A turn is complete only when turn/completed arrives for that turn ID.
run()waits for this automatically.- With
stream(), keep consuming notifications until completion.
How do I retry safely?
Use retry_on_overload(...) for transient overload failures (ServerBusyError).
Do not blindly retry all errors. For InvalidParamsError or MethodNotFoundError, fix inputs/version compatibility instead.
Common pitfalls
- Starting a new thread for every prompt when you wanted continuity.
- Forgetting to
close()(or not using context managers). - Assuming
run()returns extra SDK-only fields instead of the publicTurnmodel. - Mixing SDK input classes with raw dicts incorrectly.