A Claude Code dashboard for your whole operation

A Claude Code dashboard is a single screen that answers “what is happening across everything I'm building?” When you run Claude Code in more than one repo, that state is scattered: a thread here, a diff there, an open pull request in a browser tab, a task you meant to hand off, a log you forgot to check. A dashboard pulls all of it into one place.

Most tools that show up for “Claude Code dashboard” are usage or cost trackers — they read your token spend and draw charts of it. That's useful, but it isn't operations. Aiola takes the other meaning of the word: a real cross-project operations dashboard that shows every project's active threads, recent changes, pending tasks, GitHub activity, app logs, analytics, and feedback — plus the automations you've scheduled — in one local desktop window.

These are two different products that happen to share a name, so it's worth being clear about the split.

A usage or cost tracker answers a money question: how many tokens did you burn, on which model, and what did it cost? It sits next to your API or subscription and turns spend into a chart. If that's the only thing you want, a usage tracker is the right tool — and Aiola is honest about not being one.

An operations dashboard answers a work question: what is each project doing right now, what changed, and what still needs a decision? That's what Aiola is. It doesn't meter token spend; it shows you active threads, recent diffs, open tasks, GitHub issues and pull requests, and the health of the products you ship. The value isn't a running bill — it's never losing track of what an agent did across five repos.

The two can coexist. Nothing stops you from watching your subscription usage in whatever tool you like; Aiola simply doesn't try to be that tool. Because you bring your own Claude subscription and Aiola never marks up or resells compute, there's no billing layer for it to meter in the first place. What it optimizes for instead is situational awareness — the difference between staring at a cost curve and actually knowing which projects are moving, which are stuck, and where a decision is waiting on you.

The center of Aiola is a cross-project view — one place that rolls up every project you're running instead of one terminal per repo. From there you can see and open:

• Active threads and recent changes — which projects have work in flight, what the agents changed recently, and a jump straight into any thread to steer it.
• Pending tasks — the open items across projects on the per-project Tasks board, any of which can trigger a Claude Code agent and come back as a pull request.
• GitHub issues and pull requests — the GitHub surface brings issues and PRs next to the code so you review and merge without leaving the app.
• Analytics — Analytics is oriented to the products you ship: traffic, funnels, and revenue, plus AI-crawler and bot tracking (GPTBot, ClaudeBot and the rest) and a Google Search Console / Bing indexing panel with keywords. It's product analytics, not a token meter.
• App logs and feedback — application logs and user feedback live beside the code that produced them, so the operations layer isn't spread across five other tools.
• Scheduled automations — recurring agent jobs (triage, checks, summaries) that keep working on your machine on a schedule, and show up in the same dashboard.

Most Claude Code dashboards only understand Claude. Aiola's dashboard is provider-agnostic: it orchestrates Claude Code, Codex, Cursor, Grok CLI, and OpenCode from one app, on your own subscriptions. Every surface — the cross-project view, threads, tasks, GitHub, logs, analytics — works the same regardless of which agent did the work, and you can pick the provider per thread. That means one operations picture for your whole portfolio, even when different projects lean on different agents.

That cross-vendor reach is what separates a dashboard from a single-tool viewer. Teams rarely standardize on exactly one agent — one repo is deep in Claude Code, another has a Codex habit, a third leans on Cursor — and a dashboard that only reads one of them shows you a fraction of reality. Aiola treats the agent as a detail of the thread, so the roll-up stays complete no matter how your projects are split.

Aiola runs the agents on your own machine, against your own repositories, using the subscription you already pay for. Your code is never uploaded to Aiola — it stays on your machine and goes only to the AI provider you already subscribe to — there's no cloud runner, no compute resale, and no API-key middleman. Threads, tasks, notes, and automations are stored locally. Optional analytics, logs, and feedback telemetry from shipped products is ingested through Aiola's cloud. Read more about how Aiola keeps your data yours.

Aiola runs on macOS 11+ (Apple Silicon and Intel) and Windows 10+ (64-bit). If you're on Windows that matters, because several Claude Code dashboards and GUIs are macOS-only. When you're ready, just download Aiola and point it at your projects.