Troubleshooting

Logs & Diagnostics

Read startup, orchestration, and tool diagnostics when something breaks.

Overview

Most early failures are runtime and environment issues, not mysterious AI behavior. Start with what is missing, unreachable, or misconfigured.

Operator Note

Overseer works best when each layer stays explicit: the orchestrator routes, supervisors execute, tools return evidence, and traces show what actually happened.

Getting Started

Check whether the app launched, whether the database initialized, and whether the configured model runtime is reachable.

Configuration

Capture the exact error, the current model/runtime setup, and the last execution trace before changing multiple things at once.

Examples

triage-checklist.txt

1. Is Overseer running?
2. Is Ollama reachable at http://localhost:11434?
3. Did the workflow or conversation produce a trace?
4. Did a tool fail, time out, or return unverified output?

Next Steps

Continue with Logs & Diagnostics or head back to the documentation home.