Quick setup aliases

Connector-oriented setup aliases for supported DefenseClaw integrations.

Each connector has a setup alias that runs setup guardrail --connector <id> with a smaller, connector-oriented flag set. The hook aliases start in observe mode and never proxy model traffic. OpenClaw and ZeptoClaw run the guardrail proxy regardless of mode.

Direct-to-upstream aliases (hook or policy enforcement)

AgentIdAliasClass
Claude Codeclaudecodedefenseclaw setup claude-codeHook
Codexcodexdefenseclaw setup codexHook
Cursorcursordefenseclaw setup cursorHook
Devindevindefenseclaw setup devinHook
GitHub Copilot CLIcopilotdefenseclaw setup copilotHook
Antigravityantigravitydefenseclaw setup antigravityHook
Hermeshermesdefenseclaw setup hermesHook
OpenCodeopencodedefenseclaw setup opencodeHook (JS bridge)
Ampampdefenseclaw setup ampPolicy plugin
Kirokirodefenseclaw setup kiroHook

What a direct-to-upstream alias does

An alias selects the connector, wires its hook or plugin, writes config.yaml, the connector roster and the picked_connector hint, and restarts the gateway unless --no-restart.

Common flags

Every hook alias takes these flags; run defenseclaw setup <connector> --help for the exact list. The policy flags write a per-connector override on a multi-connector install, and the global value when the connector is the only one.

Prop

Type

Port 3000 is the current local-stack preflight

--with-local-stack treats any TCP listener on 127.0.0.1:3000 as an already-running stack and skips local-observability up, including its destination wiring. If the bundled stack or expected destination is absent, run defenseclaw setup local-observability up explicitly and follow the printed defenseclaw-gateway restart step.

Examples:

defenseclaw setup claude-code
defenseclaw setup codex --with-local-stack
defenseclaw setup cursor --no-restart
defenseclaw setup openclaw --mode action --human-approval --rule-pack default --restart

Full guardrail aliases (proxy connectors)

AgentIdAliasClass
OpenClawopenclawdefenseclaw setup openclawProxy
ZeptoClawzeptoclawdefenseclaw setup zeptoclawProxy

Add or reconfigure connectors

On a host with another connector already configured, an alias asks whether to Add the new connector or Replace the old one. Add is the default, also under --yes. Pass --replace to switch. Only the aliases add a connector to the roster: setup guardrail --connector <name> tunes a connector already on it and refuses one that is not, with No changes made and the alias that adds it. defenseclaw setup remove <connector> retires one.

For the questions setup asks and the Replace flow, see Changing connectors.

Why aliases at all?

--connector is the scope selector after setup too: defenseclaw skill list --connector codex, defenseclaw mcp scan --connector cursor and defenseclaw guardrail status --connector hermes use the same scope.