Ahmed Ibrahim 431a10fc50 chore: unify history loading (#2736) ...

We have two ways of loading conversation with a previous history. Fork
conversation and the experimental resume that we had before. In this PR,
I am unifying their code path. The path is getting the history items and
recording them in a brand new conversation. This PR also constraint the
rollout recorder responsibilities to be only recording to the disk and
loading from the disk.

The PR also fixes a current bug when we have two forking in a row:
History 1:
<Environment Context>
UserMessage_1
UserMessage_2
UserMessage_3

**Fork with n = 1 (only remove one element)**
History 2:
<Environment Context>
UserMessage_1
UserMessage_2
<Environment Context>

**Fork with n = 1 (only remove one element)**
History 2:
<Environment Context>
UserMessage_1
UserMessage_2
**<Environment Context>**

This shouldn't happen but because we were appending the `<Environment
Context>` after each spawning and it's considered as _user message_.
Now, we don't add this message if restoring and old conversation.

431a10fc50 · 2025-09-02 22:44:29 +00:00

History

..

common

[tools] Add apply_patch tool (#2303)

2025-08-15 11:55:53 -04:00

fixtures

Improve SSE tests (#1546)

2025-07-12 16:53:55 -07:00

suite

chore: unify history loading (#2736)

2025-09-02 22:44:29 +00:00

all.rs

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

2025-08-24 11:10:53 -07:00

cli_responses_fixture.sse

Add CLI streaming integration tests (#1542)

2025-07-12 18:05:58 -07:00