Add a connector without losing audit history
Use defenseclaw setup <connector> to add or reconfigure agent wiring while preserving audit history for every connector.
One gateway guards several agents at once, each with its own mode. Adding, replacing or removing an agent never deletes audit history: each audit row keeps the connector that produced it.
This story retells the walkthrough briefly. The full pages are Changing connectors and Multi-connector.
Try it
Add the second agent
Run the agent's setup command. If another agent is already guarded, setup asks.
defenseclaw setup codex DefenseClaw is already configured for: claudecode
You are setting up: codex
[a] Add — run it alongside the existing connector(s) (multi-connector)
[r] Replace — switch to only this connector
[c] Cancel — make no changes
Choose (a, r, c) [a]: a
…
OK Desired roster staged for 'codex' - 2 connectors selected: claudecode, codex
OK codex mode=observeAdd is the default, also with --yes. The new agent starts in observe mode. Add --mode action to block from the start.
Check both agents
Check both agents.
defenseclaw guardrail status * enabled: yes
Connector Key State Mode Fail Rule pack Block/alert HILT Scan Judge
----------- ---------- ------- ------- ---- --------- ---------------- ---- ---------- -----
Claude Code claudecode enabled observe open default CRITICAL/MEDIUM+ off regex_only off
Codex codex enabled observe open default CRITICAL/MEDIUM+ off regex_only offGive one agent its own settings
Give one agent its own settings. Add --connector to any guardrail command.
defenseclaw guardrail mode action --connector codex
defenseclaw guardrail hilt on --min-severity HIGH --connector claudecodeThe per-connector overrides table lists what each agent can override.
Replace one agent with another
Replace tears down the old agent's files and leaves only the new one.
defenseclaw setup claude-code --replace --mode actionSetup names the agents it removes and asks first (--yes skips the question). The same flag switches between a hook agent and a proxy agent (defenseclaw setup openclaw --replace) on Linux and macOS. Native Windows has no guardrail proxy, so OpenClaw and ZeptoClaw replacement is unsupported there. Without --replace, setup refuses and changes nothing.
Remove an agent
defenseclaw setup remove codex OK Removed connector 'codex'
OK Remaining connector(s): claudecode
Restarting gateway so the removed connector's hooks are torn down...--yes skips the question and --no-restart restarts later. Removing the last agent needs --force. DefenseClaw stays installed; defenseclaw uninstall removes it.
Check it worked
defenseclaw guardrail status lists only the agents you kept, and defenseclaw doctor reports no leftover hooks.
Next
Multi-connector
One gateway guards several agents at once, each with its own mode.
Changing connectors
Guard a second agent next to the first, replace one with another, or remove one.
Generate a setup command
Build a non-interactive defenseclaw setup guardrail command for any agent in the browser, then copy it.
Run the local observability stack
defenseclaw setup local-observability up starts the bundled OTel Collector + Prometheus, Loki, Tempo, and Grafana stack and writes its named v8 destination.
Enterprise deployment
What DefenseClaw enterprise hardening is, which profile to choose, what runs on each endpoint, and what a standard user can and cannot change on Windows, Linux, and macOS.