What is Runic?
Runic is a macOS menu bar app for developers who use multiple AI providers and want a local view of usage, costs, quotas, and reset times. It gathers information from provider APIs, local command-line logs, and browser sessions, then marks whether each value is reported, estimated, or otherwise derived. Usage history stays on the Mac, and the app does not collect telemetry or crash reports.
Runic Features:
Provider Snapshots: View enabled providers in one menu bar popover, with separate tabs for available usage, costs, quotas, model details, and reset windows.
Token And Cost Insights: Review token, cache, compaction, and cost breakdowns from supported Claude, Codex, and opencode logs and OpenTelemetry metrics.
Rolling Quota Gauges: Set local token, request, or spending limits over custom time windows and show the resulting gauges in the app and exports.
Local Usage History: Keep usage events in a Runic-owned JSONL history, with an initial log backfill and an explicit option to rebuild records.
Provenance-Aware Exports: Export scoped usage snapshots as CSV or JSON, retaining markers such as reported, estimated, declared, and heuristic.
Live Configuration: Change provider endpoints, extra log paths, and quota gauges in a watched configuration file without restarting the app.
CLI And MCP: Use the bundled command-line tool for scripts and diagnostics, or read-only MCP tools to check limits and refresh state.
Runic Benefits:
Clearer Confidence: Knowing which readings are measured and which are inferred makes it easier to decide what to trust when reviewing usage.
Fewer Account Switches: A combined view helps developers keep track of several AI subscriptions without checking each provider separately.
Earlier Limit Awareness: Seeing available quota and reset timing in one place can help developers plan work around provider limits.
Useful Cost Context: Token, cache, and cost breakdowns give teams more context for understanding where AI usage is coming from.
Local Data Control: Keeping routine usage data on the Mac reduces the need to send account details or history to another service.
Use Cases:
Daily Subscription Check: A developer using Claude, Codex, and other enabled providers can check current usage and upcoming resets before starting work.
Coding Budget Review: A developer can compare local token or spending gauges with usage records when planning a long coding session.
Historical Usage Audit: Someone reviewing past Claude, Codex, or opencode activity can backfill logs and inspect recorded token and cost events.
Scripted Usage Reports: A developer can use the CLI or CSV and JSON exports to bring Runic snapshots into scripts and diagnostics.
AI Limit Checks: An AI client can query Runic’s read-only MCP tools for available limits and the app’s refresh state.

