@sys9/pulse9-cli

@sys9/pulse9-cli installs the pulse9 command.

The installed pulse9 executable is a bundled native binary. Node.js is not required at runtime.

Install

npm install -g @sys9/pulse9-cli
# or
bun add -g @sys9/pulse9-cli

Quickstart

All registry operations are scoped by a required space_id.

pulse9 set space demo_space
# Simple path: auto-claim, keep it alive, and release it on exit
pulse9 keepalive demo.worker
# In another shell, inspect entries while that process is still running
pulse9 list --limit 20

# Advanced usage: after the simple keepalive process exits, claim first if you want manual owner-token control
pulse9 claim demo.worker --description "Tokyo worker"
pulse9 keepalive demo.worker --owner-token <token>
# or refresh the lease yourself:
pulse9 heartbeat demo.worker --owner-token <token>
pulse9 offline demo.worker --owner-token <token>
pulse9 release demo.worker --owner-token <token>

You can also save the default space with:

pulse9 set space demo_space

Supported platforms

• Linux x64, arm64
• macOS x64, arm64

Release contract

• npm package version X.Y.Z bundles prebuilt pulse9 binaries for all supported platforms
• those binaries are staged under vendor/<goos>_<goarch>/pulse9
• npm pack / npm publish fail unless vendor/ contains one non-empty executable bundled binary file for every supported platform
• GitHub release tag vX.Y.Z-pulse9-cli publishes matching standalone binaries
• the tag release workflow requires the npm package to trust sys9-ai/bricks + .github/workflows/pulse9-release.yml as a trusted publisher before the tag is pushed
• if that package-side trust is repaired after a failed tag release, rerun the same vX.Y.Z-pulse9-cli workflow run; it reuses the existing GitHub release and still derives the npm publish version from the tag
• the installed executable name is pulse9