Skip to main content
Run warden <command> -h for a command’s flags.

​
warden serve

Runs the gateway. At startup it prints, in order: configuration warnings, each connection’s capability ladder, the state directory, and any recovery notes from the journals. It refuses to start when a connection cannot meet its policy, when the audit chain is broken, or when a non-loopback listener has no TLS and no explicit permission. Shuts down cleanly on SIGINT/SIGTERM: in-flight operations finish, journals are closed.

​
warden debug attach

Starts a Debug Mode session and streams paused operations to your terminal. For each one you see the statement, the parameters, the blast radius, and the agent’s stated reason, and you answer: See Debug Mode.

​
warden audit

--url and --token work as they do for debug attach. verify exits non-zero on a break and names the event where the chain stops matching. See audit.

​
warden policy lint

Takes the policy file as an argument and checks shape and internal consistency: resources, scope bindings, masking rules, approval classes, and combinations that are individually valid but dangerous together — a granted table with no scopable column, for instance. Exits non-zero when the report is not clean.
Linting here does not probe a live connection, so it cannot check the require: block — those levels need an engine. warden serve performs that check at startup and refuses to start when the engine falls short.

​
warden keygen

Prints the credential once, with the hash to paste into warden.yaml. Store the plaintext in your secret manager; the configuration file should carry only the hash, so that the file is not itself a credential.

​
warden version

Prints the version stamped at build time. dev means a build from a branch or a working tree rather than a tagged release.