Claude Inspector

Claude Code Prompt Mechanism Visualizer — Electron desktop app

LLM Mart
18 views 104 listing impressions

See what Claude Code actually sends to the API.

A local MITM proxy that intercepts Claude Code CLI traffic in real-time,
lets you inspect every JSON payload, and analyzes session flows with AI.

Install · Usage · AI Analysis · What You'll Learn

License: MIT GitHub release macOS

English | 한국어


Proxy — Anatomy view

Proxy — Request view with cost breakdown

Proxy — AI Analysis view


Install

Homebrew (Recommended)

brew install --cask kangraemin/tap/claude-inspector && sleep 2 && open -a "Claude Inspector"

Direct Download

Download the .dmg from the Releases page.

Mac (Apple Silicon) Mac (Intel)
Claude-Inspector-arm64.dmg Claude-Inspector-x64.dmg

Upgrade / Uninstall

# Upgrade
brew update && brew upgrade --cask claude-inspector && sleep 2 && open -a "Claude Inspector"

# Uninstall
brew uninstall --cask claude-inspector

Proxy Mode

Intercept real Claude Code CLI traffic via a local MITM proxy.

Claude Code CLI  →  Inspector (localhost:9090)  →  api.anthropic.com

1. Click Start Proxy in the app
2. Run Claude Code through the proxy:

ANTHROPIC_BASE_URL=http://localhost:9090 claude

3. Every API request/response is captured in real-time.

4 Tabs

Tab What it shows
AI Analysis AI-powered session analysis — flow summary, Mermaid diagram, inline chat
Request Full JSON request body, collapsible tree, token/cost breakdown
Response Full JSON response with tool_use results
Anatomy Detected mechanisms (CLAUDE.md, Skills, MCP, Sub-agents) as colored chips

AI Analysis

Select captured requests and let Claude (Sonnet) analyze the full session flow.

What It Produces

  • Step-by-step session summary — what happened, in what order, with mechanism explanations
  • MCP dynamic loading chain — how ToolSearch fetches schemas, how deferred tools become callable
  • Skill loading flow — how slash commands trigger <command-message> → Skill tool_use
  • Sub-agent patterns — which requests are main vs sub-agent, and how they relate
  • Mermaid flowchart — visual diagram of the internal mechanism flow
  • Clickable references — each step links to the actual Request, scrolling to the relevant tool_use

How to Use

  1. Capture some requests via the proxy
  2. Click the AI Analysis tab
  3. Select requests to analyze (click to toggle, Shift+click for range)
  4. Click Analyze Session Flow
  5. Watch real-time streaming as Claude processes the session
  6. Click any Request #N badge to jump to that request's tool_use in the JSON tree

Inline Chat

After analysis, ask Claude follow-up questions about the session. The chat understands the full analysis context.

Session Detection

Requests are automatically grouped by session using message content fingerprinting. Different sessions (main conversation, sub-agents, stop hooks) get different colored borders in the sidebar.


What You'll Learn

From the project's README.

Comments (0)

Sign in to join the conversation.

No comments yet.

Related tools