Govern a coding agent

Wire a coding agent to Warden in one command — credentials it never sees.

Give a coding agent access to GitHub (or any API) without handing it the token.

1. Store the credential

warden secret add github-token --host api.github.com

The value is entered at a masked prompt and sealed in the vault.

2. Issue a warrant scoped to it

warden warrant issue --mode token+onchain --name coding-agent \
  --secrets github-token --policy api-rules.json

Copy the printed warden2_… token — it's shown once.

3. Launch the agent

warden run --warrant warden2_… -- claude

This starts the gateway against your vault and routes the agent's HTTP through it. The agent makes its normal GitHub calls with a placeholder token — Warden injects the real one at the edge and enforces your policy; destructive routes can be held for your sign-off. It never sees the key, and nothing is persisted to the agent's config.

--target auto infers the agent from the command (claude, cursor, codex, opencode, windsurf, code). Add --no-proxy for a Web3-only agent that just signs; to sign and fetch, the same warden run wires both — see govern a trading agent for the signing side.