No Claude usage cap hit in weeks, thanks to a status line and one hook
They kept running into usage caps. Claude built a status line showing usage, reset time and context, plus a hook that catches spikes, like a long chat suddenly resending everything.
Done withClaudeSpotted· by HN user hungryhobbit· Oct 15, 2026
Result Spikes caught before they burn the quota
“Between the two I haven't hit usage caps in weeks.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
Used Claude to write a plug-in that changes the bottom of the CLI to show the usage percentage, time until reset, context used, model and mode, with an indicator that changes colour when usage gets high. Paired it with a hook that watches for usage spikes, such as a long conversation suddenly resending lots of context every turn.
How it went
Between the two, they haven’t hit a usage cap in weeks.
Try it yourself with Claude
Write a status line script for Claude Code that shows my current usage percentage, the time until my limit resets, how much of the context window is used and the model, and changes colour above [threshold] percent. Then write a hook that warns me when one turn uses far more than my recent average, so I can start a fresh session before burning my allowance.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.
Working on a Quake project, Claude decided on its own to build a test suite: demo playbacks with snapshots compared pixel by pixel, plus recorded demos whose screenshots it checked for each element.
After building a minimal proof assistant, the writer asked Claude how they knew the prover was actually sound. Claude checked, found five different ways it could prove false theorems, and fixed them.
Four years after shelving a homemade RSS reader and selling off its $500 domain, the writer built it this year with Codex and Claude. They use it daily, along with 30 other strangers who found it public.
Chasing a childhood itch for the exact 1996 After Dark Flying Toasters screensaver, the writer turned to Claude. It did a lot of good reverse-engineering work, but kept inventing details that needed pushback.