Execution Traces

Viewing Traces

Open conversation and workflow traces to inspect runs event by event.

Overseer exposes traces directly in the product so you do not have to guess how a run happened.

Conversation Traces

Open a conversation and inspect the right-side trace panel. You can see the recorded runs and drill into the event timeline for the selected run.

Workflow Traces

Workflow runs can also link back to conversation-backed execution logs. This lets you inspect a workflow with the same mental model you use for chat.

Event Timeline

Read the timeline in order: decision, supervisor dispatch, tool activity, result status, and synthesis. If one of those layers is missing or vague, that is a product signal worth fixing.

What to Look For

  • Did the orchestrator choose the right mode?
  • Did the supervisor stay inside its domain?
  • Did any tool fail or time out?
  • Was the final result verified or just plausible?

Next Steps

Continue with Trace Analysis to turn trace reading into an operator habit instead of a last resort.