rphilizaire-openai bacfc5e4c0 [codex] add latency tracing spans (#27710) ...

## Why

We have some large gaps in our thread start, resume, and pre-sampling
traces that make it hard to tell where latency is coming from.

## What Changed

- Added coarse spans around thread start/resume, turn context
construction, rollout reconstruction, skill/plugin loading, and tool
preparation.
- Added a breakdown of discoverable-tool preparation across connector
loading, plugin discovery, and local plugin details.

## Testing

- `cargo check -p codex-app-server -p codex-core -p codex-core-skills -p
codex-core-plugins`
- Built the app-server locally and exercised thread start, first turn,
follow-up turn, server restart, thread resume, and a resumed turn.

bacfc5e4c0 · 2026-06-12 17:11:32 -07:00

History

..

src

[codex] add latency tracing spans (#27710)

2026-06-12 17:11:32 -07:00

BUILD.bazel

Extract plugin loading and marketplace logic into codex-core-plugins (#18070)

2026-04-15 23:13:17 -07:00

Cargo.toml

Extract shared plugin MCP config parsing (#27863)

2026-06-12 15:10:05 +02:00