Eric TrautandGitHub 43a69c50eb Use app server thread names in TUI picker (#18633) ...

## Problem

The TUI resume/fork picker was backfilling thread names from local
rollout indexes. This was left over from before the TUI was moved to the
app server. It should be using app-server APIs because the TUI might be
connected to a remote connection.

This bug wasn't (yet) reported by a user. I found it by asking Codex to
review places in the TUI code where it was still directly accessing the
CODEX_HOME directory rather than going through app-server APIs.

## Solution

The resume picker and session lookups should use app-server thread APIs
only. Remove legacy rollout name/list backfills, and avoid local name
reads in fork history.

## Testing

I manually tested `codex resume` and `codex resume --all` to look for
functional or performance regressions in the resume picker.

2026-04-20 08:16:24 -07:00

..

frames

Rename tui_app_server to tui (#16104)

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

src

Use app server thread names in TUI picker (#18633)

2026-04-20 08:16:24 -07:00

tests

Stabilize Bazel tests (timeout tweaks and flake fixes) (#17791)

2026-04-16 07:57:51 -07:00

BUILD.bazel

bazel: use native rust test sharding (#18082)

2026-04-17 23:14:11 +00:00

Cargo.toml

TUI: remove simple legacy_core re-exports (#18605)

2026-04-19 22:39:53 -07:00

prompt_for_init_command.md

Rename tui_app_server to tui (#16104)

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

styles.md

Rename tui_app_server to tui (#16104)

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

tooltips.txt

Add /side conversations (#18190)

2026-04-19 11:59:41 -07:00