Appearance
Installation
sp binary
Release builds are produced by build.sh (build_sp_cli) and uploaded as:
text
gs://softprobe-published-files/sp/<version>/sp-{os}-{arch}Supported platforms (release): linux/amd64, linux/arm64, darwin/amd64, darwin/arm64, windows/amd64, windows/arm64.
Install on PATH
bash
# Example: Linux amd64
curl -fsSL -o sp "https://<your-distribution-host>/sp/1.0.0/sp-linux-amd64"
chmod +x sp
sudo mv sp /usr/local/bin/
sp versionExact download URLs depend on your organization's artifact hosting.
Verify
bash
sp version
sp health --json # requires sp-boot running (when implemented)Backend prerequisite
API commands need sp-boot reachable at the configured URL (default http://127.0.0.1:8090).
bash
curl -s http://127.0.0.1:8090/vi/healthConfiguration file
On first use (when sp config init is implemented):
bash
sp config init
# creates ~/.config/softprobe/config.yamlSee Configuration.
OpenCode / spcode
Agents hosted in OpenCode should invoke sp on PATH for backend operations (replacing sp_api). Source-code tools (sp_read, sp_grep) are not part of the public sp CLI — use internal/private tooling only. See sp_api migration.