Open-source Claude Code observability

Your agent run has a story. Make it visible.

ClaudeScope turns raw session traces into an interactive timeline, token and tool diagnostics, and portable reports—entirely on your machine.

Local-first MIT licensed Python 3.10–3.13
TimelineEvery turn and tool
TokensContext growth over time
FailuresErrors and incomplete calls
ReportsOffline and redacted
One session, fully inspectable

Stop guessing where the run went wrong

Move from the full trajectory to one exact event without searching raw JSONL.

localhost:7860
ClaudeScope dashboard showing a Claude Code timeline and event inspector
From trace to evidence

Answer the questions the final response cannot

Where did the time go?

A real-time Gantt view separates prompts, reasoning, responses, and each tool. Long waits and dense call clusters become obvious.

Trajectory timeline

Did context explode?

Track input, cache creation, cache reads, output, and cumulative output per message.

Token flow

Which tool hurts?

Compare calls, errors, total time, mean latency, and p95 across every tool.

Tool profile

Can I share the diagnosis?

Export a self-contained interactive HTML report. Use redacted mode to remove prompts, responses, local paths, tool inputs, and results.

Portable reports
Dashboard optional

Useful from the terminal, too

Resolve a file, latest, or any unique session-ID prefix.

01

Find

claudescope list --limit 10

Discover recent local sessions across all projects.

02

Diagnose

claudescope summary latest

Get activity, token, failure, and duration totals instantly.

03

Share

claudescope export latest --redact

Create an interactive structural report safe for review.

Privacy is part of observability

Your traces stay local by default

Claude Code traces can contain prompts, source code, credentials, paths, and tool output. ClaudeScope does not upload them. Public Gradio links and full reports are explicit actions.

Local processingNo hosted backend or telemetry pipeline.

Redacted exportShare shape and metrics without session content.

Failure-tolerantWarnings surface bad events without losing valid data.

Inspect the work, not only the answer

Make your next Claude Code session explain itself.