Owen Lin 27724f6ead feat(core, tracing): add a span representing a turn (#13424) ...

This is PR 3 of the app-server tracing rollout.

PRs https://github.com/openai/codex/pull/13285 and
https://github.com/openai/codex/pull/13368 gave us inbound request spans
in app-server and propagated trace context through Submission. This
change finishes the next piece in core: when a request actually starts a
turn, we now create a core-owned long-lived span that stays open for the
real lifetime of the turn.

What changed:
- `Session::spawn_task` can now optionally create a long-lived turn span
and run the spawned task inside it
- `turn/start` uses that path, so normal turn execution stays under a
single core-owned span after the async handoff
- `review/start` uses the same pattern
- added a unit test that verifies the spawned turn task inherits the
submission dispatch trace ancestry

**Why**
The app-server request span is intentionally short-lived. Once work
crosses into core, we still want one span that covers the actual
execution window until completion or interruption. This keeps that
ownership where it belongs: in the layer that owns the runtime
lifecycle.

27724f6ead · 2026-03-04 11:09:17 -08:00

History

..

compact.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00

ghost_snapshot.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00

mod.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00

regular.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00

review.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00

undo.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00

user_shell.rs

feat(core, tracing): add a span representing a turn (#13424)

2026-03-04 11:09:17 -08:00