Charlie Marsh efa97f9bc6 Show onboarding when Codex home lacks authentication state (#38644) ...

## Why

Routine state such as history, logs, sessions, or temporary files does not mean
that the default account can authenticate. Treating any non-pristine Codex home
as configured can show the composer before onboarding is complete.

## What changed

- Base the startup decision on authentication-relevant state instead of requiring
  an empty Codex home. Existing credentials, configuration, workload identity,
  managed configuration, or a running local daemon continue to keep the composer
  visible.
- Treat an unreadable or ambiguous home conservatively and keep the composer
  visible.
- Allow onboarding when the legacy `--search` flag is the only configuration
  override.

## Testing

Expanded startup preflight and draft tests to cover existing home state,
credential sources, workload identity markers, daemon state, ambiguous paths,
and search-only overrides.

GitOrigin-RevId: 76837e3fd6aa714f2a7f72d191088a3faae23515

2026-08-14 20:38:52 +00:00

..

frames

Rename tui_app_server to tui (#16104)

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

src

Show onboarding when Codex home lacks authentication state (#38644)

2026-08-14 20:38:52 +00:00

tests

Keep the composer editable during TUI startup (#38642)

2026-08-14 20:30:30 +00:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

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

Cargo.toml

Extract persisted history types into a dedicated crate (#37871)

2026-08-10 19:26:52 +00: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