72 Commits

• feat(linux-sandbox): add bwrap support (#9938)

  ## Summary
  This PR introduces a gated Bubblewrap (bwrap) Linux sandbox path. The
  curent Linux sandbox path relies on in-process restrictions (including
  Landlock). Bubblewrap gives us a more uniform filesystem isolation
  model, especially explicit writable roots with the option to make some
  directories read-only and granular network controls.
  
  This is behind a feature flag so we can validate behavior safely before
  making it the default.
  
  - Added temporary rollout flag:
    - `features.use_linux_sandbox_bwrap`
  - Preserved existing default path when the flag is off.
  - In Bubblewrap mode:
  - Added internal retry without /proc when /proc mount is not permitted
  by the host/container.

  viyatb-oai · 2026-02-04 11:13:17 -08:00
  ae4de43ccc
• chore: nuke chat/completions API (#10157)
  jif-oai · 2026-02-03 11:31:57 +00:00
  d2394a2494
• feat(tui) /permissions flow (#9561)

  ## Summary
  Adds the `/permissions` command, with a (usually) shorter set of
  permissions. `/approvals` still exists, for backwards compatibility.
  
  <img width="863" height="309" alt="Screenshot 2026-01-20 at 4 12 51 PM"
  src="https://github.com/user-attachments/assets/c49b5ba5-bc47-46dd-9067-e1a5670328fe"
  />
  
  
  ## Testing
  - [x] updated unit tests
  - [x] Tested locally

  Dylan Hurd · 2026-01-21 21:38:46 -08:00
  038b78c915
• Improve handling of config and rules errors for app server clients (#9182)

  When an invalid config.toml key or value is detected, the CLI currently
  just quits. This leaves the VSCE in a dead state.
  
  This PR changes the behavior to not quit and bubble up the config error
  to users to make it actionable. It also surfaces errors related to
  "rules" parsing.
  
  This allows us to surface these errors to users in the VSCE, like this:
  
  <img width="342" height="129" alt="Screenshot 2026-01-13 at 4 29 22 PM"
  src="https://github.com/user-attachments/assets/a79ffbe7-7604-400c-a304-c5165b6eebc4"
  />
  
  <img width="346" height="244" alt="Screenshot 2026-01-13 at 4 45 06 PM"
  src="https://github.com/user-attachments/assets/de874f7c-16a2-4a95-8c6d-15f10482e67b"
  />

  Eric Traut · 2026-01-13 17:57:09 -08:00
  31d9b6f4d2
• ollama: default to Responses API for built-ins (#8798)

  This is an alternate PR to solving the same problem as
  <https://github.com/openai/codex/pull/8227>.
  
  In this PR, when Ollama is used via `--oss` (or via `model_provider =
  "ollama"`), we default it to use the Responses format. At runtime, we do
  an Ollama version check, and if the version is older than when Responses
  support was added to Ollama, we print out a warning.
  
  Because there's no way of configuring the wire api for a built-in
  provider, we temporarily add a new `oss_provider`/`model_provider`
  called `"ollama-chat"` that will force the chat format.
  
  Once the `"chat"` format is fully removed (see
  <https://github.com/openai/codex/discussions/7782>), `ollama-chat` can
  be removed as well
  
  ---------
  
  Co-authored-by: Eric Traut <etraut@openai.com>
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  Devon Rifkin · 2026-01-13 09:51:41 -08:00
  fe03320791
• feat: add support for building with Bazel (#8875)

  This PR configures Codex CLI so it can be built with
  [Bazel](https://bazel.build) in addition to Cargo. The `.bazelrc`
  includes configuration so that remote builds can be done using
  [BuildBuddy](https://www.buildbuddy.io).
  
  If you are familiar with Bazel, things should work as you expect, e.g.,
  run `bazel test //... --keep-going` to run all the tests in the repo,
  but we have also added some new aliases in the `justfile` for
  convenience:
  
  - `just bazel-test` to run tests locally
  - `just bazel-remote-test` to run tests remotely (currently, the remote
  build is for x86_64 Linux regardless of your host platform). Note we are
  currently seeing the following test failures in the remote build, so we
  still need to figure out what is happening here:
  
  ```
  failures:
      suite::compact::manual_compact_twice_preserves_latest_user_messages
      suite::compact_resume_fork::compact_resume_after_second_compaction_preserves_history
      suite::compact_resume_fork::compact_resume_and_fork_preserve_model_history_view
  ```
  
  - `just build-for-release` to build release binaries for all
  platforms/architectures remotely
  
  To setup remote execution:
  - [Create a buildbuddy account](https://app.buildbuddy.io/) (OpenAI
  employees should also request org access at
  https://openai.buildbuddy.io/join/ with their `@openai.com` email
  address.)
  - [Copy your API key](https://app.buildbuddy.io/docs/setup/) to
  `~/.bazelrc` (add the line `build
  --remote_header=x-buildbuddy-api-key=YOUR_KEY`)
  - Use `--config=remote` in your `bazel` invocations (or add `common
  --config=remote` to your `~/.bazelrc`, or use the `just` commands)
  
  ## CI
  
  In terms of CI, this PR introduces `.github/workflows/bazel.yml`, which
  uses Bazel to run the tests _locally_ on Mac and Linux GitHub runners
  (we are working on supporting Windows, but that is not ready yet). Note
  that the failures we are seeing in `just bazel-remote-test` do not occur
  on these GitHub CI jobs, so everything in `.github/workflows/bazel.yml`
  is green right now.
  
  The `bazel.yml` uses extra config in `.github/workflows/ci.bazelrc` so
  that macOS CI jobs build _remotely_ on Linux hosts (using the
  `docker://docker.io/mbolin491/codex-bazel` Docker image declared in the
  root `BUILD.bazel`) using cross-compilation to build the macOS
  artifacts. Then these artifacts are downloaded locally to GitHub's macOS
  runner so the tests can be executed natively. This is the relevant
  config that enables this:
  
  ```
  common:macos --config=remote
  common:macos --strategy=remote
  common:macos --strategy=TestRunner=darwin-sandbox,local
  ```
  
  Because of the remote caching benefits we get from BuildBuddy, these new
  CI jobs can be extremely fast! For example, consider these two jobs that
  ran all the tests on Linux x86_64:
  
  - Bazel 1m37s
  https://github.com/openai/codex/actions/runs/20861063212/job/59940545209?pr=8875
  - Cargo 9m20s
  https://github.com/openai/codex/actions/runs/20861063192/job/59940559592?pr=8875
  
  For now, we will continue to run both the Bazel and Cargo jobs for PRs,
  but once we add support for Windows and running Clippy, we should be
  able to cutover to using Bazel exclusively for PRs, which should still
  speed things up considerably. We will probably continue to run the Cargo
  jobs post-merge for commits that land on `main` as a sanity check.
  
  Release builds will also continue to be done by Cargo for now.
  
  Earlier attempt at this PR: https://github.com/openai/codex/pull/8832
  Earlier attempt to add support for Buck2, now abandoned:
  https://github.com/openai/codex/pull/8504
  
  ---------
  
  Co-authored-by: David Zbarsky <dzbarsky@gmail.com>
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  zbarsky-openai · 2026-01-09 11:09:43 -08:00
  2a06d64bc9
• feat: support allowed_sandbox_modes in requirements.toml (#8298)

  This adds support for `allowed_sandbox_modes` in `requirements.toml` and
  provides legacy support for constraining sandbox modes in
  `managed_config.toml`. This is converted to `Constrained<SandboxPolicy>`
  in `ConfigRequirements` and applied to `Config` such that constraints
  are enforced throughout the harness.
  
  Note that, because `managed_config.toml` is deprecated, we do not add
  support for the new `external-sandbox` variant recently introduced in
  https://github.com/openai/codex/pull/8290. As noted, that variant is not
  supported in `config.toml` today, but can be configured programmatically
  via app server.

  Michael Bolin · 2025-12-19 21:09:20 +00:00
  dc61fc5f50
• feat: introduce ExternalSandbox policy (#8290)

  ## Description
  
  Introduced `ExternalSandbox` policy to cover use case when sandbox
  defined by outside environment, effectively it translates to
  `SandboxMode#DangerFullAccess` for file system (since sandbox configured
  on container level) and configurable `network_access` (either Restricted
  or Enabled by outside environment).
  
  as example you can configure `ExternalSandbox` policy as part of
  `sendUserTurn` v1 app_server API:
  
  ```
   {
              "conversationId": <id>,
              "cwd": <cwd>,
              "approvalPolicy": "never",
              "sandboxPolicy": {
                    "type": ""external-sandbox",
                    "network_access": "enabled"/"restricted"
              },
              "model": <model>,
              "effort": <effort>,
              ....
          }
  ```

  Anton Panasenko · 2025-12-18 17:02:03 -08:00
  3429de21b3
• feat: Constrain values for approval_policy (#7778)

  Constrain `approval_policy` through new `admin_policy` config.
  
  This PR will:
  1. Add a `admin_policy` section to config, with a single field (for now)
  `allowed_approval_policies`. This list constrains the set of
  user-settable `approval_policy`s.
  2. Introduce a new `Constrained<T>` type, which combines a current value
  and a validator function. The validator function ensures disallowed
  values are not set.
  3. Change the type of `approval_policy` on `Config` and
  `SessionConfiguration` from `AskForApproval` to
  `Constrained<AskForApproval>`. The validator function is set by the
  values passed into `allowed_approval_policies`.
  4. `GenericDisplayRow`: add a `disabled_reason: Option<String>`. When
  set, it disables selection of the value and indicates as such in the
  menu. This also makes it unselectable with arrow keys or numbers. This
  is used in the `/approvals` menu.
  
  Follow ups are:
  1. Do the same thing to `sandbox_policy`.
  2. Propagate the allowed set of values through app-server for the
  extension (though already this should prevent app-server from setting
  this values, it's just that we want to disable UI elements that are
  unsettable).
  
  Happy to split this PR up if you prefer, into the logical numbered areas
  above. Especially if there are parts we want to gavel on separately
  (e.g. admin_policy).
  
  Disabled full access:
  <img width="1680" height="380" alt="image"
  src="https://github.com/user-attachments/assets/1fb61c8c-1fcb-4dc4-8355-2293edb52ba0"
  />
  
  Disabled `--yolo` on startup:
  <img width="749" height="76" alt="image"
  src="https://github.com/user-attachments/assets/0a1211a0-6eb1-40d6-a1d7-439c41e94ddb"
  />
  
  CODEX-4087

  gt-oai · 2025-12-17 16:19:27 +00:00
  9352c6b235
• make model optional in config (#7769)

  - Make Config.model optional and centralize default-selection logic in
  ModelsManager, including a default_model helper (with
  codex-auto-balanced when available) so sessions now carry an explicit
  chosen model separate from the base config.
  - Resolve `model` once in `core` and `tui` from config. Then store the
  state of it on other structs.
  - Move refreshing models to be before resolving the default model

  Ahmed Ibrahim · 2025-12-10 11:19:00 -08:00
  cb9a189857
• remove model_family from `config (#7571)

  - Remove `model_family` from `config`
  - Make sure to still override config elements related to `model_family`
  like supporting reasoning

  Ahmed Ibrahim · 2025-12-04 11:57:58 -08:00
  9b2055586d
• Migrate model preset (#7542)

  - Introduce `openai_models` in `/core`
  - Move `PRESETS` under it
  - Move `ModelPreset`, `ModelUpgrade`, `ReasoningEffortPreset`,
  `ReasoningEffortPreset`, and `ReasoningEffortPreset` to `protocol`
  - Introduce `Op::ListModels` and `EventMsg::AvailableModels`
  
  Next steps:
  - migrate `app-server` and `tui` to use the introduced Operation

  Ahmed Ibrahim · 2025-12-03 20:30:43 +00:00
  71504325d3
• chore: add cargo-deny configuration (#7119)

  - add GitHub workflow running cargo-deny on push/PR
  - document cargo-deny allowlist with workspace-dep notes and advisory
  ignores
  - align workspace crates to inherit version/edition/license for
  consistent checks

  Josh McKinney · 2025-11-24 12:22:18 -08:00
  ec49b56874
• Fix/correct reasoning display (#6749)

  This closes #6748 by implementing fallback to
  `model_family.default_reasoning_effort` in `reasoning_effort` display of
  `/status` when no `model_reasoning_effort` is set in the configuration.
  
  ## common/src/config_summary.rs
  
  - `create_config_summary_entries` now fills the "reasoning effort" entry
  with the explicit `config.model_reasoning_effort` when present and falls
  back to `config.model_family.default_reasoning_effort` when it is
  `None`, instead of emitting the literal string `none`.
  - This ensures downstream consumers such as `tui/src/status/helpers.rs`
  continue to work unchanged while automatically picking up model-family
  defaults when the user has not selected a reasoning effort.
  
  ## tui/src/status/helpers.rs / core/src/model_family.rs
  
  `ModelFamily::default_reasoning_effort` metadata is set to `medium` for
  both `gpt-5*-codex` and `gpt-5` models following the default behaviour
  of the API and recommendation of the codebase:
  - per https://platform.openai.com/docs/api-reference/responses/create
  `gpt-5` defaults to `medium` reasoning when no preset is passed
  - there is no mention of the preset for `gpt-5.1-codex` in the API docs
  but `medium` is the default setting for `gpt-5.1-codex` as per
  `codex-rs/tui/src/chatwidget/snapshots/codex_tui__chatwidget__tests__model_reasoning_selection_popup.snap`
  
  ---------
  
  Signed-off-by: lionelchg <lionel.cheng@hotmail.fr>
  Co-authored-by: Eric Traut <etraut@openai.com>

  Lionel Cheng · 2025-11-19 15:52:24 -08:00
  a6597a9958
• feat: arcticfox in the wild (#6906)

  <img width="485" height="600" alt="image"
  src="https://github.com/user-attachments/assets/4341740d-dd58-4a3e-b69a-33a3be0606c5"
  />
  
  ---------
  
  Co-authored-by: jif-oai <jif@openai.com>

  Ahmed Ibrahim · 2025-11-19 16:31:06 +00:00
  d5dfba2509
• fix: typos in model picker (#6859)

  # External (non-OpenAI) Pull Request Requirements
  
  Before opening this Pull Request, please read the dedicated
  "Contributing" markdown file or your PR may be closed:
  https://github.com/openai/codex/blob/main/docs/contributing.md
  
  If your PR conforms to our contribution guidelines, replace this text
  with a detailed and high quality description of your changes.
  
  Include a link to a bug report or enhancement request.

  Ahmed Ibrahim · 2025-11-19 06:29:02 +00:00
  793063070b
• Prompt to turn on windows sandbox when auto mode selected. (#6618)

  - stop prompting users to install WSL 
  - prompt users to turn on Windows sandbox when auto mode requested.
  
  <img width="1660" height="195" alt="Screenshot 2025-11-17 110612"
  src="https://github.com/user-attachments/assets/c67fc239-a227-417e-94bb-599a8ed8f11e"
  />
  <img width="1684" height="168" alt="Screenshot 2025-11-17 110637"
  src="https://github.com/user-attachments/assets/d18c3370-830d-4971-8746-04757ae2f709"
  />
  <img width="1655" height="293" alt="Screenshot 2025-11-17 110719"
  src="https://github.com/user-attachments/assets/d21f6ce9-c23e-4842-baf6-8938b77c16db"
  />

  iceweasel-oai · 2025-11-18 11:38:18 -08:00
  4bada5a84d
• LM Studio OSS Support (#2312)

  ## Overview
  
  Adds LM Studio OSS support. Closes #1883
  
  
  ### Changes
  This PR enhances the behavior of `--oss` flag to support LM Studio as a
  provider. Additionally, it introduces a new flag`--local-provider` which
  can take in `lmstudio` or `ollama` as values if the user wants to
  explicitly choose which one to use.
  
  If no provider is specified `codex --oss` will auto-select the provider
  based on whichever is running.
  
  #### Additional enhancements 
  The default can be set using `oss-provider` in config like:
  
  ```
  oss_provider = "lmstudio"
  ```
  
  For non-interactive users, they will need to either provide the provider
  as an arg or have it in their `config.toml`
  
  ### Notes
  For best performance, [set the default context
  length](https://lmstudio.ai/docs/app/advanced/per-model) for gpt-oss to
  the maximum your machine can support
  
  ---------
  
  Co-authored-by: Matt Clayton <matt@lmstudio.ai>
  Co-authored-by: Eric Traut <etraut@openai.com>

  rugvedS07 · 2025-11-17 11:49:09 -08:00
  837bc98a1d
• Reasoning level update (#6586)

  Automatically update reasoning levels when migrating between models

  pakrym-oai · 2025-11-13 06:24:36 +00:00
  e3dd362c94
• feat: show gpt mini (#6583)
  Ahmed Ibrahim · 2025-11-13 05:21:00 +00:00
  e3aaee00c8
• Change model picker to include gpt5.1 (#6569)

  - Change the presets
  - Change the tests that make sure we keep the list of tools updated
  - Filter out deprecated models

  Ahmed Ibrahim · 2025-11-12 19:44:53 -08:00
  ad7eaa80f9
• NUX for gpt5.1 (#6561)

  - Introducing a screen to inform users of model changes. 
  - Config name is being passed to be able to reuse this component in the
  future for future models

  Ahmed Ibrahim · 2025-11-13 01:24:21 +00:00
  e63ab0dd65
• chore: verify boolean values can be parsed as config overrides (#6516)

  This is important to ensure that this:
  
  ```
  codex --enable unified_exec
  ```
  
  and this:
  
  ```
  codex --config features.unified_exec=true
  ```
  
  are equivalent. Also that when it is passed programmatically:
  
  
  https://github.com/openai/codex/blob/807e2c27f0a9f2e85c50e7e6df5533f0d9b853c7/codex-rs/app-server-protocol/src/protocol/v1.rs#L55
  
  then this should work for `config`:
  
  ```json
  {"features": {"shell_command_tool": true}}
  ```
  
  though I believe also this:
  
  ```json
  {"features.shell_command_tool": true}
  ```

  Michael Bolin · 2025-11-12 08:19:16 -08:00
  c3a710ee14
• Fix config documentation: correct TOML parsing description (#6424)

  The CLI help text and inline comments incorrectly stated that -c
  key=value flag parses values as JSON, when the implementation actually
  uses TOML parsing via parse_toml_value(). This caused confusion when
  users attempted to configure MCP servers using JSON syntax based on the
  documentation.
  
  Changes:
  - Updated help text to correctly state TOML parsing instead of JSON
  
  Fixes #4531

  Raduan A. · 2025-11-09 22:58:32 -08:00
  557ac63094
• chore: fix grammar mistakes (#6326)
  Ahmed Ibrahim · 2025-11-06 09:48:59 -08:00
  dbad5eeec6
• chore: rename for clarity (#6319)

  Co-authored-by: Ahmed Ibrahim <aibrahim@openai.com>

  Thibault Sottiaux · 2025-11-06 08:32:57 -08:00
  649ce520c4
• feat: support models with single reasoning effort (#6300)
  Thibault Sottiaux · 2025-11-05 23:06:45 -08:00
  667e841d3e
• feat(tui): clarify Windows auto mode requirements (#5568)

  ## Summary
  - Coerce Windows `workspace-write` configs back to read-only, surface
  the forced downgrade in the approvals popup,
    and funnel users toward WSL or Full Access.
  - Add WSL installation instructions to the Auto preset on Windows while
  keeping the preset available for other
    platforms.
  - Skip the trust-on-first-run prompt on native Windows so new folders
  remain read-only without additional
    confirmation.
  - Expose a structured sandbox policy resolution from config to flag
  Windows downgrades and adjust tests (core,
  exec, TUI) to reflect the new behavior; provide a Windows-only approvals
  snapshot.
  
    ## Testing
    - cargo fmt
  - cargo test -p codex-core
  config::tests::add_dir_override_extends_workspace_writable_roots
  - cargo test -p codex-exec
  suite::resume::exec_resume_preserves_cli_configuration_overrides
  - cargo test -p codex-tui
  chatwidget::tests::approvals_selection_popup_snapshot
  - cargo test -p codex-tui
  approvals_popup_includes_wsl_note_for_auto_mode
    - cargo test -p codex-tui windows_skips_trust_prompt
    - just fix -p codex-core
    - just fix -p codex-tui

  Josh McKinney · 2025-10-28 01:19:32 +00:00
  66a4b89822
• [MCP] Redact environment variable values in /mcp and mcp get (#5648)

  Fixes #5524

  Gabriel Peal · 2025-10-24 18:30:20 -04:00
  817d1508bc
• [app-server] model/list API (#5382)

  Adds a `model/list` paginated API that returns the list of models
  supported by Codex.

  Owen Lin · 2025-10-21 11:15:17 -07:00
  26f314904a
• [MCP] Allow specifying cwd and additional env vars (#5246)

  This makes stdio mcp servers more flexible by allowing users to specify
  the cwd to run the server command from and adding additional environment
  variables to be passed through to the server.
  
  Example config using the test server in this repo:
  ```toml
  [mcp_servers.test_stdio]
  cwd = "/Users/<user>/code/codex/codex-rs"
  command = "cargo"
  args = ["run", "--bin", "test_stdio_server"]
  env_vars = ["MCP_TEST_VALUE"]
  ```
  
  @bolinfest I know you hate these env var tests but let's roll with this
  for now. I may take a stab at the env guard + serial macro at some
  point.

  Gabriel Peal · 2025-10-17 00:24:43 -04:00
  bdda762deb
• Make model switcher two-stage (#4178)

  https://github.com/user-attachments/assets/16d5c67c-e580-4a29-983c-a315f95424ee

  easong-openai · 2025-10-02 19:38:24 +00:00
  06e34d4607
• fix: remove mcp-types from app server protocol (#4537)

  We continue the separation between `codex app-server` and `codex
  mcp-server`.
  
  In particular, we introduce a new crate, `codex-app-server-protocol`,
  and migrate `codex-rs/protocol/src/mcp_protocol.rs` into it, renaming it
  `codex-rs/app-server-protocol/src/protocol.rs`.
  
  Because `ConversationId` was defined in `mcp_protocol.rs`, we move it
  into its own file, `codex-rs/protocol/src/conversation_id.rs`, and
  because it is referenced in a ton of places, we have to touch a lot of
  files as part of this PR.
  
  We also decide to get away from proper JSON-RPC 2.0 semantics, so we
  also introduce `codex-rs/app-server-protocol/src/jsonrpc_lite.rs`, which
  is basically the same `JSONRPCMessage` type defined in `mcp-types`
  except with all of the `"jsonrpc": "2.0"` removed.
  
  Getting rid of `"jsonrpc": "2.0"` makes our serialization logic
  considerably simpler, as we can lean heavier on serde to serialize
  directly into the wire format that we use now.

  Michael Bolin · 2025-10-01 02:16:26 +00:00
  5881c0d6d4
• fix: set gpt-5-codex medium preset reasoning (#4335)

  Otherwise it shows up as none, see
  https://github.com/openai/codex/issues/4321

  Thibault Sottiaux · 2025-09-26 22:31:39 -07:00
  90c3a5650c
• chore: extract readiness in a dedicated utils crate (#4140)

  Create an `utils` directory for the small utils crates

  jif-oai · 2025-09-24 10:15:54 +00:00
  5b910f1f05
• feat: readiness tool (#4090)

  Readiness flag with token-based subscription and async wait function
  that waits for all the subscribers to be ready

  jif-oai · 2025-09-23 17:27:20 +01:00
  6cd5309d91
• feat: update default (#4076)

  Changes:
  - Default model and docs now use gpt-5-codex. 
  - Disables the GPT-5 Codex NUX by default.
  - Keeps presets available for API key users.

  Thibault Sottiaux · 2025-09-22 20:10:52 -07:00
  c93e77b68b
• chore: unify cargo versions (#4044)

  Unify cargo versions at root

  jif-oai · 2025-09-22 16:47:01 +00:00
  e5fe50d3ce
• chore: rename (#3648)
  Michael Bolin · 2025-09-15 08:17:13 -07:00
  f037b2fd56
• feat: tighten preset filter, tame storage load logs, enable rollout prompt by default (#3628)

  Summary
  - common: use exact equality for Swiftfox exclusion to avoid hiding
  future slugs that merely contain the substring
  - core: treat missing internal_storage.json as expected (debug), warn
  only on real IO/parse errors
  - tui: drop DEBUG_HIGH gate; always consider showing rollout prompt, but
  suppress under ApiKey auth mode

  Thibault Sottiaux · 2025-09-14 23:05:41 -07:00
  6039f8a126
• Don't show the model for apikey (#3607)
  Ahmed Ibrahim · 2025-09-15 01:32:18 +00:00
  2ad6a37192
• Fix swiftfox model selector (#3598)

  The model shouldn't be saved with a suffix. The effort is a separate
  field.

  pakrym-oai · 2025-09-14 23:12:21 +00:00
  51f88fd04a
• chore: remove descriptions
  Thibault Sottiaux · 2025-09-12 22:55:40 -07:00
  a77364bbaa
• w
  Thibault Sottiaux · 2025-09-12 22:44:05 -07:00
  19b4ed3c96
• feat: reasoning effort as optional (#3527)

  Allow the reasoning effort to be optional

  jif-oai · 2025-09-12 12:06:33 -07:00
  c6fd056aa6
• Add spacing to timer duration formats (#3471)

  <img width="426" height="28" alt="image"
  src="https://github.com/user-attachments/assets/b281aca3-3c8d-4b88-a017-5d2f8ea9f3d5"
  />

  Ahmed Ibrahim · 2025-09-12 12:05:57 -04:00
  ba6af23cb6
• feat: TUI onboarding (#3398)

  Example of how onboarding could look like

  jif-oai · 2025-09-11 15:04:29 -07:00
  8453915e02
• feat: copy tweaks (#2502)

  - For selectable options, use sentences starting in lowercase and not
  ending with periods. To be honest I don't love this style, but better to
  be consistent for now.
  - Tweak some other strings.
  - Put in more compelling suggestions on launch. Excited to put `/mcp` in
  there next.

  ae · 2025-08-20 07:26:14 +00:00
  ee8c4ad23a
• Add a slash command to control permissions (#2474)

  A slash command to control permissions
  
  
  
  https://github.com/user-attachments/assets/c0edafcd-2085-4e09-8009-ba69c4f1c153
  
  ---------
  
  Co-authored-by: ae <ae@openai.com>

  Ahmed Ibrahim · 2025-08-20 05:34:37 +00:00
  202af12926
• Support changing reasoning effort (#2435)

  https://github.com/user-attachments/assets/50198ee8-5915-47a3-bb71-69af65add1ef
  
  Building up on #2431 #2428

  Ahmed Ibrahim · 2025-08-19 17:55:07 +00:00
  e91c3d6d1c