If you have used a terminal coding assistant, the shape will be familiar: you start it in a project and ask in plain language. Safeguard Code works that way, with one difference in what it checks. The product page says it considers reachability, policy, SBOM and license posture before it changes code.
What it is
Safeguard Code is described as a terminal-first AI coding agent that runs locally, as a native binary with no runtime, on Mac, Windows and Linux. The page says it can edit files, run builds and tests, and fix regressions it causes. It uses the Lion model on the device for routine work and Griffin in the cloud for harder reasoning. Each session is logged as an exportable trace of intent, tool calls, results and fallbacks.
The page assigns no maturity label to it, and it does not mention scheduling or a sandbox.
How to use it
Install on macOS or Linux:
curl -fsSL https://cli.safeguard.sh/install | bash
On Windows, use irm https://cli.safeguard.sh/install.ps1 | iex. To read the installer first, download it to install.sh and open it before running. Then check the install:
safeguard --version
If the version looks unfamiliar, an older copy is probably earlier on your PATH. Start the interactive agent in your project:
safeguard
Inside it, type /login to sign in, then ask for what you want. /scan . scans the current folder.
The runner docs add two more commands. safeguard agent "fix the critical CVEs in this repository" starts an interactive assistant session. safeguard exec "summarise the critical findings" runs a single turn with no prompts, meant for scripts and CI, and it defaults to strict permissions, where anything not pre-approved in the policy file is denied.
The --permission-mode option sets how much the assistant may do without asking, from supervised to autonomous. Start supervised.
Where your code goes
The page says source code does not leave the machine without a logged network action, and it lists an air-gapped mode in which Griffin escalations queue and fail closed. The local runner uploads only the SBOM and findings. Verify this against a test repository before you use it on a private one.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Which command runs one assistant turn with no prompts for CI?
safeguard exec, which defaults to strict permissions.
What does the version check warn about?
An unfamiliar version can mean an older copy is earlier on your PATH.
