Trace capture records finalized Claude Code and Codex sessions locally, then a
background daemon exports them as OpenTelemetry traces.
Preview. Use this loop with a non-sensitive coding session before you
rely on trace delivery in a team workflow.
Install and verify the integration
Install integrations before starting a coding-agent session. The command owns
only its managed hook entries and preserves unrelated configuration.
Capture one session
Start a new Claude Code or Codex session after the integration doctor succeeds,
then complete a small non-sensitive task. The integration records finalized
sessions; it does not alter the agent’s task or permissions.
The session list should contain the completed session. Outbox status shows
whether the local runtime still needs to deliver it. The active Registry CLI
workspace does not control trace attribution; trace capture resolves its own
workspace and identity.
Recover a missing delivery
reconcile asks the daemon to rescan local content and retry skill upload,
repository onboarding, and session backfill immediately. Inspect outbox status
before requeuing a dead-letter item; requeue changes delivery state.
Capture policy and local data
Review the resolved capture policy before enabling content storage or purging
local data.
Verify or escalate
Use the destination product or trace read surface to find the matching session
and attribution. A local outbox success alone does not prove that the intended
workspace can read the trace.
Inspect a support bundle before sharing it. Runtime rollback changes the active
installed version but preserves local journal state. 
