CLI / REPL¶

Raven's terminal operator client connects to a Raven server to manage engagements, run modules, inspect findings, and use the optional managed advisor. The server stores the same engagement data used by the web dashboard.

There are two binaries:

raven-server: the server (web dashboard + engine). You start this.
raven-cli: the operator REPL/CLI. Connects to a raven-server.

The current individual Docker image exposes the server command as raven-server. The operator REPL is a separate standalone download or apt package; it connects to that container's server.

Running the server¶

raven-server start -p 8080 --no-browser

Flag	Meaning
`-p, --port`	Port to bind (default 8080)
`--no-browser`	Don't auto-open a browser
`--host`	Interface to bind. Defaults to `127.0.0.1` (single-user). `--host 0.0.0.0` binds all interfaces. Only do this on a network you control; the single-user server has no auth, the loopback bind is the protection.

Optional pairing for managed AI¶

Pair only if you want Chamber Door's managed AI. Local engagement work does not require pairing. Native BYO analysis and manual prompt exchange are available in the web dashboard; they do not require Chamber Door credits.

raven-server auth login      # start device pairing (opens a URL + code)
raven-server auth status     # show current pairing
raven-server auth logout     # clear the saved token

In the current individual Docker image, use the same server command:

docker exec -it raven-pro raven-server auth login
docker exec -it raven-pro raven-server auth status
docker exec -it raven-pro raven-server auth logout

See Install Raven for the full flow. Older source-based images used the command raven; follow the guide for the image you are actually running.

The REPL¶

Launch the operator client. With nothing configured it connects to http://localhost:8080, which is raven-server's own default:

raven-cli                                  # REPL against http://localhost:8080
raven-cli -s https://your-server:8080      # point it at another server
raven-cli login https://your-server:8080   # log in first (team servers), then REPL

Inside, you drive engagements, run modules, inspect findings, and invoke the AI advisor (the same operations as the web dashboard). Type help in the REPL for the command list.

Discover commands

Both binaries are self-documenting:

raven-cli --help
raven-server --help

--help reflects the exact commands in your build, so trust it over these docs if they ever disagree.

AI from the terminal¶

Once paired, the REPL's AI commands retain the managed Chamber Door path. Saving a BYO provider in the web dashboard does not redirect them. Budget and usage are visible on the account dashboard.

Known identifiers are replaced on the Raven host, and recognized secret formats are redacted. The local mapping restores recognized response placeholders; redacted secrets are not restored. These checks reduce identifying content but do not detect every sensitive detail. See AI Analysis for the available paths and privacy limits.