Install the CLI

The CLI is served by your Shield360 platform, so machines download it from the same server they report to. Replace https://app.shield360.ai with your own address if you self-host.

curl -fsSL https://app.shield360.ai/api/cli/install.sh | SHIELD360_INSTALL_KEY=<key> sh

$env:SHIELD360_INSTALL_KEY = "<key>"
iwr -useb https://app.shield360.ai/api/cli/install.ps1 | iex

sh cli/scripts/install-local.sh

The install scripts also enrol the machine, start the collector and add coding-agent hooks. Get the install key from Visibility → Setup. For a binary without the enrolment, download it from Visibility → Setup or from /api/cli/download/<target>. See Deploy the collector for every target, MDM rollout and multi-user machines.

Install locations & PATH

Method	Install location	PATH handling
macOS / Linux script	~/.shield360/bin/shield360	Prints a PATH-add hint if the directory isn’t on $PATH
Windows script	%USERPROFILE%\.shield360\bin\shield360.exe	Updates user-scope PATH automatically - open a new terminal to pick it up
From source	~/.shield360/bin/shield360	Add it to $PATH if not already

Tip

The CLI binary must be on $PATH for the vendor plugin installs to work. The shield360 coding install command rewrites the shield360 token in each generated hook manifest to the absolute path of the running binary, which sidesteps the minimal PATH that GUI-launched agents (like Cursor) inherit - but the binary still has to be found at install time.

Script options

Environment variable	Purpose	Default
SHIELD360_INSTALL_KEY	Organisation install key used to enrol the machine (required)	none
SHIELD360_URL	Server to download from and enrol with	The server that served the script
SHIELD360_INSTALL_DIR	Target install directory	$HOME/.shield360/bin

Build from source

If you have the repository checked out and Go installed, build a local binary:

sh cli/scripts/install-local.sh

This builds with go build -trimpath -ldflags "-s -w" from cli/cmd/shield360 and installs to ~/.shield360/bin/shield360.

Verify the install

shield360 version
# shield360 v1.2.3 (abc1234)

shield360 doctor
# Prints resolved config, dials your OTLP endpoint, lists installed plugins

Uninstall

The shield360 binary is never touched by shield360 coding uninstall (which only removes vendor plugin manifests). Remove the binary the way you installed it:

shield360 collector uninstall           # stop background reporting
rm ~/.shield360/bin/shield360           # remove the binary

On Windows, run shield360 collector uninstall, then delete %USERPROFILE%\.shield360\bin\shield360.exe.

Next steps

Configuration

Point the CLI at your Shield360 collector

Wire your coding agents

Claude Code, Cursor, and Codex in under a minute