ACAgentic Craft

Intermediate~26 minHazelJS

Inspector Timelines and Traces

Use runtime.getTimeline, FileTimelineStore, and Inspector endpoints to debug AgentRuns—with code.

Authors
editorial-team
Published
Last reviewed
Progress is stored locally in this browser.

Direct answer

runtime.getTimeline({ executionId }) (and agent-name variants) plus timeline stores and Inspector /__hazel/agents/.../timeline endpoints are the operator view of decisions and tool calls.

Docs: Observability, Inspector.

Worked example

typescript
const out = await runtime.execute('support-desk', 'Status of ORD-1001?', {
  maxSteps: 6,
});

const timeline = await runtime.getTimeline({
  executionId: out.executionId,
});
// Inspect steps: model proposals, tool calls, stop reason

// Local/dev: FileTimelineStore (see Agent OS / agent docs for wiring)
// CLI companion:
//   hazel agent logs --timeline .hazel/runs/timeline.jsonl

Minimum signals to keep

executionId, agent name, step index, tool name + arg hash (redacted), latency, tokens/USD, stop reason, HITL actors.

Next

/learn/observability-and-cost/cost-budgets-and-alerts

Artifact: Runbook: fetch timeline by executionId

Sources

Related