Eric Traut a07158c784 Keep TUI prompt history tied to local settings (#42791) ...

## Why

Prompt history is client-owned state, but app-server thread lifecycle responses derived its metadata from the active server configuration. When server and local settings differ, the TUI can advertise metadata for the wrong history log.

## What changed

- Pass `LocalSettings` through thread start, resume, and fork response handling.
- Build message-history metadata from the local Codex home and history preferences while continuing to use the thread configuration for server-owned session fields.

## Testing

- Cover local history metadata across embedded and remote start, resume, and fork flows with deliberately different server settings.
- Verify single-entry and batched history lookups return entries from the local prompt history.

GitOrigin-RevId: 8b47230a4e9f2d342b8d79fd575d474c9062b05e

2026-09-04 15:58:02 +00:00

..

assets

Organize bundled Rust resources under asset directories (#41477)

2026-08-29 06:05:28 +00:00

frames

Rename tui_app_server to tui (#16104)

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

src

Keep TUI prompt history tied to local settings (#42791)

2026-09-04 15:58:02 +00:00

tests

Make the TUI symlink startup test Bazel-compatible (#42741)

2026-09-04 11:43:37 +00:00

BUILD.bazel

Make the TUI symlink startup test Bazel-compatible (#42741)

2026-09-04 11:43:37 +00:00

Cargo.toml

Support the app-server daemon on Windows (#42405)

2026-09-03 01:26:35 +00:00

styles.md

Rename tui_app_server to tui (#16104)

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