ZergBox CLI

Install with Node.js 22 or later:

npm install -g @zergai/zergbox
zergbox --help
zergbox --version

This package contains only the HTTP client, not the ZergBox server or desktop app. Existing credentials and workspace selection remain in ~/.config/zergbox-cli/state.json.

zergbox login --base-url https://your-zergbox.example --token-stdin
zergbox orgs
zergbox use my-workspace
zergbox ls

Use --state-file PATH for isolated automation. Never put tokens in shell history. Run zergbox help for file, sharing, trash, and version-history commands. Mutating commands operate on the selected server and workspace; review their targets first.

First-party code remains proprietary (UNLICENSED); npm publication does not change its license. Installed third-party dependencies retain their own licenses.

Updating the npm CLI

Run zergbox update or zergbox --update to install a newer npm release. zergbox update --check prints JSON without installing. The installed channel is preserved (dev, next, or latest); select a channel explicitly with update --channel dev|next|latest. Updates never downgrade.

Startup checks only notify on stderr when it is a terminal, never prompt or install, and are cached for one hour. CI, redirected stderr, and help/version requests skip checks. Set ZERGAI_NO_UPDATE_CHECK=1 to disable startup checks. Self-installation requires the matching macOS/Linux global npm prefix; local, linked, npx, or other package-manager installs must use their original manager. Existing releases need one ordinary npm upgrade before these commands exist.

See shared updater policy for installation safety, channel switching, and packaging details.