snare arm
One-command setup: initialize + plant canaries + test webhook. Defaults to precision mode (awsproc, ssh, k8s).—select mode
Interactive checklist. Arrow keys or j/k to move, Space to toggle, Enter to confirm.a select all, n select none, p reset to precision defaults.
Naming your canaries
The--label flag controls what your canary looks like on disk. It becomes the AWS profile name, SSH hostname, Kubernetes context name, and so on.
This is the most important thing you can tune. A compromised agent scanning for credentials will find yours and try to use it. The name determines whether it looks like a live credential worth trying.
Good names look like dormant but plausible infrastructure:
snare disarm
Remove all canaries. Surgical — only removes bytes Snare wrote.snare status
Show active canaries with last-seen timestamps.snare events
Fetch recent alert events from snare.sh.--summary shows ASN distribution, SDK/user-agent breakdown, likely-AI-agent count, and per-canary hit counts. Useful for triaging a canary fire — confirms whether activity looks like a cloud-hosted agent vs scanner noise.
snare test
Fire a test alert to verify your webhook works end-to-end.snare doctor
Validate your configuration and canary health.snare config
Show or update configuration.snare rotate
Rotate your device secret. Use if~/.snare/config.json was exposed.
snare plant
Plant individual canary types.snare teardown
Remove specific canaries.snare serve
Run a self-hosted callback server.SNARE_DASHBOARD_TOKEN env var is also accepted.