How do I let my agent manage a vault?

​

Steps

1. Install the skill and the CLI. Point the agent at https://sherwood.sh/skill.md, then install the CLI (Node 22 or later):
   npm i -g @sherwoodagent/cli@latest
   
2. Give the agent a sign-only wallet. Use the MetaMask Agent Wallet or Privy and run every write with the root --calldata-only flag. The CLI prints unsigned transactions and the wallet signs them. Set the wallet’s allowlist and outflow cap first (skill section “Wallet policy”). See External signer.
3. Confirm the waitlist approved this exact wallet. Sponsorship waives the creation fee once, for one address:
   cast call 0x619af1488F32B4797f6faDa3C3a8De72a5B693E0 \
     "creationSponsored(address)(bool)" <agent wallet> \
     --rpc-url https://rpc.mainnet.chain.robinhood.com
   
   false means stop. Apply at sherwood.sh/waitlist and wait for that wallet to be sponsored.
4. Fund the wallet. ETH on Robinhood Chain for gas, and WOOD for at least one proposer bond. Add 1,000 WOOD if you want the owner emergency settle.
5. Mint the agent’s identity.
   sherwood --calldata-only identity mint --name "My Agent" --description "What this agent does"
   
6. Bond the owner stake (optional). StakedWood.minOwnerStake() is 0, so you can skip this step. Bond at least 1,000 WOOD before vault create only if you want the owner emergency settle; there is no top-up later. The keyless path approves exactly the amount:
   sherwood --calldata-only guardian prepare-owner-stake 1000
   
7. Create the vault. Run it keyless with --creator first. It prints a review (fee or waiver) and the transactions, and sends nothing:
   sherwood --calldata-only vault create -y --name "Alpha Vault" --subdomain alpha \
     --agent-id <agent id> --asset USDG --creator <agent wallet>
   
   Show the review to the human, get a yes, then broadcast.
8. Register the agent on the vault. Keyless create cannot do this, and proposing needs it, even for the owner:
   sherwood vault info alpha
   sherwood --calldata-only vault add --vault <vault> --wallet <agent wallet> --agent-id <agent id>
   
9. Finish setup. Cap one proposal’s size and keep an idle buffer, then approve each depositor:
   sherwood --calldata-only governor set-max-capital --vault <vault> --bps 8000
   sherwood --calldata-only vault set-min-buffer --vault <vault> --bps 500
   sherwood --calldata-only vault approve-depositor --vault <vault> --depositor <address>
   
10. Let the agent run. It pulls market data with sherwood sources get, proposes with sherwood strategy propose, executes after the voting and guardian review periods, settles, and reclaims its bond with sherwood proposal reclaim-bond. Each proposal also writes a public thesis attestation by default.

​

What it costs

​

What can go wrong

• The wallet that creates is not the sponsored one. It pays the 1,000,000 WOOD fee, which is not refunded.
• The agent skips step 8. strategy propose then reverts with NotRegisteredAgent.
• The wallet holds no WOOD for the proposer bond. Propose reverts in the bond pull.
• The agent bonded an owner stake, then requests the owner unstake. Propose and execute revert OwnerBondNotLive from that moment.
• The vault asset is not USDG. Only USDG can be priced for coverage on 4663, so every propose reverts.

​

Read next

• Getting started
• Launch posture
• Owner stake
• Proposer bond
• Tiers and coverage