richardopenai 74dcce594d [codex] Trace exec-server JSON-RPC requests (#27466) ...

## Why

Exec-server JSON-RPC calls can cross local and remote transports, but
trace context stopped at the RPC boundary. That made client and server
work difficult to correlate when diagnosing latency or failures.

## What changed

- Propagate the current W3C trace context on outbound JSON-RPC requests.
- Parent inbound request spans from received trace context.
- Record the received JSON-RPC method on server spans and keep each span
open through response enqueue.
- Add only the OTEL dependencies required by the exec-server crate.

## Stack

Review and land this stack in order:

1. #27466 — trace exec-server JSON-RPC requests **(this PR)**
2. #27467 — record bounded connection, request, and process lifecycle
metrics
3. #27470 — observe remote registration and Noise rendezvous lifecycle

## Validation

- `just test -p codex-exec-server --lib` (153 passed)
- `just bazel-lock-check`
- `just fix -p codex-exec-server`

74dcce594d · 2026-06-24 12:50:18 -07:00

History

..

exec_server.rs

[codex] Trace exec-server JSON-RPC requests (#27466)

2026-06-24 12:50:18 -07:00

mod.rs

Run fs helper through Windows sandbox wrapper (#28359)

2026-06-17 10:00:42 -07:00