101–110 of 143 posts
This is pretty cool.. I like the idea, could I make a semi-snarky feature request and could we add the estimated power consumed to produce results for each session ?
Or just straight to CO2. Google said 1000 tokens emits 8.3g CO2. How many tokens used in a heavy vibe coding day? Average US daily per capita is like 40kg CO2
Can this be installed with uv? https://github.com/astral-sh/uv
Edit:
# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# Install the required CLI tool (Node.js)
npm install -g ccusage
# Clone and setup
git clone https://github.com/Maciek-roboblog/Claude-Code-Usage-Monitor.git
cd Claude-Code-Usage-Monitor
# Install Python deps with uv
uv add pytz
chmod +x ccusage_monitor.py
# Run it
uv run python ccusage_monitor.py --plan max20 --timezone America/New_YorkFor a reference point, it says my max session limit in the past was ~337,492 tokens and I have the Max20 plan and 99% use Opus. My total tokens used since I started using Claude Code on May 27th was 1,374,439,311 worth around $3397.34.
Do they have huge margins on API or are they just losing money? I use it everyday but I don't feel like I'm abusing it or anything
For a reference point, it says my max session limit in the past was ~337,492 tokens and I have the Max20 plan and 99% use Opus. My total tokens used since I started using Claude Code on May 27th was 1,374,439,311 worth around $3397.34.
I'm around ~2100 dollars equivalent on Max20 plan. Do they have huge margins on API or are they just losing money? I use it everyday but I don't feel like I'm abusing it or anything
Earlier quoted context omitted.
Or just straight to CO2. Google said 1000 tokens emits 8.3g CO2. How many tokens used in a heavy vibe coding day? Average US daily per capita is like 40kg CO2
By any chance do you remember the source for that? Googling "1000 tokens emits 8.3g CO2" only gets me this thread.
This article [0] mentions "8.3g CO2" but it's linked source [1] uses a different number - 4.32g. Perhaps revised after publication.
I ran the search again and got different numbers... I'm sure the real numbers will be changing quite a bit over time too.
[0] https://ditchcarbon.com/blog/llm-carbon-emissions
[1] https://smartly.ai/blog/the-carbon-footprint-of-chatgpt-how-...
This seems like a problem if for example, you hit 90% usage, pass the window, then burn through the remaining 10% quickly and have to wait a long time.
Earlier quoted context omitted.
pro is the $20/mo plan that they recently started allowing access to claude code.. but i’ve heard users hit the rate limit with a few queries.. so imo that sounds about right. the chat interface has its own limits separate from claude code.
Has to be wrong. I'm on that subscription as I wanted to reinforce my opinion that it's still shit for devs that actually have experience, like it was a few months ago. While my plan didn't pan out, cuz it was way too effective, I can confidently say that I'm going through 3-6k tokens per prompt on average, and usually get around 3 hours of usage before I'm hitting the rate limit. The limit is probably closer to 300k…
Earlier quoted context omitted.
pro is the $20/mo plan that they recently started allowing access to claude code.. but i’ve heard users hit the rate limit with a few queries.. so imo that sounds about right. the chat interface has its own limits separate from claude code.
Has to be wrong. I'm on that subscription as I wanted to reinforce my opinion that it's still shit for devs that actually have experience, like it was a few months ago. While my plan didn't pan out, cuz it was way too effective, I can confidently say that I'm going through 3-6k tokens per prompt on average, and usually get around 3 hours of usage before I'm hitting the rate limit. The limit is probably closer to 300k…
Transforming… (212s · 26.1k tokens · esc to interrupt)
I reset just under 2 hours ago, probably been going at this pace for the last hour or so.
I really like this idea as I find Claude's transparency frustrating. Claude code's killer features revolve around better tools to manage context and limits vs the desktop app (compact and the % remaining until auto compact), but it's not enough. If I can offer any advice, it's that the high use of emojis in a project readme (at least for me) looks so unprofessional and makes me worry that a project was vibe -coded in…
> looks so unprofessional and makes me worry that a project was vibe -coded in the sense that the AI was possibly not babysat to the extent I think they should. That's just me, though The irony of comments like this on software designed entirely for ai coding...