OpenAI Codex SDK (Python)
Embed the Codex agent in your workflows and apps.
This SDK wraps the bundled codex binary. It spawns the CLI and exchanges JSONL events over stdin/stdout.
Installation
pip install openai-codex-sdk
Requires Python 3.10+.
Installing the Codex CLI binary (notebooks/containers)
This package does not ship the codex binary by default. In environments like notebooks or containers,
install it explicitly:
from openai_codex_sdk import Codex
# Downloads a Codex CLI release asset and installs into:
# openai_codex_sdk/vendor/<target-triple>/codex/<codex|codex.exe>
Codex.install(version="rust-v0.88.0-alpha.3")
# If you hit glibc compatibility issues in containers, prefer the musl build:
# Codex.install(
# version="rust-v0.88.0-alpha.3",
# filename="codex-x86_64-unknown-linux-musl.tar.gz",
# overwrite=True,
# )
Writing auth.json (notebooks/containers)
If your environment provides the Codex CLI credentials as a secret (for example an env var containing the JSON
string), write the auth file the Codex CLI expects at ~/.codex/auth.json:
from openai_codex_sdk import Codex
# Reads from CODEX_AUTH_JSON by default
Codex.login_with_auth_json(overwrite=True)
Device code login (local terminals)
To authenticate interactively, start the device login flow and follow the printed instructions:
from openai_codex_sdk import Codex
Codex().login_with_device_code()
Alternatively, install codex separately and ensure it is on PATH, or set codex_path_override:
from openai_codex_sdk import Codex
codex = Codex({"codex_path_override": "/path/to/codex"})
Quickstart
import asyncio
from openai_codex_sdk import Codex
async def main():
codex = Codex()
thread = codex.start_thread()
turn = await thread.run("Diagnose the test failure and propose a fix")
print(turn.final_response)
print(turn.items)
next_turn = await thread.run("Implement the fix")
print(next_turn.final_response)
asyncio.run(main())
Streaming responses
run() buffers events until the turn finishes. To react to intermediate progress—tool calls, streaming responses,
and file change notifications—use run_streamed() instead.
import asyncio
from openai_codex_sdk import Codex
async def main():
codex = Codex()
thread = codex.start_thread()
streamed = await thread.run_streamed("Diagnose the test failure and propose a fix")
async for event in streamed.events:
if event.type == "item.completed":
print("item", event.item)
elif event.type == "turn.completed":
print("usage", event.usage)
asyncio.run(main())
Structured output
Provide output_schema on each turn as a JSON schema (a plain JSON object / Python dict):
import asyncio
from openai_codex_sdk import Codex
schema = {
"type": "object",
"properties": {
"summary": { "type": "string" },
"status": { "type": "string", "enum": ["ok", "action_required"] }
},
"required": ["summary", "status"],
"additionalProperties": False
}
async def main():
codex = Codex()
thread = codex.start_thread()
turn = await thread.run("Summarize repository status", {"output_schema": schema})
print(turn.final_response)
asyncio.run(main())
Attaching images
Provide structured input entries when you need to include images alongside text. Text entries are concatenated into
the final prompt while image entries are passed to the Codex CLI via --image.
turn = await thread.run([
{"type": "text", "text": "Describe these screenshots"},
{"type": "local_image", "path": "./ui.png"},
{"type": "local_image", "path": "./diagram.jpg"},
])
Resuming an existing thread
Threads are persisted in ~/.codex/sessions. If you lose the in-memory Thread object, reconstruct it with
resume_thread() and keep going.
saved_thread_id = os.environ["CODEX_THREAD_ID"]
thread = codex.resume_thread(saved_thread_id)
await thread.run("Implement the fix")
Working directory controls
Codex runs in the current working directory by default. To avoid unrecoverable errors, Codex requires the working
directory to be a Git repository. You can skip the Git repository check by passing skip_git_repo_check=True.
thread = codex.start_thread({
"working_directory": "/path/to/project",
"skip_git_repo_check": True,
})
Controlling the Codex CLI environment
By default, the Codex CLI inherits the Python process environment. Provide env when instantiating Codex to fully
control which variables the CLI receives.
codex = Codex({
"env": {
"PATH": "/usr/local/bin",
},
})
The SDK still injects required variables (such as OPENAI_BASE_URL and CODEX_API_KEY) on top of the environment
you provide.
Metadata
Release files for openai-codex-sdk 0.1.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openai_codex_sdk-0.1.11.tar.gz | 20.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openai_codex_sdk-0.1.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.4 kB
Release files / openai_codex_sdk-0.1.11.tar.gz
| Download URL | openai_codex_sdk-0.1.11.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2cb1ad6bc6318b419802f6f87e1cef2f3987580953d218933def281ff98929ab
|
|
BLAKE2b-256 checksum How to use checksums |
48d9601134e94b83017252d29bbffff85ed86b302ded014165edee8bf70c8558
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / openai_codex_sdk-0.1.11-py3-none-any.whl
| Download URL | openai_codex_sdk-0.1.11-py3-none-any.whl |
|---|---|
| Size | 19.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0575fd99ad3310ead661d8c6d54f5c3bb6b45a6ff99f57377f30f19ea34a3cc0
|
|
BLAKE2b-256 checksum How to use checksums |
532e72ce1e801d0ad668096c7a9250b23d0325a26fe9e6d63788ccf8ddfe3d81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for openai-codex-sdk 0.1.11
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.