rphilizaire-openai 322e33512b [codex] trace MCP startup latency (#28630) ...

## Summary

- add trace-level instrumentation around per-server MCP setup, client
construction, initialization, and initial tool listing
- trace Codex Apps tool and server-info cache loads
- attach `server_name` to server-scoped spans so slow startup work can
be attributed to a specific MCP server

## Why

`session_init.mcp_manager_init` can occasionally be slow, but its
existing coarse span does not identify whether time is spent loading the
Codex Apps cache, constructing a client, initializing a transport, or
listing tools. These definition-level spans provide that breakdown
without changing startup behavior.

## Validation

- `just test -p codex-mcp` (87 passed)
- `just test -p codex-rmcp-client` (86 passed, 2 skipped)

322e33512b · 2026-06-23 17:46:54 -07:00

History

..

src

[codex] trace MCP startup latency (#28630)

2026-06-23 17:46:54 -07:00

BUILD.bazel

Extract MCP into codex-mcp crate (#15919)

2026-04-01 19:03:26 -07:00

Cargo.toml

Scope MCP sandbox metadata to server environment (#28914)

2026-06-18 19:31:07 +02:00