Understanding Traces
See what Overseer records about decisions, tool calls, and final synthesis.
Traces are how you tell the difference between a system that sounds smart and a system that actually did the work.
What a Trace Captures
Overseer records execution runs and execution events. Those events capture things like orchestration decisions, supervisor steps, tool calls, status changes, and final synthesis.
Decision Layer
The trace shows whether the orchestrator classified the request as direct chat, single-domain, or multi-step work. That alone is often enough to debug why a run felt too heavy or too shallow.
Execution Layer
Once work reaches a supervisor, the trace becomes the operational log: which tool ran, what status came back, and whether the result was completed, unverified, or failed.
Trust Layer
The most important question is not "did I get an answer?" It is "what evidence supports this answer?" Traces make that question visible.
Next Steps
Continue with Viewing Traces to inspect runs in the desktop UI.