Skip to content

Trim TUI legacy telemetry and migration dependencies - #27487

Merged
etraut-openai merged 4 commits into
mainfrom
etraut/tui-legacy-telemetry-migration
Jun 11, 2026
Merged

Trim TUI legacy telemetry and migration dependencies#27487
etraut-openai merged 4 commits into
mainfrom
etraut/tui-legacy-telemetry-migration

Conversation

@etraut-openai

@etraut-openai etraut-openai commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Why

The TUI still reached through codex-app-server-client::legacy_core for process telemetry setup and personality migration, exposing core-only details after the TUI moved onto the app-server layer.

This is part of our ongoing efforts to whittle away at the legacy_core shim that was left over after migrating the TUI to the app server.

This change is just a refactor/rename and should be behavior-neutral and low risk.

What changed

  • expose OTEL provider construction through the app-server client and keep the small process/SQLite telemetry adapters local to the TUI
  • collapse personality migration results to the config-reload decision the TUI needs
  • remove the legacy_core::otel_init and legacy_core::personality_migration subnamespaces

@etraut-openai
etraut-openai marked this pull request as ready for review June 10, 2026 22:48
@etraut-openai etraut-openai changed the title [codex] trim TUI legacy telemetry and migration dependencies Trim TUI legacy telemetry and migration dependencies Jun 10, 2026
…emetry-migration

# Conflicts:
#	codex-rs/app-server-client/src/lib.rs
…ation' into etraut/tui-legacy-telemetry-migration
@etraut-openai
etraut-openai merged commit ab4ce40 into main Jun 11, 2026
46 of 47 checks passed
@etraut-openai
etraut-openai deleted the etraut/tui-legacy-telemetry-migration branch June 11, 2026 02:50
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants