mirror of https://github.com/pchuan98/codex.git synced 2026-07-01 00:31:56 +08:00

Files

T

Owen Lin 8b7ec31ba7 feat(app-server): thread/rollback API (#8454 )

Add `thread/rollback` to app-server to support IDEs undo-ing the last N
turns of a thread.

For context, an IDE partner will be supporting an "undo" capability
where the IDE (the app-server client) will be responsible for reverting
the local changes made during the last turn. To support this well, we
also need a way to drop the last turn (or more generally, the last N
turns) from the agent's context. This is what `thread/rollback` does.

**Core idea**: A Thread rollback is represented as a persisted event
message (EventMsg::ThreadRollback) in the rollout JSONL file, not by
rewriting history. On resume, both the model's context (core replay) and
the UI turn list (app-server v2's thread history builder) apply these
markers so the pruned history is consistent across live conversations
and `thread/resume`.

Implementation notes:
- Rollback only affects agent context and appends to the rollout file;
clients are responsible for reverting files on disk.
- If a thread rollback is currently in progress, subsequent
`thread/rollback` calls are rejected.
- Because we use `CodexConversation::submit` and codex core tracks
active turns, returning an error on concurrent rollbacks is communicated
via an `EventMsg::Error` with a new variant
`CodexErrorInfo::ThreadRollbackFailed`. app-server watches for that and
sends the BAD_REQUEST RPC response.

Tests cover thread rollbacks in both core and app-server, including when
`num_turns` > existing turns (which clears all turns).

**Note**: this explicitly does **not** behave like `/undo` which we just
removed from the CLI, which does the opposite of what `thread/rollback`
does. `/undo` reverts local changes via ghost commits/snapshots and does
not modify the agent's context / conversation history.

8b7ec31ba7 · 2026-01-06 21:23:48 +00:00

History

src

feat(app-server): thread/rollback API (#8454 )

2026-01-06 21:23:48 +00:00

templates

Removed experimental "command risk assessment" feature (#7799 )

2025-12-10 09:48:11 -08:00

tests

feat: agent controller (#8783 )

2026-01-06 19:08:02 +00:00

Cargo.toml

feat: introduce codex-utils-cargo-bin as an alternative to assert_cmd::Command (#8496 )

2025-12-23 19:29:32 -08:00

gpt_5_1_prompt.md

chore(prompt) Remove truncation details (#7941 )

2025-12-12 20:21:53 +00:00

gpt_5_2_prompt.md

chore(prompt) Remove truncation details (#7941 )

2025-12-12 20:21:53 +00:00

gpt_5_codex_prompt.md

refactoring with_escalated_permissions to use SandboxPermissions instead (#7750 )

2025-12-10 17:18:48 +00:00

gpt-5.1-codex-max_prompt.md

refactoring with_escalated_permissions to use SandboxPermissions instead (#7750 )

2025-12-10 17:18:48 +00:00

gpt-5.2-codex_prompt.md

caribou (#8265 )

2025-12-18 08:58:44 -08:00

models.json

Update models.json (#8446 )

2025-12-22 12:05:05 -08:00

prompt.md

chore(prompt) Update base prompt (#7943 )

2025-12-12 20:50:49 +00:00

README.md

docs: align sandbox defaults, dedupe sections and improve getting started guide (#5357 )

2025-10-19 16:41:10 -07:00

review_prompt.md

docs: Fix markdown list item spacing in codex-rs/core/review_prompt.md (#4144 )

2025-10-30 17:39:21 -07:00

README.md

codex-core

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

Dependencies

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

macOS

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

Linux

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

All Platforms

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