Limitcast 0.20.5: safer installs and reliable subagent receipts
Limitcast 0.20.5 is available on npm. This release fixes configuration changes that could remove another tool’s hook, makes interrupted installs recoverable, and prevents concurrent Grok completions from overwriting each other’s usage receipts.
All features remain free under the MIT License. Limitcast runs locally on macOS and Linux with Node.js 22 or later. The Claude Code, Codex and Grok plugins have also been updated to 0.20.5.
Keep another tool’s hooks intact
A hook group can contain more than one command. The installer previously treated a group containing any Limitcast command as a group it could replace or remove. That could also remove a command belonging to another tool.
Installation, reinstallation, notice folding and removal now edit the Limitcast commands within a shared group while preserving unrelated commands and group metadata. If Grok’s dedicated Limitcast hook file contains foreign commands, the installer refuses to replace it.
Recover interrupted installs
An invalid configuration in a later host could previously leave an earlier host partly installed. Version 0.20.5 stages the host settings and hook launcher before committing the changes. It uses atomic writes and the existing recovery journal so an interrupted operation can be reconciled.
Invalid settings stop the operation before earlier host files change. The recovery checks also refuse to overwrite configuration that has changed since the operation, preserving those edits for reconciliation.
Retain concurrent Grok receipts
When several Grok subagents finished together, two hook processes could read the same pending-receipt queue and then replace each other’s additions. An atomic file write kept the JSON readable, but did not prevent a lost update.
Queue updates and settlement now share a lock. Native subagent identity fields are retained, and repeated pending or already recorded receipts are ignored. The regression check preserves all 16 independent concurrent completions and records each once through concurrent settlement and replay.
Verify the release before publication
The earlier 0.20.4 release passed its functional tests but missed the
CI line-coverage floor. Version 0.20.5 adds meaningful checks for
configuration ownership, rollback, optimizer controls and the CLI
repair and removal paths. It also makes doctor require
Node 22+, matching the package requirement.
The 0.20.5 release commit passed 332 tests and all eight CI jobs. Its macOS Node 24 coverage was 95.39% of lines, above the unchanged 95% floor. The packed CLI and five installed adapter contracts passed, and the downloaded npm tarball matched the tested package.
A new publication preflight requires a clean checkout and successful, complete push CI for the exact release commit. Missing, pending or failed checks block publication. You can inspect the release’s CI results.
These are correctness and release checks. They do not establish real-world token savings or task-success improvements. The new measurement protocol describes a bounded comparison with the optimizer on and off; no live comparison results are claimed here.
Upgrade to 0.20.5
For an npm installation:
node --version
npm install -g limitcast@0.20.5
limitcast --version
limitcast doctor --fix
doctor --fix
refreshes the hook launcher for the installed features. Update the
plugin in each host you use. For Claude Code:
claude plugin marketplace update limitcast
claude plugin update limitcast@limitcast --scope user
For an existing Codex plugin installation:
codex plugin marketplace upgrade limitcast
For Grok:
grok plugin update limitcast
Restart open Claude Code, Codex and Grok sessions to load the refreshed plugin commands. Installing a plugin update does not prove that a session opened earlier has loaded it.
Read the 0.20.5 changelog, view the npm package, or catch up on the previous 0.20.4 update.