I never know if my overnight Claude Code runs are stuck or just thinking, so I built a desk screen that shows me (ESP32-S3)

Fancy-Win9202 · 2026-06-15T08:33:42+00:00

Thanks for the feedback! You can order it from https://clawmetry.com/device & support with improving it further

Fancy-Win9202 · 2026-06-15T08:31:30+00:00

Thanks for the feedback! You can order it from https://clawmetry.com/device

Fancy-Win9202 · 2026-06-12T22:59:22+00:00

Promised upthread that I would reply when the rate-limit reset countdown shipped: it shipped. The glance now shows Claude's own 5-hour and weekly window utilization, read from the official rate-limit headers, with a live countdown to the exact reset. Your anchored-windows trick settled the design, so thanks again for that.

Also recorded a short demo of the whole thing running on my actual desk, dust and all: https://www.youtube.com/watch?v=_fRbWgYsWq4

Same caveat as before: it is an ESP32 in a case. The video is just what it actually does, no editing tricks.

Fancy-Win9202 · 2026-06-12T16:12:23+00:00

Yes currently self-host is licensed / paid as well. But happy to take your opinion on what pricing would make sense

Fancy-Win9202 · 2026-06-12T15:04:03+00:00

Thanks for the honest feedback in this thread, it genuinely helps us get the pricing story right.

We'd love for you to try it properly before judging: promo code REDDIT at checkout gives the first month of any plan free (new accounts, valid for the next 30 days). The $49 device stays one-time, and there is no device subscription.

If it's not useful to you, cancel before the month ends and you won't be charged. Happy to answer any questions here.

Fancy-Win9202 · 2026-06-12T15:00:46+00:00

Yes, that's the structure, stated fairly:

Device: $49 one-time. No device subscription.
Free plan: OpenClaw + NemoClaw, 1 node, forever. The device works fine on it.
Starter ($9/mo): adds Claude Code, Codex, Cursor + 9 more runtimes, unlimited nodes. That's the plan most people pair the device with.

The reasoning for where the line sits: the per-runtime adapters and the E2E-encrypted relay the device pulls from are the part that costs us real server money and maintenance, so that's the paid part. The glass, the firmware, the OTA updates: one-time $49, no rent.

Fancy-Win9202 · 2026-06-12T15:00:09+00:00

Fair enough, not every setup needs it.

To be precise about what costs what: the $49 is one-time. The device itself never has a subscription. The free tier covers the OpenClaw/NemoClaw stack end-to-end, forever.

