fix: install kane-cli via npm tarball instead of bare runner binary#1
Merged
siddhant573 merged 1 commit intomainfrom Apr 16, 2026
Merged
fix: install kane-cli via npm tarball instead of bare runner binary#1siddhant573 merged 1 commit intomainfrom
siddhant573 merged 1 commit intomainfrom
Conversation
The previous formula downloaded kane-cli-darwin-arm64 / kane-cli-linux-x64
from GitHub Releases and installed them as 'kane-cli'. Those binaries
are actually v16-runner — the bare Python/Nuitka agent — not the
Node.js TUI users get from `npm install -g @testmuai/kane-cli`.
Result: brew users got a different (and broken-looking) command than
npm users — no interactive shell, different argument interface,
"v16-runner not found" errors when invoked normally.
Switch to the agent-browser pattern (Homebrew core formula for the
similar agent-browser tool):
- Download the @testmuai/kane-cli npm tarball from registry.npmjs.org
- depends_on "node"
- npm install + symlink bin/
- Platform-specific native binary auto-resolves via npm's
optionalDependencies (only the matching one installs)
This way `brew install LambdaTest/kane/kane-cli` and
`npm install -g @testmuai/kane-cli` produce identical installs.
Auto-update workflow rewritten to:
- Wait for the npm package to be visible (polls registry up to 2m)
- Compute the tarball sha256 directly from npmjs.com
- Update url / sha256 / version (single occurrences now)
- Skip commit if no changes (idempotent)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
5 tasks
This was referenced Apr 16, 2026
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Brew users currently get a different (and broken-looking) command than npm users. This PR switches the formula to install via the npm tarball so both paths produce the same install.
Background
The release on `LambdaTest/kane-cli` ships these binaries:
```
kane-cli-darwin-arm64 ← actually v16-runner, renamed
kane-cli-linux-x64 ← same
kane-cli-win-x64.exe ← same
```
Those are the bare Python/Nuitka agent (`v16-runner`). The actual user-facing CLI is the Node.js TUI shipped via `@testmuai/kane-cli` on npm — that wraps `v16-runner` as a subprocess.
The old formula installed the bare runner as `kane-cli`, so:
Approach
Adopt the agent-browser pattern — Homebrew's existing formula for a similar Node-based CLI tool.
```ruby
url "https://registry.npmjs.org/@testmuai/kane-cli/-/kane-cli-0.2.0.tgz"
sha256 "..."
depends_on "node"
def install
system "npm", "install", std_npm_args
bin.install_symlink libexec.glob("bin/")
end
```
`npm install` resolves `@testmuai/kane-cli`'s `optionalDependencies` and pulls only the matching platform binary package — same as the npm install path.
Auto-update workflow
Rewritten so it works against the new formula structure:
Test plan
🤖 Generated with Claude Code