A prompt kit and a phased plan for building dashboards that update themselves: one for your business, another to see what your Claude Code does, how often it fails and what it would cost.
CC Dashboard is a kit for using Claude Dashboards, panels that save their queries and redo the math every time you open them. It is meant for small business owners and for people who use Claude Code every day. It brings ready-made prompts to build business dashboards (money, overdue items, leaks) and a plan to measure Claude Code itself (estimated cost, tools, failures). To use it, you need a paid Claude plan and, for the parts with a database, a free Supabase account.
An old-style dashboard was a photo taken once. A Claude Dashboard saves the queries and runs them again on your data every time it is opened.
Where the money is, what is overdue, where you lose revenue. It starts with one app and grows into a central database that combines several.
Sessions, tokens, cache, estimated cost, the tools and MCP servers that fail most, most-used skills and the health of the collector.
Each card shows its query and the time of the last update. The kit teaches you to read the query and to check a number at its source before acting.
The dashboard only shows what Claude can read. For the business, the data comes through connectors; for Claude Code, it comes from the telemetry it sends itself.
Model, tool, skill and MCP server names, token counts, estimated cost, duration, success or failure, error type and machine name.
Prompt and response text, full commands, file paths, tool inputs and outputs, error text and email. From the shell, only the program name is kept.
Claude Code sends every few seconds, the summary recalculates every 10 min, the dashboard reruns its queries when opened, and the other apps are only as fresh as the last copy.
The feature is in beta and counts toward your plan's usage.
Pro, Max, Team or Enterprise. On Enterprise, an administrator turns Dashboards on in the organization settings, under Artifacts.
Free to start (500 MB). A free project pauses after a week without use. Only needed for the phases with a central database and for the Claude Code dashboard.
Only for the observability dashboard. The variables work on Mac, Linux and Windows; test on your system before relying on it.
# where the configuration goes
~/.claude/settings.jsonThe prompts are in the repository's prompts/ folder (in Portuguese). Copy one, replace what is in brackets and paste it into a Claude chat.
In Customize → Connectors, add the app where the answer lives. For read-only Supabase restricted to a single project, use a custom connector with this address:
https://mcp.supabase.com/mcp?project_ref=SEU_PROJECT_REF&read_only=true
"Which invoices are overdue and for how long?" works better than "a chart of invoices". Give the definitions and forbid changing data. Full template in prompts/01-dashboard-negocio.md (in Portuguese).
Build a Claude Dashboard using my connection to [app]. Question: [what changes what I do tomorrow]. Definitions: [balance = total − paid; empty paid = 0]. # Use saved queries, do not change data, ask if anything is missing.
Click the number and read the query: reference date, which records are included, whether it subtracts partial payments and where the range edges fall. Then compare one number with the source app (prompts/02-conferir-numero.md).
# the query shows how it was calculated — it does not guarantee it is right
Hours × invoices, subscriptions × charges, profit × cash in the bank: this requires copying the records into Supabase. Start with one question, two tables and a 90-day pilot (prompts/03-base-central.md).
I want to answer: what work was delivered and never invoiced? # Claude proposes the schema and the pilot and waits for your OK
Without a scheduled copy, the dashboard reads stale data. Ask for a daily or weekly task and a "Last updated" card (prompts/05-agendar-atualizacao.md).
Create a scheduled task that, every day at 6 am, recopies [app] into the schema [name].
With the Supabase connector in write mode (only for the setup), paste prompts/04-observabilidade-claude-code.md into a new chat. Claude asks for the project, the time zone and the machine name, lists the steps and waits for your OK.
# creates: cc_obs schema, cc-coletor function, summary every 10 min, daily cleanup
Paste the env block into ~/.claude/settings.json (template in config/claude-code-otel.example.json). Quit Claude Code completely and open it again: it only reads these variables at startup.
{ "env": {
"CLAUDE_CODE_ENABLE_TELEMETRY": "1",
"OTEL_EXPORTER_OTLP_PROTOCOL": "http/json",
"OTEL_EXPORTER_OTLP_LOGS_ENDPOINT": "https://<ref>.supabase.co/functions/v1/cc-coletor/v1/logs",
"OTEL_EXPORTER_OTLP_HEADERS": "x-cc-key=<key>",
… (full block in the example file)
} }
In a new session, send a simple prompt and tell Claude in the chat. It checks whether the collector received it and builds the five tabs. Give it a day of use before judging the charts.
claude --debug-file /tmp/cc.log # if nothing arrives, look for [3P telemetry] lines
What works well: a question that changes a decision, with a clear definition.
Open balance by range (not yet due, 1–30, 31–60, 61–90, 90+ days), by customer, with the reference date made explicit.
Logged hours that appear on no invoice line — requires a central database with both sources.
The month's accounting result against the money that actually came in and went out of the bank.
Calls, failure % and p50/p95 duration per tool and per MCP server over the last 7 days.
Cache tokens read versus created per day — a cache being rebuilt all the time shows up here.
Usage and estimated cost per skill and per subagent type, to know what is worth keeping.
The dashboard sends no alerts. To be notified when a number crosses a threshold, create a separate scheduled routine.
The value is what the usage would cost at API prices. On Pro or Max, your bill is the subscription.
Whoever receives the dashboard needs their own access to the same Supabase project; without it the cards stay empty.
Names of skills, repositories and MCP servers are stored. Think about who will see them.
The app chat and Cowork are not part of this observability dashboard.
500 MB on the free plan. Raw data is kept for 7 days, the summary is kept forever. Watch the size card.
The full plan is in PLANO.md (in Portuguese). Suggested order: the Claude Code dashboard first (one afternoon), then the business one.