Claude Performance Analyzer
See why Claude Code feels slow.
Model latency, tools, hooks, skills, subagents and MCP startup, live in your macOS menu bar.
Watch the demo in full quality (MP4)
A slow Claude Code turn can come from many places: the model, a long Bash call, a hook that runs on every prompt, an MCP server that takes seconds to connect. Claude Code already reports all of this through OpenTelemetry. Claude Performance Analyzer collects it on your Mac and shows you where the time goes.
What you get
- Latency in your menu bar. The model's response time over the last 15 minutes, always in view. It turns into a warning sign when hooks slow you down.
- Where each turn spends its time. Model, tools and hooks side by side, with the slowest items ranked.
- Details on click. Any tool, hook or subagent opens a card with p50, p95, failures, a split by repository and recent calls.
- A full dashboard in your browser: turn waterfall, recent prompts, skills, subagents, models, permission decisions, MCP connect times, errors and compaction.
- An MCP server for your agent. Claude can check what its own setup costs and help you trim it. See below.
- Your other machines too. Linux and macOS machines on your tailnet or your LAN can send their telemetry to this Mac.
- Private. Everything stays on your Mac, in a local database kept for 14 days.
Get started
Download the
.dmgfrom the latest release. It is signed and notarized, and runs on Apple silicon and Intel Macs with macOS 14 or later.Install. Open the
.dmg, drag ClaudeTelemetry to Applications and open it. It appears in your menu bar.Or skip steps 1 and 2 with Homebrew, then open ClaudeTelemetry from Applications:
brew install --cask kolezka/tap/claude-telemetry brew trust kolezka/tap # lets a plain `brew upgrade` update itConnect Claude Code. Click the menu bar item and choose Open Dashboard (or open http://127.0.0.1:4318), then click Add … missing settings. This adds the telemetry settings to
~/.claude/settings.json. Your existing values are kept, and a backup is written first.Start a new Claude Code session. Numbers show up within seconds. Sessions that were already running are not recorded.
The app keeps recording in the background, even while its panel is closed. You can turn that off in the app's Settings > General, or in System Settings > General > Login Items.
Prefer to edit the settings yourself?Add these to the env block of ~/.claude/settings.json:
CLAUDE_CODE_ENABLE_TELEMETRY=1
OTEL_LOGS_EXPORTER=otlp
OTEL_METRICS_EXPORTER=otlp
OTEL_EXPORTER_OTLP_PROTOCOL=http/json # http/protobuf works too; grpc does not
OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318
OTEL_LOGS_EXPORT_INTERVAL=1000 # how "real time" the live feed is
OTEL_LOG_TOOL_DETAILS=1 # real skill, MCP and subagent names
CLAUDE_CODE_ENHANCED_TELEMETRY_BETA=1 # optional: time to first token, turn spans
OTEL_TRACES_EXPORTER=otlp
The menu bar app

