Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • how in god's name did you blow your quota in 10 minutes?!?! Are you just queuing up a dozen agents at once to have a "team", putting them all on highest effort, and then letting them run hog wild without having you review each change it wants to make and accept it first?

    I must be using claude wrong....I never run out of quota.

    I'm genuinely curious what you are doing that would eat your quota that fast because that sounds legitimately insane.

  • 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.
  • Having a good statusline is key! I use https://github.com/lpsgverrilla/lps-statusline
  • 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.
  • In 95% of cases it is because you had a large context for which the cache expired.
    by sva_
  • I genuinely don't even understand how people run out of tokens with the basic subscription. I had Claude write an entire app that has completely replaced Adobe Illustrator for my specific usecases (mostly inking sketches, and embellishing generated SVGs). It does everything exactly the way I want and has much better ergonomics (blender hotkeys ftw) and the whole thing took me like 700k tokens over the course of a couple days.

    Do people just let Opus ultra extra max thinking run amok on their whole codebase with a single context? I don't even think I could even design sensible features faster, I'm the limiting factor here, the robot pretty much oneshots everything I ask for.

  • 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 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.

Explore Birbla archives