Skip to content

chore: run toolbox via npx instead of the bundled binary - #104

Open
wangauone wants to merge 2 commits into
mainfrom
chore/npx-toolbox
Open

chore: run toolbox via npx instead of the bundled binary#104
wangauone wants to merge 2 commits into
mainfrom
chore/npx-toolbox

Conversation

@wangauone

Copy link
Copy Markdown

Switches the MCP server from the bundled toolbox binary to npx -y @toolbox-sdk/server@1.8.0, which runs on every harness (no per-platform binary bundling).

  • gemini-extension.json: command → npx -y @toolbox-sdk/server@1.8.0 --prebuilt postgres --stdio
  • Remove the binary pipeline: package-and-upload-assets.yml, toolbox_version.txt, and the "Install toolbox binary" step in presubmit
  • renovate.json5: track the npm @toolbox-sdk/server pin in gemini-extension.json (grouped under renovate/toolbox) instead of the binary release
  • mirror-changelog.yml: retarget to the renovate/toolbox branch
  • README.md: update troubleshooting from binary-download errors to npx/Node

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As we are removing the toolbox packaging from this change, what's the behavior for a gemini-cli installation? (IIUC, Gemini CLI will attempt to do a direct clone? We would want to avoid the case where it still pulls from the legacy binary)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. Did a round of check. The Gemini CLI will install the source tarball (same as clone) in the new release if there is no platform specific binaries. So the legacy binary won't be downloaded, there will be new ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants