ccboard
Launch and navigate the ccboard TUI/Web dashboard for Claude Code. Use when monitoring token usage, tracking costs, browsing sessions, or checking MCP server status across projects.
What this skill does
# ccboard - Claude Code Dashboard Comprehensive TUI/Web dashboard for monitoring and managing your Claude Code usage. ## Overview ccboard provides a unified interface to visualize and explore all your Claude Code data: - **Sessions**: Browse all conversations across your projects - **Statistics**: Real-time token usage, cache hit rates, activity trends - **MCP Servers**: Monitor and manage Model Context Protocol servers - **Costs**: Track spending with detailed token breakdown and pricing - **Configuration**: View cascading settings (Global > Project > Local) - **Hooks**: Explore pre/post execution hooks and automation - **Agents**: Manage custom agents, commands, and skills - **History**: Search across all messages with full-text search ## Installation ### Via Cargo (Recommended) ```bash # Using Claude Code command /ccboard-install # Or manually cargo install ccboard ``` ### Requirements - Rust 1.70+ and Cargo - Claude Code installed (reads from `~/.claude/`) ## Commands | Command | Description | Shortcut | |---------|-------------|----------| | `/dashboard` | Launch TUI dashboard | `ccboard` | | `/mcp-status` | Open MCP servers tab | Press `8` | | `/costs` | Open costs analysis | Press `6` | | `/sessions` | Browse sessions | Press `2` | | `/ccboard-web` | Launch web UI | `ccboard web` | | `/ccboard-install` | Install/update ccboard | - | ## Features ### 8 Interactive Tabs #### 1. Dashboard (Press `1`) - Token usage statistics - Session count - Messages sent - Cache hit ratio - MCP server count - 7-day activity sparkline - Top 5 models usage gauges #### 2. Sessions (Press `2`) - Dual-pane: Project tree + Session list - Metadata: timestamps, duration, tokens, models - Search: Filter by project, message, or model (press `/`) - File operations: `e` to edit JSONL, `o` to reveal in finder #### 3. Config (Press `3`) - 4-column cascading view: Global | Project | Local | Merged - Settings inheritance visualization - MCP servers configuration - Rules (CLAUDE.md) preview - Permissions, hooks, environment variables - Edit config with `e` key #### 4. Hooks (Press `4`) - Event-based hook browsing (PreToolUse, UserPromptSubmit) - Hook bash script preview - Match patterns and conditions - File path tracking for easy editing #### 5. Agents (Press `5`) - 3 sub-tabs: Agents (12) | / Commands (5) | ★ Skills (0) - Frontmatter metadata extraction - File preview and editing - Recursive directory scanning #### 6. Costs (Press `6`) - 3 views: Overview | By Model | Daily Trend - Token breakdown: input, output, cache read/write - Pricing: total estimated costs - Model distribution breakdown #### 7. History (Press `7`) - Full-text search across all sessions - Activity by hour histogram (24h) - 7-day sparkline - All messages searchable #### 8. MCP (Press `8`) **NEW** - Dual-pane: Server list (35%) | Details (65%) - Live status detection: ● Running, ○ Stopped, ? Unknown - Full server details: command, args, environment vars - Quick actions: `e` edit config, `o` reveal file, `r` refresh status ### Navigation **Global Keys**: - `1-8` : Jump to tab - `Tab` / `Shift+Tab` : Navigate tabs - `q` : Quit - `F5` : Refresh data **Vim-style**: - `h/j/k/l` : Navigate (left/down/up/right) - `←/→/↑/↓` : Arrow alternatives **Common Actions**: - `Enter` : View details / Focus pane - `e` : Edit file in $EDITOR - `o` : Reveal file in finder - `/` : Search (in Sessions/History tabs) - `Esc` : Close popup / Cancel ### Real-time Monitoring ccboard includes a file watcher that monitors `~/.claude/` for changes: - **Stats updates**: Live refresh when `stats-cache.json` changes - **Session updates**: New sessions appear automatically - **Config updates**: Settings changes reflected in UI - **500ms debounce**: Prevents excessive updates ### File Editing Press `e` on any item to open in your preferred editor: - Uses `$VISUAL` > `$EDITOR` > platform default (nano/notepad) - Supports: Sessions (JSONL), Config (JSON), Hooks (Shell), Agents (Markdown) - Terminal state preserved (alternate screen mode) - Cross-platform (macOS, Linux, Windows) ### MCP Server Management The MCP tab provides comprehensive server monitoring: **Status Detection** (Unix): - Checks running processes via `ps aux` - Extracts package name from command - Displays PID when running - Windows shows "Unknown" status **Server Details**: - Full command and arguments - Environment variables with values - Config file path (`~/.claude/claude_desktop_config.json`) - Quick edit/reveal actions **Navigation**: - `h/l` or `←/→` : Switch between list and details - `j/k` or `↑/↓` : Select server - `Enter` : Focus detail pane - `e` : Edit MCP config - `o` : Reveal config in finder - `r` : Refresh server status ## Usage Examples ### Daily Monitoring ```bash # Launch dashboard /dashboard # Check activity and costs # Press '1' for overview # Press '6' for costs breakdown # Press '7' for recent history ``` ### MCP Troubleshooting ```bash # Open MCP tab /mcp-status # Or: ccboard then press '8' # Check server status (● green = running) # Press 'e' to edit config if needed # Press 'r' to refresh status after changes ``` ### Session Analysis ```bash # Browse sessions /sessions # Press '/' to search # Filter by project: /my-project # Filter by model: /opus # Press 'e' on session to view full JSONL ``` ### Cost Tracking ```bash # View costs /costs # Press '1' for overview # Press '2' for breakdown by model # Press '3' for daily trend # Identify expensive sessions # Track cache efficiency (99.9% hit rate) ``` ## Web Interface Launch browser-based interface for remote monitoring: ```bash # Launch web UI /ccboard-web # Or with custom port ccboard web --port 8080 # Access at http://localhost:3333 ``` **Features**: - Same data as TUI (shared backend) - Server-Sent Events (SSE) for live updates - Responsive design (desktop/tablet/mobile) - Concurrent multi-user access **Run both simultaneously**: ```bash ccboard both --port 3333 ``` ## Architecture ccboard is a single Rust binary with dual frontends: ``` ccboard/ ├── ccboard-core/ # Parsers, models, data store, watcher ├── ccboard-tui/ # Ratatui frontend (8 tabs) └── ccboard-web/ # Axum + Leptos frontend ``` **Data Sources**: - `~/.claude/stats-cache.json` - Statistics - `~/.claude/claude_desktop_config.json` - MCP config - `~/.claude/projects/*/` - Session JSONL files - `~/.claude/settings.json` - Global settings - `.claude/settings.json` - Project settings - `.claude/settings.local.json` - Local overrides - `.claude/CLAUDE.md` - Rules and behavior ## Troubleshooting ### ccboard not found ```bash # Check installation which ccboard # Install if needed /ccboard-install ``` ### No data visible ```bash # Verify Claude Code is installed ls ~/.claude/ # Check stats file exists cat ~/.claude/stats-cache.json # Run with specific project ccboard --project ~/path/to/project ``` ### MCP status shows "Unknown" - Status detection requires Unix (macOS/Linux) - Windows shows "Unknown" by default - Check if server process is actually running: `ps aux | grep <server-name>` ### File watcher not working - Ensure `notify` crate supports your platform - Check file permissions on `~/.claude/` - Restart ccboard if file system events missed ## Advanced Usage ### Command-line Options ```bash ccboard --help # Show all options ccboard --claude-home PATH # Custom Claude directory ccboard --project PATH # Specific project ccboard stats # Print stats and exit ccboard web --port 8080 # Web UI on port 8080 ccboard both # TUI + Web simultaneously ``` ### Environment Variables ```bash # Editor preference export EDITOR=vim export VISUAL=code # Custom Claude home export CLAUDE_HOME=~/custom/.claude ``` ### Integration with Claude Code ccboard reads **read-only** from Claude Code directories: - Non-invasive monitoring - No modifications to Claude data - Safe to run concurrently with Claude Code - File
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.