Charlie Marsh 7ed19a9758 Batch persistent history reads during reverse search (#33905) ...

## Why

Reverse search fetched persistent history one entry at a time, making a deep or unsuccessful search require a lookup for every older entry.

## What changed

- Keep the newest-entry probe lightweight, then scan older persistent history in bounded batches.
- Cache batch results by absolute offset and preserve continuation cursors across repeated searches.
- Ignore stale responses, retry failed batch reads a bounded number of times, and restore the draft without reporting a false “no match” state when history is unavailable.

## Testing

- Cover batch continuation, caching after query changes or cancellation, stale metadata, retry exhaustion, and thread routing.
- Verify that scanning 1,024 entries uses one single-entry lookup and eight batch lookups.

GitOrigin-RevId: efc791fcbd5290050af703dd31c5c21b33240e23

2026-07-17 21:16:07 +00:00

..

frames

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

src

Batch persistent history reads during reverse search (#33905)

2026-07-17 21:16:07 +00:00

tests

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

Allow ChatGPT accounts without email (#28991)

2026-06-22 13:19:40 -07:00

prompt_for_init_command.md

Reduce TUI legacy core dependencies (#26711)

2026-06-09 13:26:00 -07:00

styles.md

Rename tui_app_server to tui (#16104)

2026-03-28 11:23:07 -06:00

tooltips.txt

Support ChatGPT-branded Desktop app builds (#33901)

2026-07-17 20:46:18 +00:00