Run Inspector & Trace Viewer
Eric includes two layers of debugging:
- Run Inspector for a single assistant run
- Trace Viewer for the full conversation session
Both are admin-only.
Run Inspector
Section titled “Run Inspector”Run Inspector is opened from the activity icon on an assistant message inside chat.
What it shows
Section titled “What it shows”- Run status
- Final model name
- Total latency
- Token count
- Event count
- Prompt breakdown data when available
- Raw run event timeline
When to use it
Section titled “When to use it”Use Run Inspector when you need to answer questions like:
- Why was this one answer slow?
- Did Eric call the tool I expected?
- Did the run emit an error event?
- How many tokens did the run consume?
Trace Viewer
Section titled “Trace Viewer”Trace Viewer is the deeper, session-level debugging screen at /eric/traces/:sessionId.
You can open it from:
- The activity button beside a session in the Eric sidebar
- A direct trace URL
What it adds beyond Run Inspector
Section titled “What it adds beyond Run Inspector”- A full session export, not just one run
- Runs grouped into story-style chapters
- Linked user messages that triggered each run
- Trace graph nodes and relationships
- Operator findings and recommended actions
- Session diagnostics such as run counts and negative feedback count
- LangSmith references when available
Trace stages
Section titled “Trace stages”The trace graph groups activity into these stages:
| Stage | Meaning |
|---|---|
| Input | The user prompt that started work |
| Context | Context loading and retrieval |
| Planning | Internal planning and prompt budgeting |
| Tooling | Tool execution and result handling |
| Output | Final answer generation |
| Feedback | User feedback attached to the run |
Choosing the right tool
Section titled “Choosing the right tool”| Use case | Best tool |
|---|---|
| Check one answer’s latency or raw events | Run Inspector |
| Investigate a bad session across multiple turns | Trace Viewer |
| Review feedback patterns in a session | Trace Viewer |
| Confirm the exact event sequence for one run | Run Inspector |
Common debugging workflow
Section titled “Common debugging workflow”- Reproduce the issue in Eric.
- Open Run Inspector on the suspicious answer.
- If the issue spans multiple turns, open Trace Viewer for the full session.
- Review stage-by-stage findings, failed tool calls, slow latencies, and feedback.
Access notes
Section titled “Access notes”- Non-admins can use Eric, but they cannot open these debugging tools.
- If a non-admin reaches the trace route directly, the app redirects them back to Eric chat.
- The trace sidebar includes a shortcut back to the original conversation.