Skip to content

Install Bravos

Bravos takes two commands to install: one npm install, then bravos setup. The npm package is @bugb-technologies/bravos; the command is bravos.

  • Node.js 20 or newer, with npm, and git.
  • A Rust toolchain (cargo and rustc). Setup compiles cxg, the test engine, from crates.io. Without cargo, everything else still installs and cxg waits until you add Rust.
  • A git repository you want to secure, and a coding agent such as Claude Code, Codex or Cursor.
Terminal window
npm install -g @bugb-technologies/bravos
added 9 packages in 2s
1 package is looking for funding
run `npm fund` for details

Captured on 17 November 2026 with a scratch npm prefix, truncated before npm’s own update notice. Timing may differ.

Terminal window
bravos --version
1.18.0

If another executable named bravos comes earlier on your PATH, such as the old Python bravos, fix your PATH so it finds npm’s executable first.

In a terminal, from the root of your repository:

Terminal window
bravos setup

The guided setup asks one question at a time. It changes nothing until you choose Apply at the end. The first time on a machine it asks about the machine: terminal colours, an optional sign-in and the tools. Then it asks about the repository: which repository, which AI coding tools you use there, what Bravos should do (map threats only, also check every pull request, or everything including a scheduled run), how testing is handled, and your name to record with that choice.

The sign-in question, on a machine with no licence:

◆ No Bravos licence on this machine yet. Signing in is optional: the Free plan needs no account.
│ ❯ (•) Sign in now (recommended) — activate your licence, or start the free 30-day Team trial
│ ( ) Continue on the Free plan, no account needed — annotate and the authorized test loop (env, prove,
recheck) in each repository, no limit on how many; PR checks, CI, SAST, the code graph, schedules and
multi-repository workspaces need Team
│ ↑↓ move · enter choose · esc back · ctrl-c quit

Truncated to that one question, captured in a 110-column terminal. The rendered colours are not shown.

Choosing Free skips sign-in. The setup goes on to the repository’s questions, where pull-request checks and scheduled runs are marked as Team plan features. See how licensing works.

Running bravos setup again does only what is missing:

  • In another repository it skips what the machine already has and asks only that repository’s questions.
  • In a repository that already has Bravos it brings the machine and the repository up to date. bravos setup --change asks the repository’s questions again.

When setup finishes, open your agent in the repository and say anything. Bravos starts by drafting what the app is for. See Build your first threat model.

Setup installs two public tools: GuardLink 2.7.1 from npm, and cxg 1.9.2, which cargo builds from source. The guided setup runs this step when you choose Apply. For a script, the same step on its own is:

Terminal window
bravos setup --tools -y
guardlink: npm install --global guardlink@2.7.1
guardlink: installing the pinned GuardLink npm release…
cxg: cargo install --locked --force --version =1.9.2 cert-x-gen
cxg: building and installing the pinned CXG binary (cargo compiles it from source; this is the long step)…

Truncated before the two installed and verified on PATH at … lines, which name this machine’s paths, and a closing note about browser replay. On the machine used for this capture, with a cold cargo cache, the command took 393 seconds. Expect a few minutes.

cargo installs cxg into ~/.cargo/bin, or CARGO_HOME. If that folder is not on your PATH, setup says so and prints the line to add. Bravos still finds cxg there when a desktop app or agent starts without it.

Browser replay also needs cxg’s Python requirements and Playwright Chromium where the replay runs.

An agent or a script gets no questions. A plain bravos setup there only brings what is already installed up to date, and never installs Bravos into a repository:

bravos setup: no terminal here, so this is upkeep only: nothing is asked and nothing new is installed. In a terminal, bravos setup is the guided setup.

Truncated to the first line. To set a repository up without questions, pass flags instead:

Command What it does
bravos setup --yes a first setup of this repository with the defaults
bravos setup --tools -y this machine: GuardLink and cxg
bravos setup --agent claude,codex this repository: skills, hooks and MCP for the agents named
bravos setup --check what is installed and what setup would do; changes nothing

bravos setup --help lists the rest.

Ask your coding agent to follow www.bugb.io/skill.md. That page is Bugb’s setup instructions written for an agent. The agent checks Node, npm, git and cargo, installs the CLI, starts the tool install in the background, sets up the repository you have open for itself, and tells you which plan you are on. The page tells the agent not to sign you in, start a trial, commit or send test traffic unless you ask.

Terminal window
bravos setup --check

Before the tools were installed:

✘ analyzer absent — on the Team plan: bravos account activate
✘ codegraph absent — on the Team plan: bravos account activate
✘ guardlink absent — npm install --global guardlink@2.7.1
✘ cxg absent — cargo install --locked --force --version =1.9.2 cert-x-gen
✘ guardlink · in-session probe translation — tool missing
✘ cxg · plain scan of supplied JS probes with zero model calls — tool missing

After bravos setup --tools -y, the last two lines read:

✔ guardlink · in-session probe translation (2.7.1)
✔ cxg · plain scan of supplied JS probes with zero model calls (1.9.2)

Truncated to the capability checks; the ✔ guardlink and ✔ cxg lines above them name each executable’s path. The analyzer and code graph stay absent on Free. Setup upgrades a GuardLink or cxg older than these pins. It keeps a newer build, and reports a build whose version it cannot read.

Terminal window
bravos licence
Plan: Free (researcher) — the pre-PR gate, CI and nightly workflows, scheduled upkeep, multi-repository workspaces, campaigns, SAST, the code graph are on Team · bravos account activate starts a 30-day Team trial, no card
Licence: none
Unlocked: the research loop (context, annotate, templatize, env, prove, recheck, report, watch), in each repository on its own
On Team: the pre-PR gate, CI and nightly workflows, scheduled upkeep, multi-repository workspaces, campaigns, SAST, the code graph
Next: bravos account activate (30-day Team trial, no card) · https://account.bugb.io/pricing

Free needs no account and has no limit on how many repositories you use it in, each on its own. Team adds the pre-PR gate and autopilot, the CI and nightly workflows, scheduled upkeep, multi-repository workspaces, campaigns, SAST and the code graph.

Terminal window
bravos account activate

This opens a browser sign-in and writes this machine’s licence to ~/.bravos/licence.jwt. An account with no plan gets a 30-day Team trial, with no card. bravos account import FILE installs a licence downloaded from account.bugb.io instead.

With a licence, setup fetches the analyzer and the code graph. Both are signed bundles that come only through the account portal. Run bravos setup again, or fetch only those two:

Terminal window
bravos setup --codegraph --analyzer -y
codegraph 0.1.1: fetching the manifest
codegraph 0.1.1: fetching bravos-codegraph-0.1.1-aarch64-apple-darwin.tar.gz (15 MB)
codegraph 0.1.1: verified; unpacking

Truncated after the code graph’s signature check. The analyzer 0.6.2 follows the same steps, at 91 MB on this machine, then setup checks each staged binary. Both are staged under ~/.bravos, or $BRAVOS_HOME.

Build your first threat model sets Bravos up in a repository and starts the agent on it.