cd /news/ai-tools/limitcast-0-14-pace-your-week-by-the… · home › topics › ai-tools › article
[ARTICLE · art-158974] src=dev.to ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

limitcast 0.14: pace your week by the day, and keep what trim must not touch

The developer behind limitcast released version 0.14 of the local-only CLI tool that forecasts when Claude Code, Codex and Grok usage limits will run out. The update adds a keep-list so the `trim --apply` command never disables MCP servers or hides skills a user marks as essential, a Pro daily-share budget that can hold new subagents once a day's allotment of a weekly limit is spent, and a status line naming which limit window will be hit first. The tool runs locally and never uses the user's Claude login.

by read2 min views2 publishedOct 27, 2026

limitcast 0.14 adds three things: a keep-list so trim never touches what you rely on, a daily share of your weekly limit that can now hold new subagents, and a status line that says which limit you will hit first.

0.14 makes limitcast's advice safer to apply and harder to ignore. trim can be told what to leave alone, the daily pace acts instead of only showing, and status names the window that runs out first.

limitcast trim --apply turns off MCP servers and hides skills you have not used. Some are rare but essential. Put them on the keep-list and no --apply will touch them, in Claude Code, Codex or Grok:

$ limitcast trim keep ego-browser
Kept by `trim --apply`: ego-browser

Spelling does not matter: ego-browser and ego_browser match. limitcast trim shows what it would keep, limitcast trim keep --remove <name> drops one, and limitcast trim keep on its own lists them. It is free.

The today column in limitcast status is your share of what is left of a weekly window, split evenly over the days until it resets. In 0.14 it acts (Pro). With notifications on, you get one message a day when you have used 80% of today's share:

limitcast: Claude 7d: 80% of today's share used, 1% left today.

Turn on limitcast budget today on and the subagent guard also holds new subagents once today's share is used up, until local midnight:

limitcast: today's share of your Claude 7d limit is used up (6% of 5%).
New subagents are held until midnight. Turn this off:
`limitcast budget today off`, or set LIMITCAST_ALLOW=1 to spawn anyway.

The (6% of 5%) reads as 6% used against a 5% share for today. The hold is off by default. A window already at 100% is left to the tool, and LIMITCAST_ALLOW=1 overrides it. Free installs record what Pro would have held, and limitcast results shows it.

When a window is on pace to run out, limitcast status now ends with one line naming the one that hits the wall first and where else there is room:

You'll hit Claude 5h first (16:40). Codex 5h has 78% left.

If you split work across Claude Code, Codex and Grok, that line tells you where to send the next task.

npm install -g limitcast
limitcast status

Local only, never uses your Claude login. Feature guide · Pro plans

Originally published at limitcast.dev. limitcast is a local-only command-line tool that forecasts when your Claude Code, Codex and Grok usage limits run out.

── more in #ai-tools 4 stories · sorted by recency
── more on @limitcast 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/limitcast-0-14-pace-…] indexed:0 read:2min 2026-10-27 · —