DEV Community: notenki

We launched on Product Hunt today — here's what we shipped

notenki — Wed, 10 Jun 2026 06:45:24 +0000

We launched on Product Hunt today — here's what we shipped

Today I launched Claude Token Dashboard on Product Hunt.

👉 https://www.producthunt.com/posts/claude-token-dashboard

Here's what happened in the last two weeks.

Where it started

I had no visibility into what Claude Code was doing.

The cost was showing up in my billing. But which project?
Which session? What was the AI actually doing?

Turned out all the data was sitting on my machine the whole time —
~/.claude/projects/ — every session logged as JSONL.

So I built a dashboard to read it locally.

What shipped (v0.1.x → v0.2.2)

Token & Cost Visibility
Token usage and dollar cost by project.
Plan-aware: Pro/Max shows token volume, API shows dollar cost.

Today's Summary + Month Projection
Today's cost, tokens, actions, active projects — at a glance.
Plus: "based on this month's pace, you'll spend $XXX by month end."

Activity Log
Every file read, command executed, API call — risk-labeled, timestamped, live.
Captured via Claude Code hooks. Nothing leaves your machine.

Pre-execution Alerts
High-risk actions (rm, delete, format…) flagged BEFORE they run.
Red banner appears on dashboard. The beginning of "stop, not just watch."

Security Score
Your Claude Code environment scored out of 100.
Checks permissions, denied paths, strictMode, hooks.
Shareable. Per-project scoring included.

CLAUDE.md Editor
See the size of your CLAUDE.md. Click to view and edit it directly.
It's re-sent every turn — most people don't realize how much it costs.

Export
Activity logs as CSV or JSON. Full dashboard report as JSON.

Intelligence Tab
47 projects scored by cognitive load.
Stagnation days. Error rate. What deserves your attention next.

AI Assist Hints
Click any project → get an AI-generated suggestion on how to unblock it.
On-demand. Cached. Uses claude-sonnet-4-20250514 locally.

The reaction

Zhangcan Ding (@jason_dingzc) made an explainer video before launch:

"what your AI spent" is table stakes.

"what deserves your attention" is the real insight.

That framing is sharper than anything I wrote myself.

temp.md (@ship_temp_md) said:

turning token spend into what deserves attention next

is a much better loop than just another usage chart.

Both nailed it.

Where this is going

This started as a cost visibility tool.

It's becoming something bigger:
the audit layer AI agents have been missing.

Token Visibility → Agent Activity Log → Agent Security → Agent Control

The data was always on your machine.
I'm just making it visible — and eventually, actionable.

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard

GitHub: https://github.com/notenkitoclient-cpu/claude-token-dashboard

Would love to hear what you're seeing in your own data.

I added real-time activity logging and security scoring to my Claude Code dashboard

notenki — Fri, 05 Jun 2026 09:21:49 +0000

I added real-time activity logging and security scoring to my Claude Code dashboard

The problem with just seeing costs

Knowing how much you spent is useful.
But it's not enough.

The real question is: what is your AI actually doing?

Which files did it read?
Which commands did it run?
Is your environment even safe to run it in?

I couldn't answer any of those. So I built the answers in.

What's new in v0.1.17

Activity Log — see every action in real-time

Claude Code logs everything via hooks.
Every file read. Every command executed. Every API call.
Risk-labeled. Timestamped. Live.

Set it up once in ~/.claude/settings.json:

{
  "hooks": {
    "PostToolUse": [{
      "matcher": ".*",
      "hooks": [{
        "type": "command",
        "command": "curl -sf -X POST http://localhost:3000/api/actions -H 'Content-Type: application/json' --data-binary @- 2>/dev/null || true"
      }]
    }]
  }
}

Then open http://localhost:3000/activity.
Watch your AI's actions stream in real-time.

This is the audit layer AI agents have been missing.

Security Score — how safe is your Claude Code environment?

Scored out of 100. Checks 7 things:

Is Bash(sudo *) in your allow list? (-20)
Is ~/.ssh/** in your deny list? (-20)
Is Bash(curl *) unrestricted? (-15)
Are .env files protected? (-15)
Is strictMode enabled? (-10)
Is Bash(rm *) restricted? (-10)
Are hooks configured? (-5)

I scored 90/100. What's yours?

The point isn't to shame anyone.
It's to make the invisible visible —
so you can make informed decisions about what your AI is allowed to do.

Try it

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard

Open http://localhost:3000

GitHub: https://github.com/notenkitoclient-cpu/claude-token-dashboard

This started as a simple token counter.
It's becoming something bigger —
an observability layer for AI agents.

More coming.

I'm building the trust layer between humans and AI agents

notenki — Thu, 04 Jun 2026 06:36:12 +0000

The moment I realized something was wrong

I'd been using Claude Code every day for months.

Then one day I asked myself a simple question:
"How much have I actually spent?"

I had no idea.

Not approximately. Not roughly.
Zero visibility into what was happening.

That's when I understood the real problem.
It's not about cost. It's about trust.

AI agents are moving fast. Trust infrastructure isn't.

Claude Code can read files, write code, run commands,
and make decisions on your behalf.

But there's no dashboard. No audit trail.
No way to know what happened, why, or what it cost.

We're giving AI agents more and more autonomy
while building less and less visibility into their actions.

That's a problem that compounds.

What I'm building

I started with the most obvious gap:
token visibility for Claude Code users.

The data was always there — sitting in
~/.claude/projects/ as JSONL files.
Nobody told you it existed.

So I built a dashboard that reads it locally.
Nothing leaves your machine.

What I found in my own data:

$266 spent since March
One project eating 35% of my budget
95.9% cache read ratio — happening every turn, invisibly

But the dashboard is just the beginning

The real goal is bigger.

Think about how we built trust around cars:

License (who's allowed to drive)
Inspection (is it safe to operate)
Insurance (who's responsible when something goes wrong)

AI agents need the same stack.

That's what I'm working toward:

Identity — which AI did what
Permissions — what it's allowed to do
Audit trails — what actually happened
Cost accountability — who pays for what

The dashboard is the audit trail layer.
AgentPass is the identity and permission layer.

Together, they're the foundation of
what I'm calling the AI trust infrastructure.

Why this matters now

We're at the moment right before the problem becomes obvious.

Most companies still say "ChatGPT is convenient."
But AI agents are already making decisions,
sending emails, placing orders.

The question isn't whether AI will act autonomously.
It's whether humans will be able to understand,
verify, and trust those actions.

I'm building the infrastructure for that trust.

What's new in v6

Since this article was published, the dashboard has grown significantly
based on feedback from real Claude Code builders.

What it shows now:

Token usage by project
Cost display adapted to your plan (Pro/Max: token volume · API: dollar cost)
CLAUDE.md file sizes — re-sent every turn, most people don't realize this
Cost reduction insights — which projects to optimize first
Per-session drill-down — click any project to see individual sessions

Still local. Still private. Still free.

Try the dashboard

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard

GitHub: https://github.com/notenkitoclient-cpu/claude-token-dashboard

If you're building in this space —
identity, permissions, audit, cost accountability for AI agents —
I'd love to connect.

Update — v0.1.17: the audit layer is now real

Since writing this, the vision has gotten more concrete.

Two new features shipped:

Activity Log — Claude Code's actions now stream into the dashboard
in real-time. Every file read, every command executed, every API call.
Risk-labeled. Timestamped. Live.

This is the audit trail I was describing. It's working.

Security Score — your Claude Code environment scored out of 100.
Permissions, denied paths, strictMode, hooks.
See exactly where your exposure is.

The trust layer isn't a concept anymore.
It's running on your machine right now.

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard

Launching on Product Hunt June 9th.

I had no idea how many tokens I was burning in Claude Code — so I built a dashboard

notenki — Tue, 02 Jun 2026 22:45:17 +0000

The problem

I've been using Claude Code heavily for the past few months.
But I had absolutely no idea how many tokens I was actually burning — or where.

No visibility. No breakdown. Just vibes.

What I found

Turns out, all the data is sitting right there on your machine:

~/.claude/projects/

Every session is logged as a JSONL file with full token counts —
input, output, cache reads, cache creation.

Nobody told me this existed.

What I built

A simple Next.js dashboard that reads those files locally and shows:

Token usage per project
Daily usage chart
Cache read ratio

When I ran it on my own data, I discovered my cache read ratio was 95.8%.
I had no idea that was happening on every single turn.

My heaviest day: 340,000 tokens in a single day on one project.
I had no memory of it being that intense.

The insight

This isn't just about cost.

It's about visibility.

When you can't see what's happening, you can't improve it.
The data was always there — I just couldn't see it.

Try it yourself

Install and run:

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard

Open http://localhost:3000 — your Claude Code token data loads automatically.

Or clone it: https://github.com/notenkitoclient-cpu/claude-token-dashboard

Updates

v2 — Cost in dollars

Added estimated cost per project in USD (claude-sonnet-4-6 pricing).

My own numbers:

Total: $265 since March
Top project: $92.63 (35% of all spend)
Cache read ratio: 95.9%

A percentage is interesting. A dollar figure makes you act.

v3 — CLAUDE.md size visibility

Each CLAUDE.md is re-sent every turn.
Added a column showing file size per project.
Projects over 5KB get a warning.

Now you can see exactly which configs are silently taxing every prompt.

Install the latest version:

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard

Updates — v0.1.16 / v0.1.17

Activity Log

Claude Code now streams every action into the dashboard in real-time.
File reads, commands, API calls. Risk-labeled. Timestamped. Live.

Set up via Claude Code hooks — one config change, then open
http://localhost:3000/activity.

Security Score

Scores your Claude Code environment out of 100.
Checks permissions, denied paths, strictMode, hooks.

Open http://localhost:3000/security to see yours.

Install the latest:

npm install -g @notenkidev/claude-token-dashboard
claude-token-dashboard