Quick setup aliases
defenseclaw setup codex, setup claude-code, setup cursor, setup copilot, setup hermes, setup geminicli, setup windsurf, setup openclaw, setup zeptoclaw — one command per agent, no questions asked.
Each connector has a top-level alias that wraps defenseclaw setup guardrail with the right defaults. Use them for fast subsequent runs and CI scripts.
Observability-only aliases (no enforcement)
These connectors talk directly to their native upstream. DefenseClaw collects telemetry (hooks, native OTel, optional notify bridge) without sitting in the LLM data path.
Codex
defenseclaw setup codex
Claude Code
defenseclaw setup claude-code
Cursor
defenseclaw setup cursor
Windsurf
defenseclaw setup windsurf
Gemini CLI
defenseclaw setup geminicli
GitHub Copilot CLI
defenseclaw setup copilot
Hermes
defenseclaw setup hermes
defenseclaw setup claude-code
defenseclaw setup codex --with-local-stack # also brings up Prom/Loki/Tempo/Grafana
defenseclaw setup cursor --no-restart # apply config without bouncing the gatewayThe observability-only aliases pin claw.mode=<connector> so the rest of the CLI/TUI (skill scanner, MCP scanner, plugin scanner, overview panels) reads from the matching connector's source-of-truth files (e.g., ~/.codex/, ~/.claude/) instead of OpenClaw's default layout.
What an observability-only alias does
Pins guardrail.connector and claw.mode to the chosen connector so downstream commands read the right state directory.
Disables the matching enforcement flag (codex_enforcement_enabled / claudecode_enforcement_enabled) so the proxy listener never binds and openai_base_url / ANTHROPIC_BASE_URL are not rewritten.
Wires the connector's hook scripts and (where supported) native OTel exporter against the running gateway.
Persists config.yaml and writes the picked_connector hint so future defenseclaw setup guardrail runs default to the same connector.
Restarts the gateway (unless --no-restart).
Common flags
Prop
Type
Full guardrail aliases (proxy connectors)
OpenClaw and ZeptoClaw run the full guardrail proxy regardless of mode — there is no observability-only path because the proxy is the integration. Their aliases mirror defenseclaw setup guardrail --connector <name> with safer defaults.
defenseclaw setup openclaw --mode observe --restart
defenseclaw setup openclaw --mode action --human-approval --rule-pack strict --restartSwitch active connector
Use defenseclaw setup mode <connector> to switch the active claw connector with smart guardrail inheritance — see Switching connectors.
Why aliases at all?
Operators who only want telemetry (no traffic interception, no enforcement) used to walk through the full setup guardrail wizard, answer "yes" to a single confirm, and trust that the wizard did the right thing under the hood. The aliases shortcut that:
defenseclaw setup codex # observability-only for Codex
defenseclaw setup claude-code # observability-only for Claude Code
defenseclaw setup cursor # observability-only for Cursor
defenseclaw setup openclaw # full guardrail for OpenClawBoth halves also flip claw.mode so the rest of the CLI/TUI reads from the matching connector's source-of-truth files. Without this flip, defenseclaw skill scan --all after setup codex would scan ~/.openclaw/skills and miss every Codex skill — a foot-gun the aliases explicitly close.
defenseclaw setup guardrail
The central command. Routes LLM traffic through the Go guardrail proxy, configures observe vs action mode, picks the connector, scanner, rule pack, judge, and HITL behaviour, then restarts the gateway.
Switching connectors
defenseclaw setup mode <connector> — switch the active connector with smart guardrail inheritance. Audit history is preserved; only the connector wiring moves.