TraceID

Every run has a unique run ID. Trodo mints one for you, but you can also supply your own so a run lines up with an ID your systems already use: a request ID, a job ID, a trace ID from another tool.

Get the run ID

wrapAgent returns it; in Python, read it off the run.

const { result, runId } = await trodo.wrapAgent('my-agent', async (run) => { /* ... */ });

with trodo.wrap_agent('my-agent') as run:
    ...
run_id = run.run_id

Use it to filter runs, attach feedback, or correlate with your own logs.

Supply your own run ID

For long-running runs opened with startRun, pass a runId / run_id to correlate across processes or with an external ID.

const runId = await trodo.startRun('ingest', { runId: myJobId, conversationId: myJobId });

run_id = trodo.start_run('ingest', run_id=my_job_id, conversation_id=my_job_id)

Distributed tracing

When a run flows across services, the run ID travels on the X-Trodo-Run-Id header so downstream spans nest under the same run. You don't pass it by hand; the propagation helpers and middleware do it. See Distributed tracing.

Next

• Long-running & background runs for startRun with a custom ID
• Distributed tracing for cross-service correlation