Repository navigation
Weekly update, Nov 20: 0.20.5 keeps your other hook commands #14
SamStull9007
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Update, later on Nov 20, 2026: GitHub Release v0.20.5 is published. The first version of this note said it was not.
One improvement
Limitcast 0.20.5 is on npm and published as GitHub Release v0.20.5. Homebrew still installs 0.20.4.
npm view limitcast@0.20.5 version dist.shasum time --prefer-onlineon Nov 20, 2026 returned version0.20.5, dist.shasumccf3a9e23972372feb0d60b2abbe3342345dc060, published2026-11-20T02:29:15.042Z.npm pack limitcast@0.20.5produced a tarball with that same shasum. The pack is the release commit a03ac4b (chore(release): publish Limitcast 0.20.5), whose parent c9ceab3 is the fix. That commit ismain. CI passed on it. GitHub Release v0.20.5 is published at that commit, with the npm tarball attached (asset sha2561885857e635aac669ced3596cfe3c6ef66a70a39b16cab37c615173a0c080b0f). The Homebrew formula onorigin/mainstill downloads the v0.20.4 asset.What changed for someone who reinstalls:
preserve Grok hook file with commands not owned by Limitcastand does not write the other hosts' settings in that same run.limitcast doctorrequires Node.js 22 or later, the same floor asengines.node. Node 20 and 21 are outside the published package.Also on npm and GitHub since the Nov 17 announcement:
Upgrade the npm install with
npm install -g limitcast@0.20.5.brew upgradestays on 0.20.4 until the formula changes. Requires Node.js 22 or later. Restart Claude Code, Codex, and Grok after reinstalling hooks. Codex may ask you to approve the hooks again.One example
Synthetic settings, run Nov 20, 2026, with the published
limitcast@0.20.5tarball. The config, state, and home directories were empty temporary directories. The commandsecho originalandbefore-securitywere invented for the check. No project, account, or real hook file was used.Before:
{ "statusLine": { "type": "command", "command": "echo original" }, "hooks": { "PreToolUse": [ { "matcher": "Bash", "tag": "security", "hooks": [{ "type": "command", "command": "before-security" }] } ] } }limitcast install --guardprinted:The
ego-browserline is the default keep-list seed on an empty config. After install, thesecuritygroup still containedbefore-security, and Limitcast added its own guard beside it. The launcher path in the temporary directory is omitted here.limitcast uninstallprinted:The status line was
echo originalagain, andbefore-securitywas still in thesecuritygroup. Uninstall also left emptyUserPromptSubmitandSubagentStoparrays in this file.A second isolated run pointed Grok's dedicated hook file at a synthetic command,
foreign-check, and then ranlimitcast install --guard. The command exited withError: preserve Grok hook file with commands not owned by Limitcast. The Grok hook file and Grok config were unchanged, and no Claude settings file was created.One useful command
Run it after upgrading, or when a hook path might still point at an older install. It reports the Node version it is running on and whether the status line and guard are configured. It does not show that a hook ran inside Claude Code, Codex, or Grok. A passing line is a configuration check, not proof of live protection.
This is
doctorfrom the same published 0.20.5 tarball, in the same empty isolated config, before install. The Node version is the one that executed the tarball:✗ No Claude limit readings yetis there because the isolated config has no sessions. To pick up 0.20.5 afternpm install -g limitcast@0.20.5, runlimitcast installagain with the same flags you already use (--guard,--alerts,--optimize), then restart the coding tool. The install output confirms the files were written.One question
On Claude and Codex, 0.20.5 keeps your other commands through reinstall and uninstall. On Grok, a dedicated Limitcast hook file that already contains another command stops the install and is left unchanged. Should Grok keep that other command and continue, the way Claude and Codex do, or should it keep refusing the file?
If you answer, name the coding tool and say which behavior you want. Leave out prompts, logs, private names, and paths.
Follow shipped releases with Watch → Custom → Releases, and turn on email in your GitHub notification settings if you want release mail. npm moved ahead of this GitHub Release. The release is published now. Homebrew still installs 0.20.4.
All reactions