Debugging cubepi runs with cubepi trace

cubepi can record every agent run as an OpenTelemetry span tree, written to local JSONL files. The cubepi trace CLI reads those files so you can see exactly what happened inside a run without re-running it: which LLM calls and tool calls fired, in what order, what each returned, where it errored, and the token/cache counts. Reach for this before guessing at a bug.

When this applies

• The final answer is missing, truncated, or the run "ended" with no reply.
• A tool (web_search, web_fetch, execute, MCP tool, …) returned something wrong or empty, or the agent looped.
• The model returned a 4xx/5xx (e.g. BadRequestError), or the run status is error.
• Token / cache / cost numbers look wrong.
• You just need to understand the agent's actual trajectory for a given input.

Prerequisites (one-time)