80 Commits

• test: faster test execution in codex-core (#2633)

  this dramatically improves time to run `cargo test -p codex-core` (~25x
  speedup).
  
  before:
  ```
  cargo test -p codex-core  35.96s user 68.63s system 19% cpu 8:49.80 total
  ```
  
  after:
  ```
  cargo test -p codex-core  5.51s user 8.16s system 63% cpu 21.407 total
  ```
  
  both tests measured "hot", i.e. on a 2nd run with no filesystem changes,
  to exclude compile times.
  
  approach inspired by [Delete Cargo Integration
  Tests](https://matklad.github.io/2021/02/27/delete-cargo-integration-tests.html),
  we move all test cases in tests/ into a single suite in order to have a
  single binary, as there is significant overhead for each test binary
  executed, and because test execution is only parallelized with a single
  binary.

  Jeremy Rose · 2025-08-24 11:10:53 -07:00
  32bbbbad61
• send-aggregated output (#2364)

  We want to send an aggregated output of stderr and stdout so we don't
  have to aggregate it stderr+stdout as we lose order sometimes.
  
  ---------
  
  Co-authored-by: Gabriel Peal <gpeal@users.noreply.github.com>

  Ahmed Ibrahim · 2025-08-23 16:54:31 +00:00
  957d44918d
• [apply_patch] freeform apply_patch tool (#2576)

  ## Summary
  GPT-5 introduced the concept of [custom
  tools](https://platform.openai.com/docs/guides/function-calling#custom-tools),
  which allow the model to send a raw string result back, simplifying
  json-escape issues. We are migrating gpt-5 to use this by default.
  
  However, gpt-oss models do not support custom tools, only normal
  functions. So we keep both tool definitions, and provide whichever one
  the model family supports.
  
  ## Testing
  - [x] Tested locally with various models
  - [x] Unit tests pass

  Dylan · 2025-08-22 13:42:34 -07:00
  236c4f76a6
• Add AuthManager and enhance GetAuthStatus command (#2577)

  This PR adds a central `AuthManager` struct that manages the auth
  information used across conversations and the MCP server. Prior to this,
  each conversation and the MCP server got their own private snapshots of
  the auth information, and changes to one (such as a logout or token
  refresh) were not seen by others.
  
  This is especially problematic when multiple instances of the CLI are
  run. For example, consider the case where you start CLI 1 and log in to
  ChatGPT account X and then start CLI 2 and log out and then log in to
  ChatGPT account Y. The conversation in CLI 1 is still using account X,
  but if you create a new conversation, it will suddenly (and
  unexpectedly) switch to account Y.
  
  With the `AuthManager`, auth information is read from disk at the time
  the `ConversationManager` is constructed, and it is cached in memory.
  All new conversations use this same auth information, as do any token
  refreshes.
  
  The `AuthManager` is also used by the MCP server's GetAuthStatus
  command, which now returns the auth method currently used by the MCP
  server.
  
  This PR also includes an enhancement to the GetAuthStatus command. It
  now accepts two new (optional) input parameters: `include_token` and
  `refresh_token`. Callers can use this to request the in-use auth token
  and can optionally request to refresh the token.
  
  The PR also adds tests for the login and auth APIs that I recently added
  to the MCP server.

  Eric Traut · 2025-08-22 13:10:11 -07:00
  dc42ec0eb4
• [apply-patch] Clean up apply-patch tool definitions (#2539)

  ## Summary
  We've experienced a bit of drift in system prompting for `apply_patch`:
  - As pointed out in #2030 , our prettier formatting started altering
  prompt.md in a few ways
  - We introduced a separate markdown file for apply_patch instructions in
  #993, but currently duplicate them in the prompt.md file
  - We added a first-class apply_patch tool in #2303, which has yet
  another definition
  
  This PR starts to consolidate our logic in a few ways:
  - We now only use
  `apply_patch_tool_instructions.md](https://github.com/openai/codex/compare/dh--apply-patch-tool-definition?expand=1#diff-d4fffee5f85cb1975d3f66143a379e6c329de40c83ed5bf03ffd3829df985bea)
  for system instructions
  - We no longer include apply_patch system instructions if the tool is
  specified
  
  I'm leaving the definition in openai_tools.rs as duplicated text for now
  because we're going to be iterated on the first-class tool soon.
  
  ## Testing
  - [x] Added integration tests to verify prompt stability
  - [x] Tested locally with several different models (gpt-5, gpt-oss,
  o4-mini)

  Dylan · 2025-08-21 20:07:41 -07:00
  e4c275d615
• [prompt] xml-format EnvironmentContext (#2272)

  ## Summary
  Before we land #2243, let's start printing environment_context in our
  preferred format. This struct will evolve over time with new
  information, xml gives us a balance of human readable without too much
  parsing, llm readable, and extensible.
  
  Also moves us over to an Option-based struct, so we can easily provide
  diffs to the model.
  
  ## Testing
  - [x] Updated tests to reflect new format

  Dylan · 2025-08-20 23:45:16 -07:00
  d2b2a6d13a
• Bridge command generation to powershell when on Windows (#2319)

  ## What? Why? How?
  - When running on Windows, codex often tries to invoke bash commands,
  which commonly fail (unless WSL is installed)
  - Fix: Detect if powershell is available and, if so, route commands to
  it
  - Also add a shell_name property to environmental context for codex to
  default to powershell commands when running in that environment
  
  ## Testing
  - Tested within WSL and powershell (e.g. get top 5 largest files within
  a folder and validated that commands generated were powershell commands)
  - Tested within Zsh
  - Updated unit tests
  
  ---------
  
  Co-authored-by: Eddy Escardo <eddy@openai.com>

  eddy-win · 2025-08-20 16:30:34 -07:00
  050b9baeb6
• fix: prefer config var to env var (#2495)
  Michael Bolin · 2025-08-20 04:51:59 +00:00
  ce434b1219
• chore: upgrade to Rust 1.89 (#2465)

  Codex created this PR from the following prompt:
  
  > upgrade this entire repo to Rust 1.89. Note that this requires
  updating codex-rs/rust-toolchain.toml as well as the workflows in
  .github/. Make sure that things are "clippy clean" as this change will
  likely uncover new Clippy errors. `just fmt` and `cargo clippy --tests`
  are sufficient to check for correctness
  
  Note this modifies a lot of lines because it folds nested `if`
  statements using `&&`.
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/2465).
  * #2467
  * __->__ #2465

  Michael Bolin · 2025-08-19 13:22:02 -07:00
  50c48e88f5
• Show login options when not signed in with ChatGPT (#2440)

  Motivation: we have users who uses their API key although they want to
  use ChatGPT account. We want to give them the chance to always login
  with their account.
  
  This PR displays login options when the user is not signed in with
  ChatGPT. Even if you have set an OpenAI API key as an environment
  variable, you will still be prompted to log in with ChatGPT.
  
  We’ve also added a new flag, `always_use_api_key_signing` false by
  default, which ensures you are never asked to log in with ChatGPT and
  always defaults to using your API key.
  
  
  
  https://github.com/user-attachments/assets/b61ebfa9-3c5e-4ab7-bf94-395c23a0e0af
  
  After ChatGPT sign in:
  
  
  https://github.com/user-attachments/assets/d58b366b-c46a-428f-a22f-2ac230f991c0

  Ahmed Ibrahim · 2025-08-19 03:22:48 +00:00
  97f995a749
• Add cache tests for UserTurn (#2432)
  Ahmed Ibrahim · 2025-08-18 21:28:09 +00:00
  ecb388045c
• Add an operation to override current task context (#2431)

  - Added an operation to override current task context
  - Added a test to check that cache stays the same

  Ahmed Ibrahim · 2025-08-18 19:59:19 +00:00
  c283f9f6ce
• [tools] Add apply_patch tool (#2303)

  ## Summary
  We've been seeing a number of issues and reports with our synthetic
  `apply_patch` tool, e.g. #802. Let's make this a real tool - in my
  anecdotal testing, it's critical for GPT-OSS models, but I'd like to
  make it the standard across GPT-5 and codex models as well.
  
  ## Testing
  - [x] Tested locally
  - [x] Integration test

  Dylan · 2025-08-15 11:55:53 -04:00
  6df8e35314
• Added allow-expect-in-tests / allow-unwrap-in-tests (#2328)

  This PR:
  * Added the clippy.toml to configure allowable expect / unwrap usage in
  tests
  * Removed as many expect/allow lines as possible from tests
  * moved a bunch of allows to expects where possible
  
  Note: in integration tests, non `#[test]` helper functions are not
  covered by this so we had to leave a few lingering `expect(expect_used`
  checks around

  Parker Thompson · 2025-08-14 17:59:01 -07:00
  a075424437
• fix: run python_multiprocessing_lock_works integration test on Mac and Linux (#2318)

  The high-order bit on this PR is that it makes it so `sandbox.rs` tests
  both Mac and Linux, as we introduce a general
  `spawn_command_under_sandbox()` function with platform-specific
  implementations for testing.
  
  An important, and interesting, discovery in porting the test to Linux is
  that (for reasons cited in the code comments), `/dev/shm` has to be
  added to `writable_roots` on Linux in order for `multiprocessing.Lock`
  to work there. Granting write access to `/dev/shm` comes with some
  degree of risk, so we do not make this the default for Codex CLI.
  
  Piggybacking on top of #2317, this moves the
  `python_multiprocessing_lock_works` test yet again, moving
  `codex-rs/core/tests/sandbox.rs` to `codex-rs/exec/tests/sandbox.rs`
  because in `codex-rs/exec/tests` we can use `cargo_bin()` like so:
  
  ```
  let codex_linux_sandbox_exe = assert_cmd::cargo::cargo_bin("codex-exec");
  ```
  
  which is necessary so we can use `codex_linux_sandbox_exe` and therefore
  `spawn_command_under_linux_sandbox` in an integration test.
  
  This also moves `spawn_command_under_linux_sandbox()` out of `exec.rs`
  and into `landlock.rs`, which makes things more consistent with
  `seatbelt.rs` in `codex-core`.
  
  For reference, https://github.com/openai/codex/pull/1808 is the PR that
  made the change to Seatbelt to get this test to pass on Mac.

  Michael Bolin · 2025-08-14 15:47:48 -07:00
  2ecca79663
• fix: move general sandbox tests to codex-rs/core/tests/sandbox.rs (#2317)

  Previous to this PR, `codex-rs/core/tests/sandbox.rs` contained
  integration tests that were specific to Seatbelt. This PR moves those
  tests to `codex-rs/core/src/seatbelt.rs` and designates
  `codex-rs/core/tests/sandbox.rs` to be used as the home for
  cross-platform (well, Mac and Linux...) sandbox tests.
  
  To start, this migrates
  `python_multiprocessing_lock_works_under_seatbelt()` from #1823 to the
  new `sandbox.rs` because this is the type of thing that should work on
  both Mac _and_ Linux, though I still need to do some work to clean up
  the test so it works on both platforms.

  Michael Bolin · 2025-08-14 14:48:38 -07:00
  a8c7f5391c
• [context] Store context messages in rollouts (#2243)

  ## Summary
  Currently, we use request-time logic to determine the user_instructions
  and environment_context messages. This means that neither of these
  values can change over time as conversations go on. We want to add in
  additional details here, so we're migrating these to save these messages
  to the rollout file instead. This is simpler for the client, and allows
  us to append additional environment_context messages to each turn if we
  want
  
  ## Testing
  - [x] Integration test coverage
  - [x] Tested locally with a few turns, confirmed model could reference
  environment context and cached token metrics were reasonably high

  Dylan · 2025-08-14 14:51:13 -04:00
  544980c008
• chore: introduce ConversationManager as a clearinghouse for all conversations (#2240)

  This PR does two things because after I got deep into the first one I
  started pulling on the thread to the second:
  
  - Makes `ConversationManager` the place where all in-memory
  conversations are created and stored. Previously, `MessageProcessor` in
  the `codex-mcp-server` crate was doing this via its `session_map`, but
  this is something that should be done in `codex-core`.
  - It unwinds the `ctrl_c: tokio::sync::Notify` that was threaded
  throughout our code. I think this made sense at one time, but now that
  we handle Ctrl-C within the TUI and have a proper `Op::Interrupt` event,
  I don't think this was quite right, so I removed it. For `codex exec`
  and `codex proto`, we now use `tokio::signal::ctrl_c()` directly, but we
  no longer make `Notify` a field of `Codex` or `CodexConversation`.
  
  Changes of note:
  
  - Adds the files `conversation_manager.rs` and `codex_conversation.rs`
  to `codex-core`.
  - `Codex` and `CodexSpawnOk` are no longer exported from `codex-core`:
  other crates must use `CodexConversation` instead (which is created via
  `ConversationManager`).
  - `core/src/codex_wrapper.rs` has been deleted in favor of
  `ConversationManager`.
  - `ConversationManager::new_conversation()` returns `NewConversation`,
  which is in line with the `new_conversation` tool we want to add to the
  MCP server. Note `NewConversation` includes `SessionConfiguredEvent`, so
  we eliminate checks in cases like `codex-rs/core/tests/client.rs` to
  verify `SessionConfiguredEvent` is the first event because that is now
  internal to `ConversationManager`.
  - Quite a bit of code was deleted from
  `codex-rs/mcp-server/src/message_processor.rs` since it no longer has to
  manage multiple conversations itself: it goes through
  `ConversationManager` instead.
  - `core/tests/live_agent.rs` has been deleted because I had to update a
  bunch of tests and all the tests in here were ignored, and I don't think
  anyone ever ran them, so this was just technical debt, at this point.
  - Removed `notify_on_sigint()` from `util.rs` (and in a follow-up, I
  hope to refactor the blandly-named `util.rs` into more descriptive
  files).
  - In general, I started replacing local variables named `codex` as
  `conversation`, where appropriate, though admittedly I didn't do it
  through all the integration tests because that would have added a lot of
  noise to this PR.
  
  
  
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/2240).
  * #2264
  * #2263
  * __->__ #2240

  Michael Bolin · 2025-08-13 13:38:18 -07:00
  08ed618f72
• Re-add markdown streaming (#2029)

  Wait for newlines, then render markdown on a line by line basis. Word wrap it for the current terminal size and then spit it out line by line into the UI. Also adds tests and fixes some UI regressions.

  easong-openai · 2025-08-12 17:37:28 -07:00
  6340acd885
• [prompts] integration test prompt caching (#2189)

  ## Summary
  Our current approach to prompt caching is fragile! The current approach
  works, but we are planning to update to a more resilient system (storing
  them in the rollout file). Let's start adding some integration tests to
  ensure stability while we migrate it.
  
  ## Testing
  - [x] These are the tests 😎

  Dylan · 2025-08-11 17:03:13 -07:00
  d33793d31d
• Include output truncation message in tool call results (#2183)

  To avoid model being confused about incomplete output.

  pakrym-oai · 2025-08-11 11:52:05 -07:00
  0cf57e1f42
• [core] Allow resume after client errors (#2053)

  ## Summary
  Allow tui conversations to resume after the client fails out of retries.
  I tested this with exec / mocked api failures as well, and it appears to
  be fine. But happy to add an exec integration test as well!
  
  ## Testing
  - [x] Added integration test
  - [x] Tested locally

  Dylan · 2025-08-08 18:21:19 -07:00
  0091930f5a
• chore: change CodexAuth::from_api_key() to take &str instead of String (#1970)

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

  Michael Bolin · 2025-08-07 16:55:33 -07:00
  295abf3e51
• chore: rename CodexAuth::new() to create_dummy_codex_auth_for_testing() because it is not for general consumption (#1962)

  `CodexAuth::new()` was the first method listed in `CodexAuth`, but it is
  only meant to be used by tests. Rename it to
  `create_dummy_chatgpt_auth_for_testing()` and move it to the end of the
  implementation.
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/1962).
  * #1971
  * #1970
  * #1966
  * #1965
  * __->__ #1962

  Michael Bolin · 2025-08-07 16:33:29 -07:00
  db76f32888
• feat: parse info from auth.json and show in /status (#1923)

  - `/status` renders
      ```
      signed in with chatgpt
        login: example@example.com
        plan: plus
      ```
  - Setup for using this info in a few more places.
  
  ---------
  
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  ae · 2025-08-07 01:27:45 -07:00
  0334476894
• feat: add /tmp by default (#1919)

  Replaces the `include_default_writable_roots` option on
  `sandbox_workspace_write` (that defaulted to `true`, which was slightly
  weird/annoying) with `exclude_tmpdir_env_var`, which defaults to
  `false`.
  
  Though perhaps more importantly `/tmp` is now enabled by default as part
  of `sandbox_mode = "workspace-write"`, though `exclude_slash_tmp =
  false` can be used to disable this.

  Michael Bolin · 2025-08-07 00:17:00 -07:00
  cd5f9074af
• Prefer env var auth over default codex auth (#1861)

  ## Summary
  - Prioritize provider-specific API keys over default Codex auth when
  building requests
  - Add test to ensure provider env var auth overrides default auth
  
  ## Testing
  - `just fmt`
  - `just fix` *(fails: `let` expressions in this position are unstable)*
  - `cargo test --all-features` *(fails: `let` expressions in this
  position are unstable)*
  
  ------
  https://chatgpt.com/codex/tasks/task_i_68926a104f7483208f2c8fd36763e0e3

  pakrym-oai · 2025-08-06 13:02:00 -07:00
  8262ba58b2
• [prompts] Add <environment_context> (#1869)

  ## Summary
  Includes a new user message in the api payload which provides useful
  environment context for the model, so it knows about things like the
  current working directory and the sandbox.
  
  ## Testing
  Updated unit tests

  Dylan · 2025-08-06 01:13:31 -07:00
  3e8bcf0247
• [approval_policy] Add OnRequest approval_policy (#1865)

  ## Summary
  A split-up PR of #1763 , stacked on top of a tools refactor #1858 to
  make the change clearer. From the previous summary:
  
  > Let's try something new: tell the model about the sandbox, and let it
  decide when it will need to break the sandbox. Some local testing
  suggests that it works pretty well with zero iteration on the prompt!
  
  ## Testing
  - [x] Added unit tests
  - [x] Tested locally and it appears to work smoothly!

  Dylan · 2025-08-05 20:44:20 -07:00
  725dd6be6a
• [prompts] Better user_instructions handling (#1836)

  ## Summary
  Our recent change in #1737 can sometimes lead to the model confusing
  AGENTS.md context as part of the message. But a little prompting and
  formatting can help fix this!
  
  ## Testing
  - Ran locally with a few different prompts to verify the model
  behaves well.
  - Updated unit tests

  Dylan · 2025-08-04 18:55:57 -07:00
  063083af15
• Restore API key and query param overrides (#1826)

  Addresses https://github.com/openai/codex/issues/1796

  pakrym-oai · 2025-08-04 18:07:49 -07:00
  84bcadb8d9
• [sandbox] Filter out certain non-sandbox errors (#1804)

  ## Summary
  Users frequently complain about re-approving commands that have failed
  for non-sandbox reasons. We can't diagnose with complete accuracy which
  errors happened because of a sandbox failure, but we can start to
  eliminate some common simple cases.
  
  This PR captures the most common case I've seen, which is a `command not
  found` error.
  
  ## Testing
  - [x] Added unit tests
  - [x] Ran a few cases locally

  Dylan · 2025-08-03 13:05:48 -07:00
  e3565a3f43
• fix command duration display (#1806)

  we were always displaying "0ms" before.
  
  <img width="731" height="101" alt="Screenshot 2025-08-02 at 10 51 22 PM"
  src="https://github.com/user-attachments/assets/f56814ed-b9a4-4164-9e78-181c60ce19b7"
  />

  Jeremy Rose · 2025-08-03 11:33:44 -07:00
  78a1d49fac
• feat: make .git read-only within a writable root when using Seatbelt (#1765)

  To make `--full-auto` safer, this PR updates the Seatbelt policy so that
  a `SandboxPolicy` with a `writable_root` that contains a `.git/`
  _directory_ will make `.git/` _read-only_ (though as a follow-up, we
  should also consider the case where `.git` is a _file_ with a `gitdir:
  /path/to/actual/repo/.git` entry that should also be protected).
  
  The two major changes in this PR:
  
  - Updating `SandboxPolicy::get_writable_roots_with_cwd()` to return a
  `Vec<WritableRoot>` instead of a `Vec<PathBuf>` where a `WritableRoot`
  can specify a list of read-only subpaths.
  - Updating `create_seatbelt_command_args()` to honor the read-only
  subpaths in `WritableRoot`.
  
  The logic to update the policy is a fairly straightforward update to
  `create_seatbelt_command_args()`, but perhaps the more interesting part
  of this PR is the introduction of an integration test in
  `tests/sandbox.rs`. Leveraging the new API in #1785, we test
  `SandboxPolicy` under various conditions, including ones where `$TMPDIR`
  is not readable, which is critical for verifying the new behavior.
  
  To ensure that Codex can run its own tests, e.g.:
  
  ```
  just codex debug seatbelt --full-auto -- cargo test if_git_repo_is_writable_root_then_dot_git_folder_is_read_only
  ```
  
  I had to introduce the use of `CODEX_SANDBOX=sandbox`, which is
  comparable to how `CODEX_SANDBOX_NETWORK_DISABLED=1` was already being
  used.
  
  Adding a comparable change for Landlock will be done in a subsequent PR.

  Michael Bolin · 2025-08-01 16:11:24 -07:00
  80555d4ff2
• collabse stdout and stderr delta events into one (#1787)
  aibrahim-oai · 2025-08-01 14:00:19 -07:00
  f20de21cb6
• feat: stream exec stdout events (#1786)

  ## Summary
  - stream command stdout as `ExecCommandStdout` events
  - forward streamed stdout to clients and ignore in human output
  processor
  - adjust call sites for new streaming API

  aibrahim-oai · 2025-08-01 13:04:34 -07:00
  bc7beddaa2
• Add a custom originator setting (#1781)
  pakrym-oai · 2025-08-01 09:55:23 -07:00
  88ea215c80
• ci fix (#1782)
  aibrahim-oai · 2025-08-01 09:17:13 -07:00
  b67c485d84
• Add /compact (#1527)

  - Add operation to summarize the context so far.
  - The operation runs a compact task that summarizes the context.
  - The operation clear the previous context to free the context window
  - The operation didn't use `run_task` to avoid corrupting the session
  - Add /compact in the tui
  
  
  
  https://github.com/user-attachments/assets/e06c24e5-dcfb-4806-934a-564d425a919c

  aibrahim-oai · 2025-07-31 21:34:32 -07:00
  e2c994e32a
• Send account id when available (#1767)

  For users with multiple accounts we need to specify the account to use.

  pakrym-oai · 2025-07-31 15:40:19 -07:00
  0935e6a875
• chore: refactor exec.rs: create separate seatbelt.rs and spawn.rs files (#1762)

  At 550 lines, `exec.rs` was a bit large. In particular, I found it hard
  to locate the Seatbelt-related code quickly without a file with
  `seatbelt` in the name, so this refactors things so:
  
  - `spawn_command_under_seatbelt()` and dependent code moves to a new
  `seatbelt.rs` file
  - `spawn_child_async()` and dependent code moves to a new `spawn.rs`
  file

  Michael Bolin · 2025-07-31 13:11:47 -07:00
  5a0ad5ab8f
• Add codex login --api-key (#1759)

  Allow setting the API key via `codex login --api-key`

  pakrym-oai · 2025-07-31 17:48:49 +00:00
  549846b29a
• fix git tests (#1747)

  the git tests were failing on my local machine due to gpg signing config
  in my ~/.gitconfig. tests should not be affected by ~/.gitconfig, so
  configure them to ignore it.

  Jeremy Rose · 2025-07-31 09:17:59 -07:00
  be0cd34300
• Send AGENTS.md as a separate user message (#1737)
  pakrym-oai · 2025-07-30 13:56:24 -07:00
  e0e245cc1c
• Add support for a separate chatgpt auth endpoint (#1712)

  Adds a `CodexAuth` type that encapsulates information about available
  auth modes and logic for refreshing the token.
  Changes `Responses` API to send requests to different endpoints based on
  the auth type.
  Updates login_with_chatgpt to support API-less mode and skip the key
  exchange.

  pakrym-oai · 2025-07-30 19:40:15 +00:00
  ea01a5ffe2
• Relative instruction file (#1722)

  Passing in an instruction file with a bad path led to silent failures,
  also instruction relative paths were handled in an unintuitive fashion.

  easong-openai · 2025-07-29 10:06:05 -07:00
  f8fcaaaf6f
• chore: update Codex::spawn() to return a struct instead of a tuple (#1677)

  Also update `init_codex()` to return a `struct` instead of a tuple, as well.

  Michael Bolin · 2025-07-27 20:01:35 -07:00
  2405c40026
• fix: create separate test_support crates to eliminate #[allow(dead_code)] (#1667)

  Because of a quirk of how implementation tests work in Rust, we had a
  number of `#[allow(dead_code)]` annotations that were misleading because
  the functions _were_ being used, just not by all integration tests in a
  `tests/` folder, so when compiling the test that did not use the
  function, clippy would complain that it was unused.
  
  This fixes things by create a "test_support" crate under the `tests/`
  folder that is imported as a dev dependency for the respective crate.

  Michael Bolin · 2025-07-24 12:19:46 -07:00
  7af9cedbd7
• Record Git metadata to rollout (#1598)

  # Summary
  
  - Writing effective evals for codex sessions requires context of the
  overall repository state at the moment the session began
  - This change adds this metadata (git repository, branch, commit hash)
  to the top of the rollout of the session (if available - if not it
  doesn't add anything)
  - Currently, this is only effective on a clean working tree, as we can't
  track uncommitted/untracked changes with the current metadata set.
  Ideally in the future we may want to track unclean changes somehow, or
  perhaps prompt the user to stash or commit them.
  
  # Testing
  - Added unit tests
  - `cargo test && cargo clippy --tests && cargo fmt -- --config
  imports_granularity=Item`
  
  ### Resulting Rollout
  <img width="1243" height="127" alt="Screenshot 2025-07-17 at 1 50 00 PM"
  src="https://github.com/user-attachments/assets/68108941-f015-45b2-985c-ea315ce05415"
  />

  vishnu-oai · 2025-07-24 11:35:28 -07:00
  2437a8d17a
• Always send entire request context (#1641)

  Always store the entire conversation history.
  Request encrypted COT when not storing Responses.
  Send entire input context instead of sending previous_response_id

  pakrym-oai · 2025-07-23 10:37:45 -07:00
  591cb6149a