Limitcast 0.20.4: every large tool result gets a notice
Limitcast 0.20.4 is available on npm, GitHub and Homebrew. When the repository optimizer and the large-result notice are both installed, one PostToolUse process does both jobs, and that process now checks every tool result. A large write, edit, search, or directory listing is reported once per tool per session.
Limitcast forecasts usage limits and provides optional controls for Claude Code, Codex and Grok. All features remain free under the MIT License. Version 0.20.4 requires Node.js 22 or later on macOS or Linux. This post also covers 0.20.3, which shipped the same day and had no separate announcement.
One process for every result
A very large tool result is written once as new tokens and then re-read on later calls. Limitcast tells you about a result of about 20,000 tokens or more, once per tool per session, and suggests a narrower next call. The message goes to you. It is not added to the model's context.
Version 0.20.3 put that notice inside the optimizer's PostToolUse hook when both features are installed, so matched tools no longer start a second process. The first cut of that hook still followed the old matcher: Bash, Read, Grep, WebFetch, and MCP tools. A write, edit, search, or directory listing was recorded by the optimizer and then skipped by the notice.
Version 0.20.4 checks every result that process already has. The threshold is unchanged. Examples of the next-step line:
writeasks for a smaller part of the file.-
search_replaceand Edit ask for a smaller span. web_searchasks for a narrower query.list_dirasks for a smaller directory.search_toolasks for a tighter query.
Codex and Grok also record the size of each result they see, which feeds the fat-tool averages. Claude Code still takes those sizes from its transcripts. An install that has the alerts and not the optimizer still uses the hook matcher, so it does not start a process for every tool.
The optimizer keeps its own lock
Version 0.20.3 also split the optimizer's state lock from the
settings lock. An optimizer update no longer reads
config.json. A trim, or a broken settings file, cannot
stall or skip it. If the update does not change the optimizer
state, the file is left as it is.
That change does not make each tool call faster. The time you feel is still the process that starts for the hook. Combining the notice with that process removes a second start on the tools that used to run both.
What was verified
The release passed 320 tests and lint. GitHub's lint, security, and Ubuntu test jobs passed on the release commit. The macOS Node 24 job missed the 95% line-coverage floor at 94.99% and cancelled the other macOS jobs. The functional tests in that job had completed.
The tarball on npm matches the file attached to the GitHub release, and the Homebrew formula's checksum matches that file. These checks confirm the release was assembled correctly. They do not measure token savings, and this release makes no new claim about them.
Upgrade to 0.20.4
Use the package manager you installed Limitcast with. For npm:
node --version
npm install -g limitcast@0.20.4
For an existing Homebrew installation:
brew update
brew upgrade samstull9007/limitcast/limitcast
limitcast doctor --fix
Check the result with:
limitcast --version
limitcast doctor
doctor --fix points the hook launcher at the new
install. If you already installed the plugin, update it in each
host you use. For Claude Code:
claude plugin marketplace update limitcast
claude plugin update limitcast@limitcast --scope user
For Codex:
codex plugin marketplace upgrade limitcast
codex plugin add limitcast@limitcast
For Grok:
grok plugin update limitcast
Restart open Claude Code, Codex and Grok sessions to load the new binary and the refreshed plugin commands.
Read the 0.20.4 release notes or the previous 0.20.2 update.