Show HN: Claude Code Usage Monitor – real-time tracker to dodge usage cut-offs

This code was written in pure vibe-coding style — mostly for fun. I've got about 10 years of experience in IT, and even I fully agree: a 1000-line main file like this one probably deserves to be locked away in a secure facility.

But hey — if it's stupid and it works, it ain't stupid.

I don’t understand the concern of this. Let’s say it says you’ve used 1.521kg of CO2 today. How is that actionable?

A single flight from JFK to LAX produces around 20,000kg of CO2. Using the 8.3g value means a flight is equivalent to 2.41 billion tokens.

[dead]

Let's start with npm and node_modules first - I think it is responsible for at least half of the global warming.

We all were low carbon developers once

Soon the AI companies will have different tiers of plan based on carbon output.

For $200 per month they’ll only use carbon-free power sources for your prompts. At $100 they’ll use nuclear, then $20 per month for coal, and then there will be a free tier where your prompts are powered by throwing baby seals into a furnace.

Wow, I had no idea Claude Code had this kind of verbose logging turned on by default. Looking around I also found a cool tool for converting these logs to HTML format for easy viewing: https://github.com/daaain/claude-code-log

It's definitely interesting. Probably, one could also see how much of the context is unnecessary to optimise usage. I wonder if one could also detect whether cache was used.

Is there anyway to ensure these logs are output in a current project folder? Would like to store a copy in git for reference

This tool is for plans with a fixed cost — like Pro Max x5 or x10 — not for API usage.

I used to think the same thing, and I still want a login/password alternative for me. But after seeing normies use online accounts and the trouble they have with password managers, I realized one of my friends had the most secure process: she would create extremely high-entropy passwords everywhere, but not remember them. Once she's logged out of her sessions after a couple of months, she uses the password forgotten link to generate another password, and so on. So her passwords are never stored anywhere, she's immune to many login stealing phishing attempts through genuine-looking fake websites as she can't enter the password, she doesn't have to deal with syncing the passwords between all her devices, and she doesn't have passwords on a post-it on her workstation. And she also doesn't get those annoying emails saying "your password is 6-months old, please change it or else!".

The email auth flow is a simplified and more efficient way to achieve the same outcome.

Another reason to ditch email-to-login: It decreases active user count because login is such a chore. I only use those websites if I absolutely have to and there are no alternatives.

Yeah, it's the reason I eventually tuned out of Slack too (obviously I don't use it day to day). I used it for some things, some community stuff, every now and then.

So when I open it up on a new machine or after months, you have to go through that magic link bs multiple times! For all your accounts/channels! I did that 2 or 3 times and then I just stopped using it.

I don't even remember what I signed up for over the years, I know some of it was nice (like an LoRa IOT channel, an "AWS professionals" channel, I set something up for the LoRaWan network in the previous city I lived in... All just tuned out because of the login bs.