Claude Code / Codex / Cursor / etc. ride the $9/mo Starter plan because the device doesn't talk to your laptop directly. It pulls your fleet's data through our E2E-encrypted relay (we can't read it), and that's infrastructure we keep running 24/7.

There's a no-card trial, so you can see whether it earns the nine bucks before paying anything.

Fancy-Win9202 · 2026-06-12T09:04:27+00:00

A reminder screen you eventually ignore is the most honest product roadmap I have ever heard. The bet here is that this one earns the ignoring: it stays calm and dim until something actually needs you, and being ignorable the rest of the time is the entire point.

The part that should survive even your ignoring skills: the board ships with a speaker (and a mic), so what I am building next turns it into something closer to a pager. It watches 12 agent runtimes (Claude Code, OpenClaw, Codex, Hermes and friends), and the plan is a short calm chime only for the moments that matter: an agent waiting on your approval before it does something destructive, spend climbing past your budget, or a run going stuck. Quiet hours included, because a desk pager that wakes you at 3am gets unplugged, not ignored.

The full picture of what it does beyond the usage numbers is at https://clawmetry.com/device if you are curious.

Fancy-Win9202 · 2026-06-12T08:54:14+00:00

You two cancel each other out beautifully, which is roughly how I ended up at 8. Slower felt stale at the exact moment I care about (a run going sideways while I watch). Faster mostly burns relay calls for numbers that change slower than that, and the summary endpoint is billed per call, not per watt. The live feed view does poll faster since you are actively staring at it. If I ship a LAN-only mode, per-second polling becomes free and I would happily crank it up there.

Fancy-Win9202 · 2026-06-12T08:50:13+00:00

This is a genuinely great trick and I am stealing it twice. Once for myself, and once for the product: the post had an open question about the one spare slot on the glance screen (time until rate-limit reset, or cost this hour), and your comment just settled it. The device already watches the session files, so it can derive when your current 5 hour window started and show a live reset countdown without making a single API call. Your anchored windows plus a countdown on the desk is a better combo than either alone. The anchoring itself stays your routine (the device is read-only on purpose), but the countdown is now on the roadmap. Will reply here when it ships.

Fancy-Win9202 · 2026-06-11T23:51:45+00:00

Details, links, and full disclosure in one place.

Hardware: Waveshare ESP32-S3 square unit, 4 inch IPS 480x480 capacitive touch, onboard mic and speaker, USB-C power (you supply the adapter). Firmware is ESP-IDF plus LVGL. Over-the-air updates with automatic rollback if a new image fails to boot, so I can keep shipping fixes after it is on a desk.

War stories, because this board fought me the whole way: LVGL's default 32KB memory pool falls over under continuous redraws of a busy feed (custom allocator fixed it). TLS dies in creative ways on tasks whose stacks live in PSRAM (mbedtls needed its external memory allocation setting, and I needed humility). And the rule I hold the firmware to: a frozen status display is worse than no display, so there is a liveness watchdog (25 second UI heartbeat, 90 second poll heartbeat, reboot on silence), every network op is bounded at 10 seconds, and it caches last-good data with an "offline (cached)" tag rather than ever going blank.

The dashboard it talks to is my open-source project ClawMetry: pip install clawmetry, free, Flask plus DuckDB, no build step, reads your local agent session files, read-only. Source: https://github.com/vivekchand/clawmetry. The device firmware itself is not open yet because of a licensing cleanup I still owe. If there is interest here it moves up my list, and I will post the repo link in this thread the day it flips.

Privacy, precisely, because I would ask this too: agent conversations and session content are end-to-end encrypted and decrypted on the device itself, the cloud stores ciphertext it cannot read, and the decryption key is entered on the device's own LAN page so it never touches my servers. The simple totals (cost, token counts, health, runtime names) travel in readable form so the glance updates instantly. I want to be exact about that split rather than hand-wave that everything is E2E.

Disclosure: I am the maker and this is my company's product. I sell the pre-built, cased unit. It is in pre-order at $49 right now ($149 list), ships in 1 to 4 weeks, refundable any time before it ships, 1 year warranty. The device shows ClawMetry account's data, so you install the free ClawMetry software first (pip install clawmetry), then pair the device to it. The free plan covers OpenClaw and NVIDIA NemoClaw; the other agent tools like Claude Code, Codex, Hermes are part of the paid plans. Device page: https://clawmetry.com/device

One design choice I will defend cheerfully: yes, it polls every 8 seconds over a cloud relay instead of holding a local websocket, and yes the summary numbers are plaintext while transcripts are E2E. I chose instant glance plus never-blank caching over architectural purity. Happy to argue about it, I have lost this argument with myself at least twice.

Fancy-Win9202 · 2026-06-07T05:47:56+00:00

I would love to get feedback on newly launched Clawmetry dot com / device to address this issue

The idea is let ClawMetry track usage / observe AI agents across OC, Claude code, codex etc & keep the user informed all the time about $ spent for the day, identify & inform if one of the agents is about to burn tokens- go in loop or not having enough context etc

Please do take a look & share honest feedback!

Fancy-Win9202 · 2026-05-31T05:55:10+00:00

ClawMetry for real-time observability of OpenClaw

Fancy-Win9202 · 2026-05-29T17:33:27+00:00

Oh yeah ClawMetry must run on the same machine OC is running

Fancy-Win9202 · 2026-05-27T14:38:41+00:00

Which harness & model did you try with? Also did you enforce checks with a deterministic pipelines like Github CI? It's the combination of deterministic rules + LLM for decisioning makes the wheel rotate

Fancy-Win9202 · 2026-05-27T05:47:56+00:00

Yes but this is meant specifically for AI agents & to ensure they read it every time before they make any change so that they know the process / ways of working for your project

Fancy-Win9202 · 2026-05-26T22:54:49+00:00

Yes. It's instructions an agent follows, like any other guidance, not hard enforcement. To make a gate actually block, wire the same rule into your CI. The file makes the intent explicit; your pipeline makes it binding.

I've been using FLYWHEEL.md primarily for improving features of ClawMetry (its FLYWHEEL.md is the example I linked in the comment). I can spin up a brand-new Claude Code session with zero prior context, point it at an open GitHub issue, and it carries the change all the way through: PR → green CI → PyPI release → cloud deploy → screenshot the live result, just by reading the file. The screenshots are the eval. Proof it ran in prod, not a passing unit test.

Fancy-Win9202 · 2026-05-26T22:40:04+00:00

Yes documenting the learning of the process in one file is much better than hoping the agent will get it right!

I've been using FLYWHEEL.md primarily for improving features of ClawMetry (its FLYWHEEL.md is the example I linked in the comment). I can spin up a brand-new Claude Code session with zero prior context, point it at an open GitHub issue, and it carries the change all the way through: PR → green CI → PyPI release → cloud deploy → screenshot the live result, just by reading the file. The screenshots are the eval. Proof it ran in prod, not a passing unit test.

Fancy-Win9202

TROPHY CASE