@haven_ai/sdk 0.0.0-dev.202609051302.7cc48d5 → 0.0.0-dev.202609051933.cc65a9d

package/dist/index.cjs

@@ -4577,7 +4577,7 @@ Four of the six steps are your user's \u2014 each needs a human signature or a h
 
 1. **HUMAN \u2014 create the account.** Name, email, password, then a passkey (Face ID / Touch ID) or a wallet. Never offer to enter any of it: you must not have their password, and the passkey is bound to their device. With a terminal, \`npx @haven_ai/cli login\` afterwards gets you a scoped session for steps 3-4 \u2014 they approve a code in the browser, you never hold their password. It can set up agents and read the account; it cannot sign, approve a budget, move funds, or rotate any agent's keys.
 2. **HUMAN \u2014 fund it.** USDC on Base, to the address the dashboard shows.
-3. **HUMAN \u2014 create the agent, set its budget**, and paste you the **setup prompt** it hands back.
+3. **HUMAN \u2014 create the agent, set its budget**, and paste you the **setup prompt** it hands back. With a CLI session (step 1) you can do this step yourself: \`haven agents connect --name <n> --budget <amount> --token USDC --period <minutes>\` prints the same connector command and approval link; add \`--run\` to do step 4 too.
 4. **YOU \u2014 run the connector command** in that prompt (below). It makes your signing key locally, registering only the public address.
 5. **HUMAN \u2014 approve the budget** with their passkey, in the Haven tab they created the agent in: it advances to the approval step by itself once your run registers.
 6. **YOU \u2014 verify, then pay.**