View as markdown

# CLI Reference

The clawpatrol binary is the unified entry point for both the gateway server and the client tools. Same binary, different subcommands.

# Install

curl -fsSL https://clawpatrol.dev/install.sh | sh

Statically-linked Go binary, dropped in ~/.local/bin. macOS and Linux on amd64 + arm64. Set CLAWPATROL_FROM_SOURCE=1 to build from source instead (requires Go + gh auth login).

# Commands

# clawpatrol gateway

Run the gateway daemon against an HCL config. Start from gateway.example.hcl — see Getting Started for the operational fields you need to edit.

clawpatrol gateway <config.hcl>

By default the gateway is read-only-config: the dashboard can generate HCL from observed actions, but it will not edit the running file. Set dashboard_config_writes = true in gateway {} to let the dashboard append generated rules after validating the full candidate config and hot-reloading it. Git-managed deployments should leave it false and push edits through their normal review/deploy flow. See config-reference for the HCL grammar.

# clawpatrol join

Enroll the current device with a gateway. Prints a one-time code, opens the dashboard so an operator can confirm and assign a profile, persists the WireGuard conf, and installs the CA in your trust store. Falls back to the Tailscale path (see login below) when the gateway runs in Tailscale mode.

clawpatrol join <gateway-url> [flags]

# clawpatrol login

Tailscale-based onboarding alternative for fleets already on a tailnet. Joins the device to the tailnet, finds the gateway by its exit-node hostname, and installs the CA.

clawpatrol login [flags]

# clawpatrol run

Run a command with its traffic routed through the joined gateway.

clawpatrol run [--conf <path>] -- <command> [args...]

--conf points at the WG conf written by clawpatrol join; defaults to the standard location so you rarely need it. On Linux the wrapped command runs in an unprivileged user namespace with a private WG tunnel; on macOS the Network Extension does the capture.

clawpatrol run -- claude
clawpatrol run -- gh pr create
clawpatrol run -- psql 'host=db user=agent'

The agent sees a normal network — outbound flows just route through the gateway, which matches each request against the rules, injects the configured credential, and forwards.

# Root and sudo inside clawpatrol run (Linux)

clawpatrol run builds the network namespace one of two ways, depending on whether the invoking user has passwordless sudo:

• Passwordless sudo available (preferred). clawpatrol uses it to set up the net + mount namespace as real root, then drops back to your own user before exec'ing the command. Inside the wrapper you are your normal uid, root (uid 0) exists in the namespace, and sudo works — a command that needs to elevate can just call sudo as it would anywhere. The wrapped command can't tell it was launched this way: clean environment, normal uid, no leftover SUDO_* vars.

• No passwordless sudo (or CLAWPATROL_NO_SUDO=1). clawpatrol falls back to an unprivileged user namespace. As a consequence of how Linux user namespaces work, that namespace has no mapped root: your own uid is the only one mapped in, host root (uid 0) is not. So commands that need real root won't work — sudo fails with messages like:

  sudo: /etc/sudo.conf is owned by uid 65534, should be 0
  sudo: The "no new privileges" flag is set, which prevents sudo from running as root.

  The first is the namespace mapping root-owned files to "nobody" (65534); the second is the no_new_privileges flag clawpatrol sets to install its unprivileged seccomp filter. This isn't a deliberate restriction — it falls out of running unprivileged, and the host's own sudo is unaffected outside the wrapper.

Gaining root inside the wrapper doesn't bypass the gateway's purpose: real secrets never leave the gateway, so a process that steps around the tunnel only reaches the network with placeholder credentials that mean nothing upstream. The namespace makes the gateway the path of least resistance, not an escape-proof jail.

If you're on the unprivileged path and a command needs to act as root:

• Install the tooling on the host first, then launch — e.g. sudo apt-get install -y postgresql-client && clawpatrol run -- psql …. Many tools can also be unpacked into a local prefix (e.g. dpkg-deb -x) without root at all.
• Use --whole-machine (see clawpatrol join --whole-machine). It routes traffic at the host level instead of per-process, so the command runs in the normal host environment where sudo works — you run it directly, not through clawpatrol run.

# clawpatrol test

Replay recorded gateway actions against a candidate HCL policy and report verdict drift.

clawpatrol test <config.hcl> <fixture.json | fixture-dir>

See Testing for the fixture format and CI integration. Exit 0 = all match, 1 = drift, 2 = usage/config error.

# clawpatrol validate

Parse and compile a gateway HCL config, then exit. Use it in CI to catch typos before they hit production.

clawpatrol validate <config.hcl>

validate runs the same load path the daemon does, so any external plugin referenced from the file is spawned and its manifest is checked. Beyond the HCL pipeline it also runs a schema-only pass that exercises every plugin-declared facet’s CEL env and resolves every plugin endpoint’s Family against the facet registry — catches authoring bugs (typo’d Family, invalid identifier in a facet name, …) the operator’s HCL didn’t happen to exercise. The success line names what loaded:

ok: gateway.hcl — 7 endpoints across 3 profile(s)
  plugin "example" v0.1: 2 facet(s), 1 credential type(s), 1 tunnel type(s), 3 endpoint type(s)

# clawpatrol plugins

Manage external plugins — download GitHub-sourced plugins, pin them in clawpatrol.lock.hcl, and approve permission grants. The running gateway only ever loads the locked version and never downloads on its own; these are the explicit, reviewable steps.

clawpatrol plugins install <config.hcl> [name...]   # download + pin the locked version
clawpatrol plugins update  <config.hcl> [name...]   # re-pin to the newest matching release
clawpatrol plugins lock    <config.hcl> [name...]   # record every platform's binary hash
clawpatrol plugins info    <config.hcl> [name...]   # show required privileges (no download)
clawpatrol plugins approve <config.hcl> [name...]   # approve a pending permission escalation

info reads each GitHub plugin's signed static manifest — without downloading the binary — and prints its types and the network / egress / privileged grants it requests. approve records a plugin's requested grants in the lockfile after a manifest escalation held it closed (a new version that wants more than the lockfile recorded). Local (./path) sources skip the download but still pin a binary hash. See Plugins for the source / version syntax and the trust model.

# clawpatrol status

Report device install state — whether join/login ran, whether the CA is trusted, whether the WG conf or tailnet membership is healthy.

clawpatrol status

# clawpatrol uninstall

Tear down everything join / login put on this machine — stops the macOS Network Extension, brings down the WG interface, removes the CA from system trust, drops per-user state dirs, strips the shell-rc.

clawpatrol uninstall [-y] [--keep-ca] [--keep-conf]

# clawpatrol env

Print the shell exports clawpatrol injects when wrapping a command (SSL_CERT_FILE, credential-placeholder env vars). Source from your shell rc if you need them outside clawpatrol run.

eval "$(clawpatrol env)"

# clawpatrol version

Print the version. Also accepts -v and --version.

# Environment variables

Most configuration lives in gateway.hcl on the gateway side. A few device-side knobs:

# Data directories

Where state lives, by role:

Gateway host — the operator picks the location; nothing is hardcoded. A typical layout under /opt/clawpatrol/:

gateway.hcl              HCL config (operator-edited)
state/clawpatrol.db      SQLite — everything else

state_dir in the HCL points at the sqlite directory. The DB holds the CA cert + key, WireGuard server key, SSH host keys, sessions, audit log, telemetry UUID, and DNS-VIP allocations.

Device (set up by join / login):

~/.clawpatrol/
  ca.crt                  Fetched gateway CA
~/.config/clawpatrol/
  wg.conf                 Per-device WireGuard config (join path)