👋 oh-my-hi (Oh My Harness Insights)

Oh, so that's what Claude's been doing! — A visual dashboard for your Claude Code harness.
Parses your entire Claude Code configuration and usage data, stores results in a local SQLite database, and serves an interactive dashboard via a local HTTP server.
What it shows
- Harness overview — skills, agents, plugins, hooks, memory, MCP servers, rules, principles, commands, teams, plans
- Context budget — estimated token distribution between visible and invisible contexts (startup, tools, user messages)
- Token analytics — usage by model, daily trends, cache efficiency, prompt statistics, response latency
- Token Breakdown — per-item token attribution by context type (skill / agent / MCP / built-in tool). Shows startup context cost estimate (CLAUDE.md, skill descriptions, principles, MCP tool listings) multiplied by session count, plus a Top 5 per type and an expandable drill-down by type
- Cache TTL Impact — detects cost waste from short cache TTL. Shows best/worst 7-day rolling efficiency, estimated waste cost, and a daily hit-rate trend chart with reference lines
- Month-end cost projection — trailing 7-day average extrapolated to month end, compared against your monthly budget
- Skill & agent efficiency — per-item call count, avg tokens/call, total cost, and category cost share. Sidebar marks the top 3 cost contributors with a 🔥 badge so optimization targets are obvious
- Context Window Explorer — replay any past session turn-by-turn to see exactly how the context window filled up
- Activity heatmaps — daily usage patterns across skills, agents, and commands
- Task categories — auto-classified token usage by work type (code editing, docs, planning, etc.)
- Multi-workspace — switch between global and per-project scopes
Token Breakdown
Breaks down token usage by context type and individual item. Shows which skills, agents, MCP servers, and built-in tools are consuming the most tokens — and how much of that cost comes from startup context that loads on every session.
Startup context cost estimates the cumulative token cost of items that load automatically before every session (CLAUDE.md, skill descriptions, principles, MCP tool listings). Multiplied by session count for the selected period, it gives you a concrete number to act on — trim a large CLAUDE.md or remove unused skills to reduce your baseline cost per session.
Cache TTL Impact
Tracks how much the cache TTL regression (5 min vs 1 hr) may be costing you. Compares 7-day rolling cache hit rates to estimate excess re-creation cost — drops in the trend chart indicate periods when caches expired before being reused.
Context Window Explorer
Pick a real session from your Claude Code history and replay it turn-by-turn. The explorer breaks down every API turn into its contribution to the context window — system prompt, CLAUDE.md, memory, skill descriptions, MCP tools, user prompts, model responses, tool calls — so you can see exactly where your tokens went and when /compact kicked in.
You can also view a guided example session to walk through the mechanics before loading your own:
Installation
From the Command Line
claude plugin marketplace add netil/oh-my-hi
claude plugin install oh-my-hi
Claude Code (in-session)
/plugin marketplace add netil/oh-my-hi
/plugin install oh-my-hi@oh-my-hi
Usage
Run in Claude Code:
/omh
This will parse your harness data, build the dashboard, and open it in your browser.
Parameters
| Command | Description |
|---|
/omh | Full build — parse data, build web-ui, open in browser |
/omh --data-only | Lightweight data collection (skip dashboard build) |
/omh --enable-auto | Auto-rebuild on session end (registers Stop hook) |
/omh --disable-auto | Disable auto-rebuild |
/omh --update | Check and install latest version |
/omh --status | Check auto-rebuild status |
/omh <path> | Build with specific project paths only |
Auto-refresh
Enable automatic data refresh so the dashboard stays up to date:
/omh --enable-auto