Eric Traut 56958f2512 Seed prompt history from resumed messages (#24298) ...

## Why

When the TUI resumes a thread, transcript replay renders prior user
messages but did not seed the composer history. That leaves the resumed
session with empty in-memory prompt history, so pressing Up can fall
through to persisted global history and surface a prompt from another
thread.

The expected behavior is that prompts from the resumed thread are
recalled first, with global history only as a fallback.

## What changed

- Record replayed user messages into the composer history during resume
replay.
- Preserve the existing persisted history format and avoid any startup
history scan.
- Add focused TUI coverage showing replayed prompts are recalled before
persisted global history.

## Validation

- Added `replayed_user_messages_seed_composer_history` in
`codex-rs/tui/src/chatwidget/tests/history_replay.rs`.
- `just test -p codex-tui replayed_user_messages_seed_composer_history`
passed.

2026-05-28 22:08:05 -07:00

..

src

Seed prompt history from resumed messages (#24298)

2026-05-28 22:08:05 -07:00

BUILD.bazel

[apps] Add tool_suggest tool. (#14287)

2026-03-11 22:06:59 -07:00

Cargo.toml

Using cached connector directory for discoverable tools list (#21497)

2026-05-08 14:14:11 -07:00