@haven_ai/sdk 0.0.0-dev.202609051933.cc65a9d → 0.0.0-dev.202609060835.03f674a
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.cjs +2 -2
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +1 -1
- package/dist/index.d.ts +1 -1
- package/dist/index.js +2 -2
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/dist/index.cjs
CHANGED
|
@@ -4576,7 +4576,7 @@ Your user gives you a **budget on their own account** \u2014 not their wallet, a
|
|
|
4576
4576
|
Four of the six steps are your user's \u2014 each needs a human signature or a human decision. The rest is yours. If they already have a funded account, start at step 3.
|
|
4577
4577
|
|
|
4578
4578
|
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.
|
|
4579
|
-
2. **HUMAN \u2014 fund it.** USDC on Base, to the address the dashboard shows.
|
|
4579
|
+
2. **HUMAN \u2014 fund it.** USDC on Base, to the address the dashboard shows. With a CLI session, \`haven wallets funding\` prints the address and the amount to send.
|
|
4580
4580
|
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.
|
|
4581
4581
|
4. **YOU \u2014 run the connector command** in that prompt (below). It makes your signing key locally, registering only the public address.
|
|
4582
4582
|
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.
|
|
@@ -4596,7 +4596,7 @@ Send these as your own message, \`<host>\` replaced by the host you fetched this
|
|
|
4596
4596
|
|
|
4597
4597
|
**At funding** (step 2):
|
|
4598
4598
|
|
|
4599
|
-
> Your Haven account needs USDC on Base before I can pay for anything \u2014 USDC only, no ETH: Haven sponsors the gas. The dashboard shows the address to send it to; a small amount first is fine.
|
|
4599
|
+
> Your Haven account needs USDC on Base before I can pay for anything \u2014 USDC only, no ETH: Haven sponsors the gas. The dashboard shows the address to send it to; a small amount first is fine. If I have a terminal session, \`haven wallets funding\` prints the address, the amount and an explorer link \u2014 say the word and I will paste them here.
|
|
4600
4600
|
|
|
4601
4601
|
**At the budget** (step 3):
|
|
4602
4602
|
|