I just used Claude to write a plug-in which changed the bottom of the CLI to say:
( ) Usage: 34% (resets in 2h 47m) Context: 56% [Opus 4.6]
auto mode on (shift+tab to cycle)
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).
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).
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.
Why not juat write the code. Its not that much faster to produce good code with AI. I spend nearly identical amoubts of time reviewing AI code as it would take to write. Im honestly not convinced there is all that much of a productivity boost, maybe 20% faster.
I was mostly joking, but to answer your question, the productivity boost entirely depends on your concern for code quality. Sometimes is it faster to just write the code than to try to explain in the prompt what to do. But if you don't care or don't need to understand what it is creating, you can get a ton of functionality fast.
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.
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.
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.
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.
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.
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).
Between the two I haven't hit usage caps in weeks.
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.
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.
Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something.
If you're going to fully vibe code a repo, maybe we should get the build artifacts (i.e., the claude session).
Be kind. Don't be snarky. Converse curiously; don't cross-examine. Edit out swipes.
> If you're going to fully vibe code a repo,
I'm not the OP.
Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.
> If you're going to fully vibe code a repo,
> I'm not the OP.
https://www.collinsdictionary.com/us/dictionary/english/you
"In spoken English and informal written English, you is sometimes used to refer to people in general."
If you are going to repeatedly point out technicalities of a flagged post, please get your ducks in order first.
100% Human written slop