The label shows the model's p50 latency over the last 15 minutes. It changes to a warning triangle when hooks take more than 15% of turn time, or when one hook's p95 is above 2 seconds.
Click it to open the panel: headline numbers, a latency chart, where turn time goes, the slowest items, the biggest total time and a live feed. Switch between 15 minutes, 1 hour, 24 hours and 7 days, or between this Mac and a remote host.
Everything in the panel can be tuned or hidden in Settings. More on each section: docs/menu-bar-app.md.
Let your agent check its setup (MCP)
Hooks, plugins and memory tools add time and text to every prompt, and you rarely see how much. The performance-analyzer plugin gives Claude Code a read-only MCP server, so the agent can look at its own harness and tell you what to fix.
Ask it things like:
- "Which hooks slow down my prompts the most?"
- "How much text do my hooks add to every prompt, and which plugin adds it?"
- "How much of my context is Hindsight memory, and does it get used?"
Install it, then start a new session:
claude plugin marketplace add kolezka/marketplace
claude plugin install performance-analyzer@kolezka
It needs Bun on your PATH. Hook timing comes from the telemetry the app records, so install the app first. Without the app, the answers about injected text still work.
| Tool | What it answers |
|---|---|
harness_summary |
Start here: hook time, injected text and the Hindsight share in one answer |
hook_time |
Time per hook, with the plugin or settings file that owns it |
injected_context |
What hooks put into the model's context, and who put it there |
memory_cost |
How much Hindsight memory gets injected, and whether the agent reads it |
harness_query |
One read-only SQL query over the same data, for anything else |
The plugin also ships the harness-cost skill. It tells the agent when to reach for these tools, how to read the numbers and where each fix goes, so you can ask in plain words ("why is every prompt slow?").
The server only reads. It never changes your settings or hooks, and it covers sessions on this Mac. Parameters and where each number comes from: docs/mcp.md.
DeepSeek Harness
dsh/ is a DeepSeek Harness (DSH) adapter for the same plugin. It loads the harness-cost skill through the published claude-plugin-dsh package, pinned to 0.1.0 in dsh/package.json and dsh/bun.lock. The Claude Code install above does not change.
DSH does not install the adapter's dependencies for you. Install them first, from a release checkout (the release branch, which carries dist/):
cd /absolute/path/to/claude-performance-analyzer/dsh && bun install --frozen-lockfile
# or, from anywhere:
bun install --cwd /absolute/path/to/claude-performance-analyzer/dsh --frozen-lockfile
Then add it with dsh plugin add file:/absolute/path/to/claude-performance-analyzer/dsh. To see what it registers without touching a profile, run bun x claude-plugin-dsh@0.1.0 inspect /absolute/path/to/claude-performance-analyzer.
The harness MCP server is not mapped automatically. dsh/cordis.patch.yml carries an explicit dsh-mcp-client row for it that ships disabled, because the server reads Claude Code sessions and settings. To enable it, set PERFORMANCE_ANALYZER_ROOT to the release checkout and add - id: claude-compat-performance-analyzer-mcp with disabled: false to your profile.
To move to a newer runtime, change the exact version in dsh/package.json and run bun install in dsh/ to refresh dsh/bun.lock. Do not run the package's sync or scaffold commands here: in 0.1.0 they write a vendored runtime copy, and this adapter imports the package directly.
Your other machines
Claude Code on another Linux or macOS machine can send its telemetry to this Mac over Tailscale or your LAN. Nothing extra runs on the other machine.
- In the app, open Settings > Hosts and add a host.
- Pick which of this Mac's addresses it should send to (Tailscale or LAN), then copy the
envblock it shows. It is shown only once. - Paste it into
~/.claude/settings.jsonon the other machine and start a new Claude Code session there.
Pick the host in the panel or the dashboard to see its numbers. Security and limits: docs/remote-hosts.md.
Privacy
- The collector listens on
127.0.0.1only. It opens up only after you add a remote host, and then accepts telemetry only from Tailscale or private LAN addresses with a valid token. Over the LAN that traffic is not encrypted. - Data lives in
~/.claude-telemetry/telemetry.sqliteon your Mac and is deleted after 14 days. - Without remote hosts, nothing leaves your Mac.
Good to know
- Only sessions started after you connect Claude Code are recorded. There is no backfill.
- Telemetry times hooks per event and matcher (
PreToolUse:Bash), not per script. Per-script detail needs detailed beta tracing. The MCP server adds per-command times where Claude Code logs them. - Rules have no timing in telemetry. They only appear as
source: configpermission decisions. - "Where turn time goes" adds up durations, so parallel tool calls overlap.
Build from source
You need Bun and Xcode 26.
git clone https://github.com/kolezka/claude-performance-analyzer.git
cd claude-performance-analyzer
bun install
bun run start # collector and dashboard on http://127.0.0.1:4318
bun run app # build and open the menu bar app
How it fits together, the project layout and how releases work: docs/development.md.
License
MIT © 2026 Mariusz Rakus
packages/otlp/proto/ holds the OTLP .proto definitions from open-telemetry/opentelemetry-proto v1.11.1, Apache 2.0 (see packages/otlp/proto/LICENSE).
No comments yet. Be the first to write one.