Claudoscope

What is Claudoscope?

Claudoscope is a free, open-source macOS menu bar app for working with Claude Code sessions. It lets you browse and search your sessions and track associated costs while keeping session activity on your device.

The app is designed for users who want more visibility into what happens during Claude Code runs. It also claims to detect leaked API keys, tokens, and credentials present in sessions automatically, and it emphasizes “zero telemetry” and “100% local” operation.

Key Features

• Native macOS menu bar interface for viewing and managing Claude Code sessions, so session browsing stays accessible while you work.
• Browse and search across your Claude Code sessions, helping you locate specific conversations or runs.
• Cost tracking for Claude Code sessions, so you can review usage-related costs alongside the sessions themselves.
• Real-time tracking, intended to reflect changes as sessions run.
• “Zero telemetry” / local-only operation (“your sessions never leave your disk”), designed to minimize data sharing.
• Automatic detection of leaked API keys, tokens, and credentials in your sessions, intended to surface sensitive information embedded in session content.

How to Use Claudoscope

1. Install Claudoscope on macOS via Homebrew (brew tap cordwainersmith/claudoscope and brew install --cask claudoscope) or by downloading the provided .dmg.
2. Launch the app and use the menu bar entry to access your Claude Code sessions.
3. Browse and search your sessions to find relevant conversations.
4. Review cost analytics and any real-time updates shown by the app.
5. Pay attention to any alerts related to leaked API keys, tokens, or credentials found in session data.

Use Cases

• Reviewing a specific Claude Code run: Use browsing and search to find the session you want and review cost details for that work.
• Tracking spending over time: Use the app’s cost tracking (with real-time updates) to understand how costs accumulate as multiple sessions are executed.
• Debugging or auditing conversation history: Search through past sessions to locate a particular exchange or output and see the associated session context.
• Checking for accidental credential exposure: Rely on automatic detection to identify API keys, tokens, or credentials that appear in session content.
• Managing sessions while working: Keep the app in the macOS menu bar to quickly view, analyze, and monitor sessions without switching away from your current workflow.

FAQ

• Is Claudoscope a local-only app? Yes. The site states it is “100% local” and emphasizes “Zero telemetry,” including that sessions “never leave your disk.”

• What platforms does Claudoscope support? The page specifies it as a macOS menu bar app.

• Can Claudoscope find specific Claude Code sessions? Yes. It supports browsing and searching across Claude Code sessions.

• Does Claudoscope track costs? Yes. The page states it can “track costs across Claude Code sessions,” with real-time tracking.

• What does Claudoscope do about leaked credentials? The page states it can catch leaked API keys, tokens, and credentials in sessions automatically.

Alternatives

• Local developer logging and session history tools: Tools that focus on storing and searching your own application logs locally can provide similar “browse and search” capabilities, though they may not include Claude Code-specific cost tracking.
• Cost and usage dashboards for API tools: General analytics dashboards can track spend and usage, but they may require exporting data from your workflow and may not provide menu bar session browsing.
• Secure secret scanning tools: Dedicated secret scanning (for example, repository or file-based scanners) can help detect exposed keys and tokens, though they may not understand Claude Code sessions or provide session-level cost analytics.
• Chat and conversation management apps: Conversation managers can help organize prompts and outputs, but may not include the same cost tracking and Claude Code session detection described for Claudoscope.