50 Commits

• Improve Default mode prompt (less confusion with Plan mode) (#10545)

  ## Summary
  
  This PR updates `request_user_input` behavior and Default-mode guidance
  to match current collaboration-mode semantics and reduce model
  confusion.
  
  ## Why
  
  - `request_user_input` should be explicitly documented as **Plan-only**.
  - Tool description and runtime availability checks should be driven by
  the **same centralized mode policy**.
  - Default mode prompt needed stronger execution guidance and explicit
  instruction that `request_user_input` is unavailable.
  - Error messages should report the **actual mode name** (not aliases
  that can read as misleading).
  
  ## What changed
  
  - Centralized `request_user_input` mode policy in `core` handler logic:
    - Added a single allowed-modes config (`Plan` only).
    - Reused that policy for:
      - runtime rejection messaging
      - tool description text
  - Updated tool description to include availability constraint:
    - `"This tool is only available in Plan mode."`
  - Updated runtime rejection behavior:
    - `Default` -> `"request_user_input is unavailable in Default mode"`
    - `Execute` -> `"request_user_input is unavailable in Execute mode"`
  - `PairProgramming` -> `"request_user_input is unavailable in Pair
  Programming mode"`
  - Strengthened Default collaboration prompt:
    - Added explicit execution-first behavior
    - Added assumptions-first guidance
    - Added explicit `request_user_input` unavailability instruction
    - Added concise progress-reporting expectations
  - Simplified formatting implementation:
    - Inlined allowed-mode name collection into `format_allowed_modes()`
  - Kept `format_allowed_modes()` output for 3+ modes as CSV style
  (`modes: a,b,c`)

  Charley Cunningham · 2026-02-03 12:08:38 -08:00
  998eb8f32b
• Cleanup collaboration mode variants (#10404)

  ## Summary
  
  This PR simplifies collaboration modes to the visible set `default |
  plan`, while preserving backward compatibility for older partners that
  may still send legacy mode
  names.
  
  Specifically:
  - Renames the old Code behavior to **Default**.
  - Keeps **Plan** as-is.
  - Removes **Custom** mode behavior (fallbacks now resolve to Default).
  - Keeps `PairProgramming` and `Execute` internally for compatibility
  plumbing, while removing them from schema/API and UI visibility.
  - Adds legacy input aliasing so older clients can still send old mode
  names.
  
  ## What Changed
  
  1. Mode enum and compatibility
  - `ModeKind` now uses `Plan` + `Default` as active/public modes.
  - `ModeKind::Default` deserialization accepts legacy values:
    - `code`
    - `pair_programming`
    - `execute`
    - `custom`
  - `PairProgramming` and `Execute` variants remain in code but are hidden
  from protocol/schema generation.
  - `Custom` variant is removed; previous custom fallbacks now map to
  `Default`.
  
  2. Collaboration presets and templates
  - Built-in presets now return only:
    - `Plan`
    - `Default`
  - Template rename:
    - `core/templates/collaboration_mode/code.md` -> `default.md`
  - `execute.md` and `pair_programming.md` remain on disk but are not
  surfaced in visible preset lists.
  
  3. TUI updates
  - Updated user-facing naming and prompts from “Code” to “Default”.
  - Updated mode-cycle and indicator behavior to reflect only visible
  `Plan` and `Default`.
  - Updated corresponding tests and snapshots.
  
  4. request_user_input behavior
  - `request_user_input` remains allowed only in `Plan` mode.
  - Rejection messaging now consistently treats non-plan modes as
  `Default`.
  
  5. Schemas
  - Regenerated config and app-server schemas.
  - Public schema types now advertise mode values as:
    - `plan`
    - `default`
  
  ## Backward Compatibility Notes
  
  - Incoming legacy mode names (`code`, `pair_programming`, `execute`,
  `custom`) are accepted and coerced to `default`.
  - Outgoing/public schema surfaces intentionally expose only `plan |
  default`.
  - This allows tolerant ingestion of older partner payloads while
  standardizing new integrations on the reduced mode set.
  
  ## Codex author
  `codex fork 019c1fae-693b-7840-b16e-9ad38ea0bd00`

  Charley Cunningham · 2026-02-03 09:23:53 -08:00
  d509df676b
• fix(personality) prompt patch (#10375)

  ## Summary
  We had 2 typos in #10373
  
  ## Testing
  - [x] unit tests pass

  Dylan Hurd · 2026-02-01 23:32:07 -08:00
  08a5ad95a8
• chore(core) gpt-5.2-codex personality template (#10373)

  ## Summary
  Consolidate prompts
  
  ## Testing
  - [x] Existing tests pass

  Dylan Hurd · 2026-02-01 22:54:12 -08:00
  a90ff831e7
• Improve plan mode interaction rules (#10329)

  ## Summary
  - Replace the “Hard interaction rule” with a clearer “Response
  constraints” section that enumerates the allowed exceptions for Plan
  Mode replies.
  - Remove the stray Phase 1 exception line about simple questions.
  - Update plan content requirements to ask for a brief summary section
  and generalize API/type wording.

  Charley Cunningham · 2026-01-31 23:20:27 -08:00
  3dd9a37e0b
• plan mode prompt (#10308)

  # 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 · 2026-01-31 13:55:52 -08:00
  2d6757430a
• plan prompt (#10255)

  # 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 · 2026-01-30 12:22:37 -08:00
  b7351f7f53
• Plan mode prompt (#10238)

  # 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 · 2026-01-30 11:48:03 -08:00
  9b29a48a09
• Plan mode: stream proposed plans, emit plan items, and render in TUI (#9786)

  ## Summary
  - Stream proposed plans in Plan Mode using `<proposed_plan>` tags parsed
  in core, emitting plan deltas plus a plan `ThreadItem`, while stripping
  tags from normal assistant output.
  - Persist plan items and rebuild them on resume so proposed plans show
  in thread history.
  - Wire plan items/deltas through app-server protocol v2 and render a
  dedicated proposed-plan view in the TUI, including the “Implement this
  plan?” prompt only when a plan item is present.
  
  ## Changes
  
  ### Core (`codex-rs/core`)
  - Added a generic, line-based tag parser that buffers each line until it
  can disprove a tag prefix; implements auto-close on `finish()` for
  unterminated tags. `codex-rs/core/src/tagged_block_parser.rs`
  - Refactored proposed plan parsing to wrap the generic parser.
  `codex-rs/core/src/proposed_plan_parser.rs`
  - In plan mode, stream assistant deltas as:
    - **Normal text** → `AgentMessageContentDelta`
    - **Plan text** → `PlanDelta` + `TurnItem::Plan` start/completion  
    (`codex-rs/core/src/codex.rs`)
  - Final plan item content is derived from the completed assistant
  message (authoritative), not necessarily the concatenated deltas.
  - Strips `<proposed_plan>` blocks from assistant text in plan mode so
  tags don’t appear in normal messages.
  (`codex-rs/core/src/stream_events_utils.rs`)
  - Persist `ItemCompleted` events only for plan items for rollout replay.
  (`codex-rs/core/src/rollout/policy.rs`)
  - Guard `update_plan` tool in Plan Mode with a clear error message.
  (`codex-rs/core/src/tools/handlers/plan.rs`)
  - Updated Plan Mode prompt to:  
    - keep `<proposed_plan>` out of non-final reasoning/preambles  
    - require exact tag formatting  
    - allow only one `<proposed_plan>` block per turn  
    (`codex-rs/core/templates/collaboration_mode/plan.md`)
  
  ### Protocol / App-server protocol
  - Added `TurnItem::Plan` and `PlanDeltaEvent` to core protocol items.
  (`codex-rs/protocol/src/items.rs`, `codex-rs/protocol/src/protocol.rs`)
  - Added v2 `ThreadItem::Plan` and `PlanDeltaNotification` with
  EXPERIMENTAL markers and note that deltas may not match the final plan
  item. (`codex-rs/app-server-protocol/src/protocol/v2.rs`)
  - Added plan delta route in app-server protocol common mapping.
  (`codex-rs/app-server-protocol/src/protocol/common.rs`)
  - Rebuild plan items from persisted `ItemCompleted` events on resume.
  (`codex-rs/app-server-protocol/src/protocol/thread_history.rs`)
  
  ### App-server
  - Forward plan deltas to v2 clients and map core plan items to v2 plan
  items. (`codex-rs/app-server/src/bespoke_event_handling.rs`,
  `codex-rs/app-server/src/codex_message_processor.rs`)
  - Added v2 plan item tests.
  (`codex-rs/app-server/tests/suite/v2/plan_item.rs`)
  
  ### TUI
  - Added a dedicated proposed plan history cell with special background
  and padding, and moved “• Proposed Plan” outside the highlighted block.
  (`codex-rs/tui/src/history_cell.rs`, `codex-rs/tui/src/style.rs`)
  - Only show “Implement this plan?” when a plan item exists.
  (`codex-rs/tui/src/chatwidget.rs`,
  `codex-rs/tui/src/chatwidget/tests.rs`)
  
  <img width="831" height="847" alt="Screenshot 2026-01-29 at 7 06 24 PM"
  src="https://github.com/user-attachments/assets/69794c8c-f96b-4d36-92ef-c1f5c3a8f286"
  />
  
  ### Docs / Misc
  - Updated protocol docs to mention plan deltas.
  (`codex-rs/docs/protocol_v1.md`)
  - Minor plumbing updates in exec/debug clients to tolerate plan deltas.
  (`codex-rs/debug-client/src/reader.rs`, `codex-rs/exec/...`)
  
  ## Tests
  - Added core integration tests:
    - Plan mode strips plan from agent messages.
    - Missing `</proposed_plan>` closes at end-of-message.  
    (`codex-rs/core/tests/suite/items.rs`)
  - Added unit tests for generic tag parser (prefix buffering, non-tag
  lines, auto-close). (`codex-rs/core/src/tagged_block_parser.rs`)
  - Existing app-server plan item tests in v2.
  (`codex-rs/app-server/tests/suite/v2/plan_item.rs`)
  
  ## Notes / Behavior
  - Plan output no longer appears in standard assistant text in Plan Mode;
  it streams via `PlanDelta` and completes as a `TurnItem::Plan`.
  - The final plan item content is authoritative and may diverge from
  streamed deltas (documented as experimental).
  - Reasoning summaries are not filtered; prompt instructs the model not
  to include `<proposed_plan>` outside the final plan message.
  
  ## Codex Author
  `codex fork 019bec2d-b09d-7450-b292-d7bcdddcdbfb`

  Charley Cunningham · 2026-01-30 18:59:30 +00:00
  ec4a2d07e4
• plan mode: add TL;DR checkpoint and client behavior note (#10195)

  ## Summary
  - Tightens Plan Mode to encourage exploration-first behavior and more
  back-and-forth alignment.
  - Adds a required TL;DR checkpoint before drafting the full plan.
  - Clarifies client behavior that can cause premature “Implement this
  plan?” prompts.
  
  ## What changed
  - Require at least one targeted non-mutating exploration pass before the
  first user question.
  - Insert a TL;DR checkpoint between Phase 2 (intent) and Phase 3
  (implementation).
  - TL;DR checkpoint guidance:
    - Label: “Proposed Plan (TL;DR)”
    - Format: 3–5 bullets using `- `
    - Options: exactly one option, “Approve”
  - `isOther: true`, with explicit guidance that “None of the above” is
  the edit path in the current UI.
  - Require the final plan to include a TL;DR consistent with the approved
  checkpoint.
  
  ## Why
  - In Plan Mode, any normal assistant message at turn completion is
  treated as plan content by the client. This can trigger premature
  “Implement this plan?” prompts.
  - The TL;DR checkpoint aligns on direction before Codex drafts a long,
  decision-complete plan.
  
  ## Testing
  - Manual: built the local CLI and verified the flow now explores first,
  presents a TL;DR checkpoint, and only drafts the full plan after
  approval.
  
  ---------
  
  Co-authored-by: Nick Baumann <@openai.com>

  baumann-oai · 2026-01-30 10:14:46 -08:00
  1ce722ed2e
• chore(personality) new schema with fallbacks (#10147)

  ## Summary
  Let's dial in this api contract in a bit more with more robust fallback
  behavior when model_instructions_template is false.
  
  Switches to a more explicit template / variables structure, with more
  fallbacks.
  
  ## Testing
  - [x] Adding unit tests
  - [x] Tested locally

  Dylan Hurd · 2026-01-30 00:10:12 -07:00
  e3ab0bd973
• chore(config) Update personality instructions (#10114)

  ## Summary
  Add personality instructions so we can let users try it out, in tandem
  with making it an experimental feature
  
  ## Testing
  - [x] Tested locally

  Dylan Hurd · 2026-01-29 01:14:44 +00:00
  9757e1418d
• chore: clean orchestrator prompt (#9994)
  jif-oai · 2026-01-27 16:32:05 +00:00
  3b726d9550
• nit: better unused prompt (#9991)
  jif-oai · 2026-01-27 13:03:12 +00:00
  74ffbbe7c1
• make plan prompt less detailed (#9977)

  This was too much to ask for

  Ahmed Ibrahim · 2026-01-26 21:42:01 -08:00
  cabb2085cc
• tui: wrapping user input questions (#9971)
  Ahmed Ibrahim · 2026-01-26 21:30:09 -08:00
  4db6da32a3
• plan prompt (#9975)

  # 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 · 2026-01-26 21:14:05 -08:00
  28bd7db14a
• prompt (#9970)

  # 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 · 2026-01-26 20:27:57 -08:00
  0c72d8fd6e
• prompt final (#9969)

  hopefully final this time (at least tonight) >_<

  Ahmed Ibrahim · 2026-01-26 20:12:43 -08:00
  f45a8733bf
• Improve plan mode prompt (#9968)

  # 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 · 2026-01-26 19:56:16 -08:00
  b655a092ba
• plan prompt v7 (#9966)

  # 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 · 2026-01-26 19:34:18 -08:00
  b7bba3614e
• plan prompt (#9943)

  # 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 · 2026-01-26 14:48:54 -08:00
  159ff06281
• prompt (#9928)

  # 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 · 2026-01-26 10:27:18 -08:00
  e471ebc5d2
• fix: attempt to reduce high cpu usage when using collab (#9776)

  Reproduce with a prompt like this with collab enabled:
  ```
  Examine the code at <some subdirectory with a deeply nested project>.  Find the most urgent issue to resolve and describe it to me.
  ```
  
  Existing behavior causes the top-level agent to busy wait on subagents.

  Gene Oden · 2026-01-26 10:07:25 -08:00
  375a5ef051
• Plan prompt (#9877)

  # 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 · 2026-01-25 19:50:35 -08:00
  d27f2533a9
• Prompt (#9874)

  # 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 · 2026-01-25 18:24:25 -08:00
  0f798173d7
• Remove batman reference from experimental prompt (#9812)

  https://www.reddit.com/r/codex/comments/1qldbmg/if_you_enable_experimental_subagents_in_openai/

  Charley Cunningham · 2026-01-24 14:24:36 +01:00
  eb7558ba85
• Have a coding mode and only show coding and plan (#9802)
  Ahmed Ibrahim · 2026-01-23 19:28:49 -08:00
  b3127e2eeb
• prompt (#9777)

  # 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 · 2026-01-23 19:24:48 +00:00
  f353d3d695
• Change the prompt for planning and reasoning effort (#9733)

  Change the prompt for planning and reasoning effort preset for better
  experience

  Ahmed Ibrahim · 2026-01-22 18:22:12 -08:00
  d86bd20411
• Fix typo in experimental_prompt.md (#9716)

  Simple typo fix in the first sentence of the experimental_prompt.md
  instructions file.

  iudi · 2026-01-22 14:07:14 -08:00
  afd63e8bae
• Chore: update plan mode output in prompt (#9592)

  ### Summary
  * Update plan prompt output
  * Update requestUserInput response to be a single key value pair
  `answer: String`.

  Shijie Rao · 2026-01-21 14:12:18 -08:00
  3fcb40245e
• feat(personality) introduce model_personality config (#9459)

  ## Summary
  Introduces the concept of a config model_personality. I would consider
  this an MVP for testing out the feature. There are a number of
  follow-ups to this PR:
  
  - More sophisticated templating with validation
  - In-product experience to manage this
  
  ## Testing
  - [x] Testing locally

  Dylan Hurd · 2026-01-20 11:06:14 -08:00
  714151eb4e
• Feat: plan mode prompt update (#9495)

  ### Summary
  * Added instruction on using `request_user_input`
  * Added the output to be json with `plan` key and the actual plan as the
  value.
  * Remove `PLAN.md` write because that gets into sandbox issue. We can
  add it back later.

  Shijie Rao · 2026-01-19 12:17:29 -08:00
  d544adf71a
• prompt 3 (#9479)
  jif-oai · 2026-01-19 11:56:38 +00:00
  3c28c85063
• Add collaboration modes test prompts (#9443)

  # 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 · 2026-01-18 11:39:08 -08:00
  f72f87fbee
• prompt collab (#9367)
  jif-oai · 2026-01-16 15:12:41 +01:00
  7905e99d03
• chore: better orchestrator prompt (#9301)
  jif-oai · 2026-01-15 18:11:43 +00:00
  393a5a0311
• feat: add agent roles to collab tools (#9275)

  Add `agent_type` parameter to the collab tool `spawn_agent` that
  contains a preset to apply on the config when spawning this agent

  jif-oai · 2026-01-15 13:33:52 +00:00
  05b960671d
• feat: add collab prompt (#9208)

  Adding a prompt for collab tools. This is only for internal use and the
  prompt won't be gated for now as it is not stable yet.
  
  The goal of this PR is to provide the tool required to iterate on the
  prompt

  jif-oai · 2026-01-14 09:58:15 -08:00
  3d322fa9d8
• Removed experimental "command risk assessment" feature (#7799)

  This experimental feature received lukewarm reception during internal
  testing. Removing from the code base.

  Eric Traut · 2025-12-10 09:48:11 -08:00
  c4af707e09
• chore: enable parallel tc (#7589)
  jif-oai · 2025-12-09 17:00:56 +00:00
  6382dc2338
• fix: parallel tool call instruction injection (#6893)
  jif-oai · 2025-11-19 11:01:57 +00:00
  4985a7a444
• feat: enable parallel tool calls (#6796)
  jif-oai · 2025-11-18 17:10:14 +00:00
  f5d9939cda
• Improve compact (#6692)

  This PR does the following:
  - Add compact prefix to the summary
  - Change the compaction prompt
  - Allow multiple compaction for long running tasks
  - Filter out summary messages on the following compaction
  
  Considerations:
  - Filtering out the summary message isn't the most clean
  - Theoretically, we can end up in infinite compaction loop if the user
  messages > compaction limit . However, that's not possible in today's
  code because we have hard cap on user messages.
  - We need to address having multiple user messages because it confuses
  the model.
  
  Testing:
  - Making sure that after compact we always end up with one user message
  (task) and one summary, even on multiple compaction.

  Ahmed Ibrahim · 2025-11-15 07:17:51 +00:00
  0b28e72b66
• Changes to sandbox command assessment feature based on initial experiment feedback (#6091)

  * Removed sandbox risk categories; feedback indicates that these are not
  that useful and "less is more"
  * Tweaked the assessment prompt to generate terser answers
  * Fixed bug in orchestrator that prevents this feature from being
  exposed in the extension

  Eric Traut · 2025-11-01 14:52:23 -07:00
  d5853d9c47
• feat: compactor 2 (#6027)

  Co-authored-by: pakrym-oai <pakrym@openai.com>

  jif-oai · 2025-10-31 14:27:08 -07:00
  611e00c862
• Delegate review to codex instance (#5572)

  In this PR, I am exploring migrating task kind to an invocation of
  Codex. The main reason would be getting rid off multiple
  `ConversationHistory` state and streamlining our context/history
  management.
  
  This approach depends on opening a channel between the sub-codex and
  codex. This channel is responsible for forwarding `interactive`
  (`approvals`) and `non-interactive` events. The `task` is responsible
  for handling those events.
  
  This opens the door for implementing `codex as a tool`, replacing
  `compact` and `review`, and potentially subagents.
  
  One consideration is this code is very similar to `app-server` specially
  in the approval part. If in the future we wanted an interactive
  `sub-codex` we should consider using `codex-mcp`

  Ahmed Ibrahim · 2025-10-29 21:04:25 +00:00
  13e1d0362d
• Added model summary and risk assessment for commands that violate sandbox policy (#5536)

  This PR adds support for a model-based summary and risk assessment for
  commands that violate the sandbox policy and require user approval. This
  aids the user in evaluating whether the command should be approved.
  
  The feature works by taking a failed command and passing it back to the
  model and asking it to summarize the command, give it a risk level (low,
  medium, high) and a risk category (e.g. "data deletion" or "data
  exfiltration"). It uses a new conversation thread so the context in the
  existing thread doesn't influence the answer. If the call to the model
  fails or takes longer than 5 seconds, it falls back to the current
  behavior.
  
  For now, this is an experimental feature and is gated by a config key
  `experimental_sandbox_command_assessment`.
  
  Here is a screen shot of the approval prompt showing the risk assessment
  and summary.
  
  <img width="723" height="282" alt="image"
  src="https://github.com/user-attachments/assets/4597dd7c-d5a0-4e9f-9d13-414bd082fd6b"
  />

  Eric Traut · 2025-10-24 15:23:44 -07:00
  f8af4f5c8d
• feat: context compaction (#3446)

  ## Compact feature:
  1. Stops the model when the context window become too large
  2. Add a user turn, asking for the model to summarize
  3. Build a bridge that contains all the previous user message + the
  summary. Rendered from a template
  4. Start sampling again from a clean conversation with only that bridge

  jif-oai · 2025-09-12 13:07:10 -07:00
  ea225df22e