1727 Commits

• feat: update process_exec_tool_call() to take a cancellation token (#6972)

  This updates `ExecParams` so that instead of taking `timeout_ms:
  Option<u64>`, it now takes a more general cancellation mechanism,
  `ExecExpiration`, which is an enum that includes a
  `Cancellation(tokio_util::sync::CancellationToken)` variant.
  
  If the cancellation token is fired, then `process_exec_tool_call()`
  returns in the same way as if a timeout was exceeded.
  
  This is necessary so that in #6973, we can manage the timeout logic
  external to the `process_exec_tool_call()` because we want to "suspend"
  the timeout when an elicitation from a human user is pending.
  
  
  
  
  
  
  
  
  ---
  [//]: # (BEGIN SAPLING FOOTER)
  Stack created with [Sapling](https://sapling-scm.com). Best reviewed
  with [ReviewStack](https://reviewstack.dev/openai/codex/pull/6972).
  * #7005
  * #6973
  * __->__ #6972

  Michael Bolin · 2025-11-20 16:29:57 -08:00
  f56d1dc8fc
• migrate collect_tool_identifiers_for_model to test_codex (#7041)

  Maybe it solved flakiness

  Ahmed Ibrahim · 2025-11-20 16:02:50 -08:00
  9be310041b
• core: make shell behavior portable on FreeBSD (#7039)

  - Use /bin/sh instead of /bin/bash on FreeBSD/OpenBSD in the process
  group timeout test to avoid command-not-found failures.
  
  - Accept /usr/local/bin/bash as a valid SHELL path to match common
  FreeBSD installations.
  
  - Switch the shell serialization duration test to /bin/sh for improved
  portability across Unix platforms.
  
  With this change, `cargo test -p codex-core --lib` runs and passes on
  FreeBSD.

  Xiao-Yong Jin · 2025-11-20 16:01:35 -08:00
  0fbcdd77c8
• [app-server & core] introduce new codex error code and v2 app-server error events (#6938)

  This PR does two things:
  1. populate a new `codex_error_code` protocol in error events sent from
  core to client;
  2. old v1 core events `codex/event/stream_error` and `codex/event/error`
  will now both become `error`. We also show codex error code for
  turncompleted -> error status.
  
  new events in app server test:
  ```
  < {
  <   "method": "codex/event/stream_error",
  <   "params": {
  <     "conversationId": "019aa34c-0c14-70e0-9706-98520a760d67",
  <     "id": "0",
  <     "msg": {
  <       "codex_error_code": {
  <         "response_stream_disconnected": {
  <           "http_status_code": 401
  <         }
  <       },
  <       "message": "Reconnecting... 2/5",
  <       "type": "stream_error"
  <     }
  <   }
  < }
  
   {
  <   "method": "error",
  <   "params": {
  <     "error": {
  <       "codexErrorCode": {
  <         "responseStreamDisconnected": {
  <           "httpStatusCode": 401
  <         }
  <       },
  <       "message": "Reconnecting... 2/5"
  <     }
  <   }
  < }
  
  < {
  <   "method": "turn/completed",
  <   "params": {
  <     "turn": {
  <       "error": {
  <         "codexErrorCode": {
  <           "responseTooManyFailedAttempts": {
  <             "httpStatusCode": 401
  <           }
  <         },
  <         "message": "exceeded retry limit, last status: 401 Unauthorized, request id: 9a1b495a1a97ed3e-SJC"
  <       },
  <       "id": "0",
  <       "items": [],
  <       "status": "failed"
  <     }
  <   }
  < }
  ```

  Celia Chen · 2025-11-20 23:06:55 +00:00
  9bce050385
• Attempt to fix unified_exec_formats_large_output_summary flakiness (#7029)

  second attempt to fix this test after
  https://github.com/openai/codex/pull/6884. I think this flakiness is
  happening because yield_time is too small for a 10,000 step loop in
  python.

  Ahmed Ibrahim · 2025-11-20 14:38:04 -08:00
  54ee302a06
• Delete shell_command feature (#7024)
  pakrym-oai · 2025-11-20 14:14:56 -08:00
  856f97f449
• execpolicycheck command in codex cli (#7012)

  adding execpolicycheck tool onto codex cli
  
  this is useful for validating policies (can be multiple) against
  commands.
  
  it will also surface errors in policy syntax:
  <img width="1150" height="281" alt="Screenshot 2025-11-19 at 12 46
  21 PM"
  src="https://github.com/user-attachments/assets/8f99b403-564c-4172-acc9-6574a8d13dc3"
  />
  
  this PR also changes output format when there's no match in the CLI.
  instead of returning the raw string `noMatch`, we return
  `{"noMatch":{}}`
  
  this PR is a rewrite of: https://github.com/openai/codex/pull/6932 (due
  to the numerous merge conflicts present in the original PR)
  
  ---------
  
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  zhao-oai · 2025-11-20 16:44:31 -05:00
  fe7a3f0c2b
• increasing user shell timeout to 1 hour (#7025)

  setting user shell timeout to an unreasonably high value since there
  isn't an easy way to have a command run without timeouts
  
  currently, user shell commands timeout is 10 seconds

  zhao-oai · 2025-11-20 13:39:16 -08:00
  c30ca0d5b6
• Delete tiktoken-rs (#7018)
  pakrym-oai · 2025-11-20 11:15:04 -08:00
  52d0ec4cd8
• Fix: Improve text encoding for shell output in VSCode preview (#6178) (#6182)

  ## 🐛 Problem
  
  Users running commands with non-ASCII characters (like Russian text
  "пример") in Windows/WSL environments experience garbled text in
  VSCode's shell preview window, with Unicode replacement characters (�)
  appearing instead of the actual text.
  
  **Issue**: https://github.com/openai/codex/issues/6178
  
  ## 🔧 Root Cause
  
  The issue was in `StreamOutput<Vec<u8>>::from_utf8_lossy()` method in
  `codex-rs/core/src/exec.rs`, which used `String::from_utf8_lossy()` to
  convert shell output bytes to strings. This function immediately
  replaces any invalid UTF-8 byte sequences with replacement characters,
  without attempting to decode using other common encodings.
  
  In Windows/WSL environments, shell output often uses encodings like:
  
  - Windows-1252 (common Windows encoding)
  - Latin-1/ISO-8859-1 (extended ASCII)
  
  ## 🛠️ Solution
  
  Replaced the simple `String::from_utf8_lossy()` call with intelligent
  encoding detection via a new `bytes_to_string_smart()` function that
  tries multiple encoding strategies:
  
  1. **UTF-8** (fast path for valid UTF-8)
  2. **Windows-1252** (handles Windows-specific characters in 0x80-0x9F
  range)
  3. **Latin-1** (fallback for extended ASCII)
  4. **Lossy UTF-8** (final fallback, same as before)
  
  ## 📁 Changes
  
  ### New Files
  
  - `codex-rs/core/src/text_encoding.rs` - Smart encoding detection module
  - `codex-rs/core/tests/suite/text_encoding_fix.rs` - Integration tests
  
  ### Modified Files
  
  - `codex-rs/core/src/lib.rs` - Added text_encoding module
  - `codex-rs/core/src/exec.rs` - Updated StreamOutput::from_utf8_lossy()
  - `codex-rs/core/tests/suite/mod.rs` - Registered new test module
  
  ## ✅ Testing
  
  - **5 unit tests** covering UTF-8, Windows-1252, Latin-1, and fallback
  scenarios
  - **2 integration tests** simulating the exact Issue #6178 scenario
  - **Demonstrates improvement** over the previous
  `String::from_utf8_lossy()` approach
  
  All tests pass:
  
  ```bash
  cargo test -p codex-core text_encoding
  cargo test -p codex-core test_shell_output_encoding_issue_6178
  ```
  
  ## 🎯 Impact
  
  - ✅ **Eliminates garbled text** in VSCode shell preview for non-ASCII
  content
  - ✅ **Supports Windows/WSL environments** with proper encoding detection
  - ✅ **Zero performance impact** for UTF-8 text (fast path)
  - ✅ **Backward compatible** - UTF-8 content works exactly as before
  - ✅ **Handles edge cases** with robust fallback mechanism
  
  ## 🧪 Test Scenarios
  
  The fix has been tested with:
  
  - Russian text ("пример")
  - Windows-1252 quotation marks (""test")
  - Latin-1 accented characters ("café")
  - Mixed encoding content
  - Invalid byte sequences (graceful fallback)
  
  ## 📋 Checklist
  
  - [X] Addresses the reported issue
  - [X] Includes comprehensive tests
  - [X] Maintains backward compatibility
  - [X] Follows project coding conventions
  - [X] No breaking changes
  
  ---------
  
  Co-authored-by: Josh McKinney <joshka@openai.com>

  LIHUA · 2025-11-20 11:04:11 -08:00
  397279d46e
• Always fallback to real shell (#6953)

  Either cmd.exe or `/bin/sh`.

  pakrym-oai · 2025-11-20 10:58:46 -08:00
  30ca89424c
• Added feature switch to disable animations in TUI (#6870)

  This PR adds support for a new feature flag `tui.animations`. By
  default, the TUI uses animations in its welcome screen, "working"
  spinners, and "shimmer" effects. This animations can interfere with
  screen readers, so it's good to provide a way to disable them.
  
  This change is inspired by [a
  PR](https://github.com/openai/codex/pull/4014) contributed by @Orinks.
  That PR has faltered a bit, but I think the core idea is sound. This
  version incorporates feedback from @aibrahim-oai. In particular:
  1. It uses a feature flag (`tui.animations`) rather than the unqualified
  CLI key `no-animations`. Feature flags are the preferred way to expose
  boolean switches. They are also exposed via CLI command switches.
  2. It includes more complete documentation.
  3. It disables a few animations that the other PR omitted.

  Eric Traut · 2025-11-20 10:40:08 -08:00
  d909048a85
• Allow unified_exec to early exit (if the process terminates before yield_time_ms) (#6867)

  Thread through an `exit_notify` tokio `Notify` through to the
  `UnifiedExecSession` so that we can return early if the command
  terminates before `yield_time_ms`.
  
  As Codex review correctly pointed out below 🙌 we also need a
  `exit_signaled` flag so that commands which finish before we start
  waiting can also exit early.
  
  Since the default `yield_time_ms` is now 10s, this means that we don't
  have to wait 10s for trivial commands like ls, sed, etc (which are the
  majority of agent commands 😅)
  
  ---------
  
  Co-authored-by: jif-oai <jif@openai.com>

  hanson-openai · 2025-11-20 13:34:41 +01:00
  b5dd189067
• [app-server] feat: v2 apply_patch approval flow (#6760)

  This PR adds the API V2 version of the apply_patch approval flow, which
  centers around `ThreadItem::FileChange`.
  
  This PR wires the new RPC (`item/fileChange/requestApproval`, V2 only)
  and related events (`item/started`, `item/completed` for
  `ThreadItem::FileChange`, which are emitted in both V1 and V2) through
  the app-server
  protocol. The new approval RPC is only sent when the user initiates a
  turn with the new `turn/start` API so we don't break backwards
  compatibility with VSCE.
  
  Similar to https://github.com/openai/codex/pull/6758, the approach I
  took was to make as few changes to the Codex core as possible,
  leveraging existing `EventMsg` core events, and translating those in
  app-server. I did have to add a few additional fields to
  `EventMsg::PatchApplyBegin` and `EventMsg::PatchApplyEnd`, but those
  were fairly lightweight.
  
  However, the `EventMsg`s emitted by core are the following:
  ```
  1) Auto-approved (no request for approval)

  - EventMsg::PatchApplyBegin
  - EventMsg::PatchApplyEnd
  
  2) Approved by user
  - EventMsg::ApplyPatchApprovalRequest
  - EventMsg::PatchApplyBegin
  - EventMsg::PatchApplyEnd
  
  3) Declined by user
  - EventMsg::ApplyPatchApprovalRequest
  - EventMsg::PatchApplyBegin
  - EventMsg::PatchApplyEnd
  ```
  
  For a request triggering an approval, this would result in:
  ```
  item/fileChange/requestApproval
  item/started
  item/completed
  ```
  
  which is different from the `ThreadItem::CommandExecution` flow
  introduced in https://github.com/openai/codex/pull/6758, which does the
  below and is preferable:
  ```
  item/started
  item/commandExecution/requestApproval
  item/completed
  ```
  
  To fix this, we leverage `TurnSummaryStore` on codex_message_processor
  to store a little bit of state, allowing us to fire `item/started` and
  `item/fileChange/requestApproval` whenever we receive the underlying
  `EventMsg::ApplyPatchApprovalRequest`, and no-oping when we receive the
  `EventMsg::PatchApplyBegin` later.
  
  This is much less invasive than modifying the order of EventMsg within
  core (I tried).
  
  The resulting payloads:
  ```
  {
    "method": "item/started",
    "params": {
      "item": {
        "changes": [
          {
            "diff": "Hello from Codex!\n",
            "kind": "add",
            "path": "/Users/owen/repos/codex/codex-rs/APPROVAL_DEMO.txt"
          }
        ],
        "id": "call_Nxnwj7B3YXigfV6Mwh03d686",
        "status": "inProgress",
        "type": "fileChange"
      }
    }
  }
  ```
  
  ```
  {
    "id": 0,
    "method": "item/fileChange/requestApproval",
    "params": {
      "grantRoot": null,
      "itemId": "call_Nxnwj7B3YXigfV6Mwh03d686",
      "reason": null,
      "threadId": "019a9e11-8295-7883-a283-779e06502c6f",
      "turnId": "1"
    }
  }
  ```
  
  ```
  {
    "id": 0,
    "result": {
      "decision": "accept"
    }
  }
  ```
  
  ```
  {
    "method": "item/completed",
    "params": {
      "item": {
        "changes": [
          {
            "diff": "Hello from Codex!\n",
            "kind": "add",
            "path": "/Users/owen/repos/codex/codex-rs/APPROVAL_DEMO.txt"
          }
        ],
        "id": "call_Nxnwj7B3YXigfV6Mwh03d686",
        "status": "completed",
        "type": "fileChange"
      }
    }
  }
  ```

  Owen Lin · 2025-11-19 20:13:31 -08:00
  d6c30ed25e
• migrating execpolicy -> execpolicy-legacy and execpolicy2 -> execpolicy (#6956)
  zhao-oai · 2025-11-19 19:14:10 -08:00
  fb9849e1e3
• Revert "[core] add optional status_code to error events (#6865)" (#6955)

  This reverts commit c2ec477d93.
  
  # 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.

  Celia Chen · 2025-11-20 01:26:14 +00:00
  72a1453ac5
• stop model migration screen after first time. (#6954)

  it got serialized wrong.

  Ahmed Ibrahim · 2025-11-19 17:17:04 -08:00
  6d67b8b283
• Single pass truncation (#6914)
  pakrym-oai · 2025-11-19 16:56:37 -08:00
  92e3046733
• execpolicy2 core integration (#6641)

  This PR threads execpolicy2 into codex-core.
  
  activated via feature flag: exec_policy (on by default)
  
  reads and parses all .codexpolicy files in `codex_home/codex`
  
  refactored tool runtime API to integrate execpolicy logic
  
  ---------
  
  Co-authored-by: Michael Bolin <mbolin@openai.com>

  zhao-oai · 2025-11-19 16:50:43 -08:00
  65c13f1ae7
• fix(shell) fallback shells (#6948)

  ## Summary
  Add fallbacks when user_shell_path does not resolve to a known shell
  type
  
  ## Testing
  - [x] Tests still pass

  Dylan Hurd · 2025-11-19 16:41:38 -08:00
  b00a7cf40d
• [core] add optional status_code to error events (#6865)

  We want to better uncover error status code for clients. Add an optional
  status_code to error events (thread error, error, stream error) so app
  server could uncover the status code from the client side later.
  
  in event log:
  ```
  < {
  <   "method": "codex/event/stream_error",
  <   "params": {
  <     "conversationId": "019a9a32-f576-7292-9711-8e57e8063536",
  <     "id": "0",
  <     "msg": {
  <       "message": "Reconnecting... 5/5",
  <       "status_code": 401,
  <       "type": "stream_error"
  <     }
  <   }
  < }
  < {
  <   "method": "codex/event/error",
  <   "params": {
  <     "conversationId": "019a9a32-f576-7292-9711-8e57e8063536",
  <     "id": "0",
  <     "msg": {
  <       "message": "exceeded retry limit, last status: 401 Unauthorized, request id: 9a0cb03a485067f7-SJC",
  <       "status_code": 401,
  <       "type": "error"
  <     }
  <   }
  < }
  ```

  Celia Chen · 2025-11-19 19:51:21 +00:00
  c2ec477d93
• Keep gpt-5.1-codex the default (#6922)
  pakrym-oai · 2025-11-19 11:08:10 -08:00
  64ae9aa3c3
• storing credits (#6858)

  Expand the rate-limit cache/TUI: store credit snapshots alongside
  primary and secondary windows, render “Credits” when the backend reports
  they exist (unlimited vs rounded integer balances)

  zhao-oai · 2025-11-19 10:49:35 -08:00
  72af589398
• use another prompt (#6912)
  jif-oai · 2025-11-19 17:47:47 +00:00
  91a1d20e2d
• NITs (#6911)
  jif-oai · 2025-11-19 17:43:51 +00:00
  87716e7cd0
• Fix ordering 2 (#6910)
  jif-oai · 2025-11-19 17:40:27 +00:00
  8976551f0d
• fix: ordering (#6909)
  jif-oai · 2025-11-19 17:39:07 +00:00
  f1d6767685
• fix: don't truncate at new lines (#6907)
  Ahmed Ibrahim · 2025-11-19 17:05:48 +00:00
  d62cab9a06
• 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(core) Support changing /approvals before conversation (#6836)

  ## Summary
  Setting `/approvals` before the start of a conversation was not updating
  the environment_context for a conversation. Not sure exactly when this
  problem was introduced, but this should reduce model confusion
  dramatically.
  
  ## Testing
  - [x] Added unit test to reproduce bug, confirmed fix with update
  - [x] Tested locally

  Dylan Hurd · 2025-11-19 11:32:48 +00:00
  15b5eb30ed
• chore: consolidate compaction token usage (#6894)
  jif-oai · 2025-11-19 11:26:01 +00:00
  3e9e1d993d
• fix: parallel tool call instruction injection (#6893)
  jif-oai · 2025-11-19 11:01:57 +00:00
  4985a7a444
• nit: stable (#6895)
  jif-oai · 2025-11-19 10:43:43 +00:00
  10d571f236
• feat: warning large commits (#6838)
  jif-oai · 2025-11-19 10:22:10 +00:00
  956d3bfac6
• Move shell to use truncate_text (#6842)

  Move shell to use the configurable `truncate_text`
  
  ---------
  
  Co-authored-by: pakrym-oai <pakrym@openai.com>

  Ahmed Ibrahim · 2025-11-19 01:56:08 -08:00
  efebc62fb7
• Run remote auto compaction (#6879)
  pakrym-oai · 2025-11-19 00:43:58 -08:00
  75f38f16dd
• flaky-unified_exec_formats_large_output_summary (#6884)

  # 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 00:00:37 -08:00
  0440a3f105
• shell_command returns freeform output (#6860)

  Instead of returning structured out and then re-formatting it into
  freeform, return the freeform output from shell_command tool.
  
  Keep `shell` as the default tool for GPT-5.

  pakrym-oai · 2025-11-18 23:38:43 -08:00
  ee0484a98c
• chore(core) arcticfox (#6876)

  ..

  Dylan Hurd · 2025-11-18 23:38:08 -08:00
  7e0e675db4
• fix(tui) ghost snapshot notifications (#6881)

  ## Summary
  - avoid surfacing ghost snapshot warnings in the TUI when snapshot
  creation fails, logging the conditions instead
  - continue to capture successful ghost snapshots without changing
  existing behavior
  
  ## Testing
  - `cargo test -p codex-core` *(fails:
  default_client::tests::test_create_client_sets_default_headers,
  default_client::tests::test_get_codex_user_agent,
  exec::tests::kill_child_process_group_kills_grandchildren_on_timeout)*
  
  ------
  [Codex
  Task](https://chatgpt.com/codex/tasks/task_i_691c02238db08322927c47b8c2d72c4c)

  Dylan Hurd · 2025-11-18 23:23:00 -08:00
  84458f12f6
• 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
• fix: add more fields to ThreadStartResponse and ThreadResumeResponse (#6847)

  This adds the following fields to `ThreadStartResponse` and
  `ThreadResumeResponse`:
  
  ```rust
      pub model: String,
      pub model_provider: String,
      pub cwd: PathBuf,
      pub approval_policy: AskForApproval,
      pub sandbox: SandboxPolicy,
      pub reasoning_effort: Option<ReasoningEffort>,
  ```
  
  This is important because these fields are optional in
  `ThreadStartParams` and `ThreadResumeParams`, so the caller needs to be
  able to determine what values were ultimately used to start/resume the
  conversation. (Though note that any of these could be changed later
  between turns in the conversation.)
  
  Though to get this information reliably, it must be read from the
  internal `SessionConfiguredEvent` that is created in response to the
  start of a conversation. Because `SessionConfiguredEvent` (as defined in
  `codex-rs/protocol/src/protocol.rs`) did not have all of these fields, a
  number of them had to be added as part of this PR.
  
  Because `SessionConfiguredEvent` is referenced in many tests, test
  instances of `SessionConfiguredEvent` had to be updated, as well, which
  is why this PR touches so many files.

  Michael Bolin · 2025-11-18 21:18:43 -08:00
  a75321a64c
• Remote compaction on by-default (#6866)
  pakrym-oai · 2025-11-19 02:21:57 +00:00
  cac0a6a29d
• windows sandbox: support multiple workspace roots (#6854)

  The Windows sandbox did not previously support multiple workspace roots
  via config. Now it does

  iceweasel-oai · 2025-11-18 16:35:00 -08:00
  cf57320b9f
• fix: local compaction (#6844)
  jif-oai · 2025-11-18 22:18:10 +00:00
  c56d0c159b
• [codex][otel] support mtls configuration (#6228)

  fix for https://github.com/openai/codex/issues/6153
  
  supports mTLS configuration and includes TLS features in the library
  build to enable secure HTTPS connections with custom root certificates.
  
  grpc:
  https://docs.rs/tonic/0.13.1/src/tonic/transport/channel/endpoint.rs.html#63
  https:
  https://docs.rs/reqwest/0.12.23/src/reqwest/async_impl/client.rs.html#516

  Anton Panasenko · 2025-11-18 14:01:01 -08:00
  f7a921039c
• feat: review in app server (#6613)
  jif-oai · 2025-11-18 21:58:54 +00:00
  8ddae8cde3
• chore(config) enable shell_command (#6843)

  ## Summary
  Enables shell_command as default for `gpt-5*` and `codex-*` models.
  
  ## Testing
  - [x] Updated unit tests

  Dylan Hurd · 2025-11-18 12:46:02 -08:00
  29ca89c414
• 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
• Add the utility to truncate by tokens (#6746)

  - This PR is to make it on path for truncating by tokens. This path will
  be initially used by unified exec and context manager (responsible for
  MCP calls mainly).
  - We are exposing new config `calls_output_max_tokens`
  - Use `tokens` as the main budget unit but truncate based on the model
  family by Introducing `TruncationPolicy`.
  - Introduce `truncate_text` as a router for truncation based on the
  mode.
  
  In next PRs:
  - remove truncate_with_line_bytes_budget
  - Add the ability to the model to override the token budget.

  Ahmed Ibrahim · 2025-11-18 11:36:23 -08:00
  3de8790714