Files

Michael Bolin b991c04f86 chore: move top-level load_auth() to CodexAuth::from_codex_home() (#1966 )

There are two valid ways to create an instance of `CodexAuth`:
`from_api_key()` and `from_codex_home()`. Now both are static methods of
`CodexAuth` and are listed first in the implementation.

---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed
with [ReviewStack](https://reviewstack.dev/openai/codex/pull/1966).
* #1971
* #1970
* __->__ #1966
* #1965
* #1962

2025-08-07 16:49:37 -07:00

src

chore: move top-level load_auth() to CodexAuth::from_codex_home() (#1966 )

2025-08-07 16:49:37 -07:00

tests

chore: rename CodexAuth::new() to create_dummy_codex_auth_for_testing() because it is not for general consumption (#1962 )

2025-08-07 16:33:29 -07:00

Cargo.toml

[config] Onboarding flow with persistence (#1929 )

2025-08-07 09:27:38 -07:00

prompt.md

feat: update system prompt (#1939 )

2025-08-07 04:29:50 -07:00

README.md

fix: support special --codex-run-as-apply-patch arg (#1702 )

2025-07-28 09:26:44 -07:00

README.md

codex-core

This crate implements the business logic for Codex. It is designed to be used by the various Codex UIs written in Rust.

Dependencies

Note that codex-core makes some assumptions about certain helper utilities being available in the environment. Currently, this

macOS

Expects /usr/bin/sandbox-exec to be present.

Linux

Expects the binary containing codex-core to run the equivalent of codex debug landlock when arg0 is codex-linux-sandbox. See the codex-arg0 crate for details.

All Platforms

Expects the binary containing codex-core to simulate the virtual apply_patch CLI when arg1 is --codex-run-as-apply-patch. See the codex-arg0 crate for details.