Launching today
ilha
Your Claude Code and Codex limits, live in the notch
46 followers
Your Claude Code and Codex limits, live in the notch
46 followers
ilha is a native Mac app that lives in the notch (a small pill on other displays) and shows how much of your Claude Code, Codex and Grok Build limits you've used: the 5-hour and weekly windows, when they reset, and whether you're on pace to run out. If you pay for several accounts, it switches the CLI to one with room before the limit, without logging anything out. Insights prices each week at API rates, by project.
Very slick product! Easy to understand and use. I appreciate the placement, ux, and how it lists each platform.
opus vs sonnet, no clue which one burns through it faster lol
Opus generally burns through more of the allowance per turn. long conversations and higher effort use more too, so the model alone won’t tell the whole story. i’d start with Sonnet for routine edits and use Opus for the problems it can’t crack.
Can you switch between the different accounts if the usages are approaching their weekly limit?
yes. ilha watches both the weekly and 5 hour limits across your saved accounts, so you can switch to one with room. with auto switch enabled, Claude Code can move before the limit and running sessions follow it. Codex switches at the limit, and you need to restart open Codex sessions afterward. switching is part of Pro.
I have no clue how my codex limits work. they keep resetting 50% before they should. Could it be due to me using future quotas etc? any insight into this? Since you probably know more about limits than most? 😸 And love the design! Good job!
thanks André! when you say resetting early, does the usage percentage drop back to zero, or do you hit a limit with 50% left? and is that the 5 hour or weekly window? ilha reads the values OpenAI reports, so i’d want to check those before guessing at future quotas. glad you like the design!
The "on pace to run out" part is what I'd actually use. I hit the 5-hour window mid-task more often than I'd like to admit. Does the pace estimate learn from how I usually work during the week, or is it a straight line from the current window? Also nice that the cost view reads local logs and nothing leaves the Mac.
it’s a straight line from the average usage rate since the current window started. it doesn’t learn your weekly work schedule. i hold the forecast back for the first 10% of the window because there’s too little to go on. a long break followed by a heavy session can still throw it off, so it’s a rough estimate.