I just used Claude to write a plug-in which changed the bottom of the CLI to say:<p><pre><code> ( ) Usage: 34% (resets in 2h 47m) Context: 56% [Opus 4.6]
auto mode on (shift+tab to cycle)
</code></pre>
That way if my usage starts shooting up, it's very easy to notice (and the color of "( )", which is a circle that I couldn't paste here, changes when it gets high, ensuring I don't miss it).<p>I coupled that with a hook that watches for usage spiking (basically when I've been talking too long or did something to add a ton of context, so suddenly every turn sends a ton of context back, using up a ton of usage).<p>Between the two I haven't hit usage caps in weeks.
I made an "amateur hour" error with Codex. Given Anthropic's recent reliability problems I thought I'd take a little time to try Codex with their $20/mo plan. So I downloaded it and gave it a whirl, not realizing that the default model was gpt-5.6-sol. Well after just an hour or two, I blew through my entire week's quota. Whoops! It would be cool if these harnesses could all graphically display your quota usage on the screen at all times.
I didn't know it was still possible to develop software after your ai quota runs out.
Pretty cool tool! Congrats!
Not sure if I'm missing something but this tells you where your tokens went, breakdown per day/tool.
So the "why" is still a question left for the user to answer. Can be something like "Because I was missing a good CLAUDE.md file so it had to explore the whole repo before doing any work" or anything else. Just my take.
The only time I've ever managed to burn through a quota that fast (on the cheap plan) was with an open-ended request to check a codebase for any defects or deficiencies. It dispatched five Fable subagents.
In 95% of cases it is because you had a large context for which the cache expired.
I’ve been using headroom to save on token usage and it’s pretty effective.
this kind of stats feature should be shipped by default with every harness imvho
You can't ask Claude if your quota ran out. You have to wait for the reset...
I care more about your experience. I'd read the blog post of the story behind this.
23 em-dashes in the span of a single README. I gotta hand it to Anthropic. They seriously managed to find a completely legal way to sell crack to crack addicts using other crack addicts as their unpaid sales force.
How on Earth does one use 1.1B tokens in a week?
[flagged]
[flagged]
[flagged]
Can you please not post AI-generated or AI-edited comments to HN? It's not allowed here - see <a href="https://news.ycombinator.com/newsguidelines.html#generated">https://news.ycombinator.com/newsguidelines.html#generated</a> and <a href="https://news.ycombinator.com/item?id=47340079">https://news.ycombinator.com/item?id=47340079</a>.<p>Of course, it's impossible to know for sure what was LLM processed or not, but some of your posts (like this one) have been getting classified that way.
[flagged]
At least it's not rewriting stuff in Rust.
Genuinely of the best reasons to build a tool tho? "I had a problem X, so I did nothing and kept complaining (without LLM)" would be pretty tiring to me personally
The problem is that anyone can type "I have this problem, plz fix" into Claude Code.<p>What unique insight or skill did they bring to the process? That's the interesting part. Otherwise it's just a small part of a huge sea of people's individual attempts to solve the same problems that everyone else is solving by themselves.
These kinds of trivial CLI vibes tools save an evening and some tokens. And sometimes it’s also not something you think of, or done with better or worse taste than your own. I think it’s nice
Indeed. Pre-LLM this kind of thing was a little interesting because you'd need to put a little thought and effort in whereas now it's a one-shot thing straight from an LLM. Don't be a slop proxy, as the saying goes.
<a href="https://news.ycombinator.com/newsguidelines.html">https://news.ycombinator.com/newsguidelines.html</a><p>Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
Hi Claude, please build a tool for analyzing Claude token usage and then deploy it to github.<p>If you're going to fully vibe code a repo, maybe we should get the build artifacts (i.e., the claude session).
<a href="https://news.ycombinator.com/newsguidelines.html">https://news.ycombinator.com/newsguidelines.html</a><p>Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.<p>> If you're going to fully vibe code a repo,<p>I'm not the OP.
<a href="https://news.ycombinator.com/newsguidelines.html">https://news.ycombinator.com/newsguidelines.html</a><p>Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.<p>> If <i>you</i>'re going to fully vibe code a repo,<p>> I'm not the OP.<p><a href="https://www.collinsdictionary.com/us/dictionary/english/you" rel="nofollow">https://www.collinsdictionary.com/us/dictionary/english/you</a><p>"In spoken English and informal written English, you is sometimes used to refer to people in general."<p>If you are going to repeatedly point out technicalities of a flagged post, please get your ducks in order first.
That is a very common title format for HN, and has been for a while. It wasn't just since AI has evolved—it has always been a load bearing part of HN<p>100% Human written slop