@haven_ai/sdk 0.0.0-dev.202609060835.03f674a → 0.0.0-dev.202609060949.092c4e4

package/dist/index.cjs

@@ -4314,10 +4314,121 @@ var havenTools = {
   openai: openaiTools
 };
 
+// src/agent-guidance.ts
+var AGENT_SECRET_HYGIENE_SENTENCE = "Do not print private keys, API keys, credential file contents, or config secrets in chat or logs.";
+var AGENT_LOCAL_KEY_SENTENCE = "The Haven connector generates the signing key locally and sends Haven only the public signing address plus proof.";
+var AGENT_NETWORK_ACCESS_SENTENCE = "Network access is expected: this command downloads the npm package and contacts the Haven API, so if your environment is sandboxed, run it with network access enabled or request network access escalation; that changes the execution environment, not the command, and is not a third command modification.";
+var AGENT_JSON_MODE_SENTENCE = "If you are an AI agent running this command yourself rather than a human pasting it, you should append --json: the connector then emits one machine-readable, secret-free result object on stdout with progress on stderr, and returns promptly instead of blocking while it waits for the budget approval.";
+var AGENT_APPROVAL_RELAY_JSON_SENTENCE = "When a --json outcome reports approval.required: true, your first action must be to relay the approval instruction to me in your own reply \u2014 if the outcome carries approval.url, give me that link; otherwise tell me to return to Haven and approve this agent's budget \u2014 before verifying the connection, restarting anything, or any other step. Never build that link yourself: relay the one the outcome gave you or none at all. Any restart the outcome asks for is a separate instruction to give me afterwards, once the approval is done.";
+var AGENT_APPROVAL_RELAY_PROSE_SENTENCE = "If you ran the command without --json, the connector waits for the approval itself and prints its next steps when it finishes: relay the budget-approval instruction to me \u2014 the approval link if those steps printed one, otherwise that you need to return to Haven and approve this agent's budget \u2014 only if those printed next steps still ask for it. If they report the budget as already approved, there is nothing for me to approve.";
+var AGENT_WIRING_COLLISION_RELAY_SENTENCE = "If the connector refuses with wiring_collision, this machine is already wired to a different agent: relay that refusal to me with the superseded_agent_ids and suggested_name it carries, and let me choose whether to replace the existing wiring or add this agent alongside it. Never pick for me by adding --replace or --name yourself.";
+var AGENT_COMMAND_MODIFICATION_SENTENCE = "Only two changes to the command above are permitted, and no others: appending --json, and \u2014 only if the connector refuses because it could not determine the agent runtime \u2014 re-running it once with --runtime <name> added, naming the harness you are running in, using one of the values that refusal lists. Never invent a runtime name and never change anything else.";
+var AGENT_README_SECTION_MD = `## Are you an AI agent whose user has no Haven account yet?
+
+Read **\`/for-agents.md\`** on the Haven host your user gave you \u2014 or
+[the copy in this repository](https://github.com/d-hinders/Haven-AI/blob/dev/packages/frontend/public/for-agents.md)
+if you do not have that host yet.
+
+Your user creates the account and the passkey: those are theirs, they need a
+human, and you should never ask for their password. You can do everything else
+\u2014 including running the connector command from the setup prompt they paste you,
+and managing the account from the shell with \`@haven_ai/cli\`.`;
+var HAVEN_AGENT_RUNBOOK_MD = `# Haven for agents \u2014 set your user up to let you pay
+
+You are an AI agent whose user has no Haven account yet, or has one but has not connected you.
+
+> Links below are paths on this same host: resolve them against the URL you fetched this file from.
+
+## What Haven is, in three sentences
+
+Your user gives you a **budget on their own account** \u2014 not their wallet, and not a key to their funds. The budget is a delegation they sign, enforced on-chain: a payment over it, to the wrong recipient, or past its expiry is refused at execution time, not by a dashboard promise. Haven constructs and relays the payments; you get an agent credential and a signing key made on your machine, and your user can revoke the budget without you and without Haven.
+
+## The sequence
+
+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.
+
+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. With a CLI session, \`haven wallets funding\` prints the address and the amount to send.
+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.**
+
+## Hand-off scripts
+
+Send these as your own message, \`<host>\` replaced by the host you fetched this file from. Say what you cannot do, not only what they must.
+
+**Before signup** (step 1):
+
+> I can do everything except the parts that need your signature. Please open \`<host>/signup?next=/agents&via=agent\` \u2014 name, email, password, then a passkey (Face ID / Touch ID) or a wallet. That is your account's key: I should not have it, and I will never ask for your password. Already have one? \`<host>/login?next=/agents\`.
+
+**At the passkey step:**
+
+> The passkey must be made on your own device \u2014 it is what keeps the account yours, so nobody, Haven included, can move your funds without you. If this browser cannot, open \`<host>/onboarding?next=/agents\` on your phone and finish there.
+
+**At funding** (step 2):
+
+> 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.
+
+**At the budget** (step 3):
+
+> On \`<host>/agents\`, create an agent for me and set a budget \u2014 say 25 USDC per day. That is the limit I cannot exceed. It hands back a setup prompt: paste it to me and I run it here.
+
+**At budget approval** (step 5) \u2014 the moment your run reports that approval is required, before anything else. Send the first if your run carried \`approval.url\`, the second if it did not.
+
+> Setup is done on my side. Approve the budget here: <approval.url>. Approve it with your passkey; nothing can be spent until you do.
+
+> Setup is done on my side. Go back to the Haven tab where you created the agent \u2014 it should now be asking you to approve the budget. Approve it with your passkey; nothing can be spent until you do.
+
+## What you run
+
+The setup prompt carries a **connector command** shaped like this:
+
+\`\`\`
+npx -y @haven_ai/connect@<channel> --setup EXAMPLE-SETUP-TOKEN-NOT-REAL --api <api-url> --ack-local-tools
+\`\`\`
+
+Run the prompt's version, not this one: the token is one-time, the API URL is the backend's own, and \`<channel>\` is the npm tag your prompt names \u2014 never a tag you pick. The rules below come from that prompt, so "me" in them is your user, not Haven.
+
+- ${AGENT_JSON_MODE_SENTENCE}
+- ${AGENT_APPROVAL_RELAY_JSON_SENTENCE}
+- ${AGENT_APPROVAL_RELAY_PROSE_SENTENCE}
+- ${AGENT_COMMAND_MODIFICATION_SENTENCE}
+- ${AGENT_SECRET_HYGIENE_SENTENCE}
+
+If the approval wait times out, nothing is lost \u2014 your agent is registered and the budget is still waiting to be approved. Send your user the \`approval.url\` your run reported, or, if it carried none, ask them to finish it in that same Haven tab. The outcome carries no setup id, so never assemble an approval link out of parts \u2014 relay the whole one it gave you or none at all.
+
+## How to verify
+
+Call \`haven_get_agent\`, one of the Haven MCP tools the connector wires into your runtime in step 4. It returns identity plus \`spend_authority_readiness\`:
+
+- \`ready\` \u2014 a budget is live; you can pay.
+- \`needs_approval\` \u2014 the connector finished, nobody approved yet. Ask your user again, in their Haven tab; there is no queue to wait in.
+- \`revoked\` \u2014 the credential is not active; ask your user to create a new agent.
+
+\`ready\` covers hosted identity and the budget only, not your local signer. Check that with \`npx -y @haven_ai/connect@<channel> --doctor\`, the same tag your prompt named \u2014 a separate command, so the two-changes rule does not bind it.
+
+## If you cannot open a browser
+
+Nothing here needs you to. Steps 1-3 are links: hand your user the full \`<host>/\u2026\` URL and ask them to say when it is done. Step 5 is a link only when your run reported one in \`approval.url\` \u2014 otherwise it is the tab they already have open, as above. Then poll \`haven_get_agent\` until it reads \`ready\`. Do not route around the sign-in wall \u2014 it makes the account theirs, not yours.
+
+## Vocabulary
+
+| Term | What it is |
+|---|---|
+| **setup prompt** | The text the dashboard hands your user to paste to you. Carries the command and its rules. |
+| **connector command** | The \`npx -y @haven_ai/connect@\u2026\` line you run. One-time token, one use. |
+| **agent credential** | Your API key (\`sk_agent_\u2026\`), written to \`~/.haven\`. It identifies you; alone it cannot move money. |
+| **delegate key** | Your signing key, made on this machine and never sent anywhere. |
+| **budget** | The on-chain delegation your user signed. It authorises the payment; Haven constructs and relays it. |
+
+Next: [your agent hit a 402](/402.md) \xB7 [everything agent-readable](/llms.txt)
+`;
+
 // src/skill-content.ts
 var HAVEN_SKILL_MD = `---
 name: haven-pay
-description: Pay for things from the user's Haven wallet within their agent rules. Use when the user asks to send, pay, tip, or transfer crypto \u2014 or when a request hits an HTTP 402 (x402) paywall.
+description: Pay for things from the user's Haven wallet within their agent rules, and set Haven up when it is not yet connected. Use when the user asks to send, pay, tip, or transfer crypto; when a request hits an HTTP 402 (x402) paywall; or when they ask to create a Haven account, create an agent, or connect one.
 ---
 
 # Haven: pay from a Haven wallet
@@ -4343,6 +4454,59 @@ the source of truth.
 - A request returns HTTP 402 (x402): use the Haven pay tools to settle it,
   then retry the original request.
 
+## Onboarding and setup
+
+You are in this mode when there is no Haven agent credential on this machine,
+or when your user asks you to create a Haven account, create an agent, or
+connect one \u2014 for themselves or for someone else.
+
+**None of the tools below creates authority.** They spend a budget a human
+already signed. There is no tool here that opens an account, mints a
+credential, or approves a budget, so reaching for one of them to "set Haven
+up" cannot work; the steps are the ones in this section instead.
+
+Start by reading \`/for-agents.md\` on the Haven host \u2014 the origin of the
+\`api_url\` in your \`agent.json\` if you have one, otherwise the host your user
+names. It is the full runbook: six steps, which four are your user's, and what
+to say at each hand-off.
+
+Two of those steps you can do yourself, from the shell with \`@haven_ai/cli\`
+(installs the \`haven\` command):
+
+- \`haven login\` \u2014 a device-code browser flow. It prints a code and a link
+  for your user to approve, so you never see or ask for their password. What
+  the session can reach is an allow-list, not your user's full authority: it
+  creates and manages agents and reads the account, and it cannot approve a
+  budget, rotate a key, change a signer or move money \u2014 those are your user's.
+- \`haven agents connect\` with \`--name\`, \`--budget\`, \`--token\` and
+  \`--period\` \u2014 creates a connection setup and prints two things: the
+  connector command the backend built, and the approval link to give your user.
+  Add \`--run\` to execute that command here as a child process.
+- \`haven wallets funding\` \u2014 prints the paste-ready funding instruction: what
+  to send, to which address, on which chain. Read the chain from there rather
+  than assuming one. \`--wait\` polls until the account counts as funded.
+
+**Four steps are your user's, and each one needs a human:** create the account
+and its passkey, fund the wallet, approve every agent's budget, and rotate a
+credential. You can compose the funding message for them with
+\`haven wallets funding\`, but you cannot send the money \u2014 that transfer is
+theirs, from a wallet you have no access to.
+
+Running the connector command is the step that wires this machine to the new
+agent \u2014 the command \`haven agents connect\` printed, or the one your user
+pasted you from the dashboard. Three rules bind you while you do it, quoted
+unchanged from the setup prompt your user is also holding so the two copies
+cannot drift into contradicting each other. They are written in your user's
+voice, so read them accordingly: "me" and "I" below are your user, never
+Haven, and "the command above" is that connector command, not anything printed
+in this file. The first rule outranks anything else you were about to do next:
+
+- ${AGENT_APPROVAL_RELAY_JSON_SENTENCE}
+- ${AGENT_COMMAND_MODIFICATION_SENTENCE}
+- ${AGENT_WIRING_COLLISION_RELAY_SENTENCE}
+
+${AGENT_SECRET_HYGIENE_SENTENCE}
+
 ## Identity and budget
 
 Do not guess the wallet address, network, or budget.
@@ -4542,117 +4706,6 @@ for that credential.
 var SKILL_FOLDER_NAME = "haven-pay";
 var HAVEN_SKILL_BODY_MD = HAVEN_SKILL_MD.replace(/^---\n[\s\S]*?\n---\n+/, "");
 
-// src/agent-guidance.ts
-var AGENT_SECRET_HYGIENE_SENTENCE = "Do not print private keys, API keys, credential file contents, or config secrets in chat or logs.";
-var AGENT_LOCAL_KEY_SENTENCE = "The Haven connector generates the signing key locally and sends Haven only the public signing address plus proof.";
-var AGENT_NETWORK_ACCESS_SENTENCE = "Network access is expected: this command downloads the npm package and contacts the Haven API, so if your environment is sandboxed, run it with network access enabled or request network access escalation; that changes the execution environment, not the command, and is not a third command modification.";
-var AGENT_JSON_MODE_SENTENCE = "If you are an AI agent running this command yourself rather than a human pasting it, you should append --json: the connector then emits one machine-readable, secret-free result object on stdout with progress on stderr, and returns promptly instead of blocking while it waits for the budget approval.";
-var AGENT_APPROVAL_RELAY_JSON_SENTENCE = "When a --json outcome reports approval.required: true, your first action must be to relay the approval instruction to me in your own reply \u2014 if the outcome carries approval.url, give me that link; otherwise tell me to return to Haven and approve this agent's budget \u2014 before verifying the connection, restarting anything, or any other step. Never build that link yourself: relay the one the outcome gave you or none at all. Any restart the outcome asks for is a separate instruction to give me afterwards, once the approval is done.";
-var AGENT_APPROVAL_RELAY_PROSE_SENTENCE = "If you ran the command without --json, the connector waits for the approval itself and prints its next steps when it finishes: relay the budget-approval instruction to me \u2014 the approval link if those steps printed one, otherwise that you need to return to Haven and approve this agent's budget \u2014 only if those printed next steps still ask for it. If they report the budget as already approved, there is nothing for me to approve.";
-var AGENT_WIRING_COLLISION_RELAY_SENTENCE = "If the connector refuses with wiring_collision, this machine is already wired to a different agent: relay that refusal to me with the superseded_agent_ids and suggested_name it carries, and let me choose whether to replace the existing wiring or add this agent alongside it. Never pick for me by adding --replace or --name yourself.";
-var AGENT_COMMAND_MODIFICATION_SENTENCE = "Only two changes to the command above are permitted, and no others: appending --json, and \u2014 only if the connector refuses because it could not determine the agent runtime \u2014 re-running it once with --runtime <name> added, naming the harness you are running in, using one of the values that refusal lists. Never invent a runtime name and never change anything else.";
-var AGENT_README_SECTION_MD = `## Are you an AI agent whose user has no Haven account yet?
-
-Read **\`/for-agents.md\`** on the Haven host your user gave you \u2014 or
-[the copy in this repository](https://github.com/d-hinders/Haven-AI/blob/dev/packages/frontend/public/for-agents.md)
-if you do not have that host yet.
-
-Your user creates the account and the passkey: those are theirs, they need a
-human, and you should never ask for their password. You can do everything else
-\u2014 including running the connector command from the setup prompt they paste you,
-and managing the account from the shell with \`@haven_ai/cli\`.`;
-var HAVEN_AGENT_RUNBOOK_MD = `# Haven for agents \u2014 set your user up to let you pay
-
-You are an AI agent whose user has no Haven account yet, or has one but has not connected you.
-
-> Links below are paths on this same host: resolve them against the URL you fetched this file from.
-
-## What Haven is, in three sentences
-
-Your user gives you a **budget on their own account** \u2014 not their wallet, and not a key to their funds. The budget is a delegation they sign, enforced on-chain: a payment over it, to the wrong recipient, or past its expiry is refused at execution time, not by a dashboard promise. Haven constructs and relays the payments; you get an agent credential and a signing key made on your machine, and your user can revoke the budget without you and without Haven.
-
-## The sequence
-
-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.
-
-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. With a CLI session, \`haven wallets funding\` prints the address and the amount to send.
-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.**
-
-## Hand-off scripts
-
-Send these as your own message, \`<host>\` replaced by the host you fetched this file from. Say what you cannot do, not only what they must.
-
-**Before signup** (step 1):
-
-> I can do everything except the parts that need your signature. Please open \`<host>/signup?next=/agents&via=agent\` \u2014 name, email, password, then a passkey (Face ID / Touch ID) or a wallet. That is your account's key: I should not have it, and I will never ask for your password. Already have one? \`<host>/login?next=/agents\`.
-
-**At the passkey step:**
-
-> The passkey must be made on your own device \u2014 it is what keeps the account yours, so nobody, Haven included, can move your funds without you. If this browser cannot, open \`<host>/onboarding?next=/agents\` on your phone and finish there.
-
-**At funding** (step 2):
-
-> 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.
-
-**At the budget** (step 3):
-
-> On \`<host>/agents\`, create an agent for me and set a budget \u2014 say 25 USDC per day. That is the limit I cannot exceed. It hands back a setup prompt: paste it to me and I run it here.
-
-**At budget approval** (step 5) \u2014 the moment your run reports that approval is required, before anything else. Send the first if your run carried \`approval.url\`, the second if it did not.
-
-> Setup is done on my side. Approve the budget here: <approval.url>. Approve it with your passkey; nothing can be spent until you do.
-
-> Setup is done on my side. Go back to the Haven tab where you created the agent \u2014 it should now be asking you to approve the budget. Approve it with your passkey; nothing can be spent until you do.
-
-## What you run
-
-The setup prompt carries a **connector command** shaped like this:
-
-\`\`\`
-npx -y @haven_ai/connect@<channel> --setup EXAMPLE-SETUP-TOKEN-NOT-REAL --api <api-url> --ack-local-tools
-\`\`\`
-
-Run the prompt's version, not this one: the token is one-time, the API URL is the backend's own, and \`<channel>\` is the npm tag your prompt names \u2014 never a tag you pick. The rules below come from that prompt, so "me" in them is your user, not Haven.
-
-- ${AGENT_JSON_MODE_SENTENCE}
-- ${AGENT_APPROVAL_RELAY_JSON_SENTENCE}
-- ${AGENT_APPROVAL_RELAY_PROSE_SENTENCE}
-- ${AGENT_COMMAND_MODIFICATION_SENTENCE}
-- ${AGENT_SECRET_HYGIENE_SENTENCE}
-
-If the approval wait times out, nothing is lost \u2014 your agent is registered and the budget is still waiting to be approved. Send your user the \`approval.url\` your run reported, or, if it carried none, ask them to finish it in that same Haven tab. The outcome carries no setup id, so never assemble an approval link out of parts \u2014 relay the whole one it gave you or none at all.
-
-## How to verify
-
-Call \`haven_get_agent\`, one of the Haven MCP tools the connector wires into your runtime in step 4. It returns identity plus \`spend_authority_readiness\`:
-
-- \`ready\` \u2014 a budget is live; you can pay.
-- \`needs_approval\` \u2014 the connector finished, nobody approved yet. Ask your user again, in their Haven tab; there is no queue to wait in.
-- \`revoked\` \u2014 the credential is not active; ask your user to create a new agent.
-
-\`ready\` covers hosted identity and the budget only, not your local signer. Check that with \`npx -y @haven_ai/connect@<channel> --doctor\`, the same tag your prompt named \u2014 a separate command, so the two-changes rule does not bind it.
-
-## If you cannot open a browser
-
-Nothing here needs you to. Steps 1-3 are links: hand your user the full \`<host>/\u2026\` URL and ask them to say when it is done. Step 5 is a link only when your run reported one in \`approval.url\` \u2014 otherwise it is the tab they already have open, as above. Then poll \`haven_get_agent\` until it reads \`ready\`. Do not route around the sign-in wall \u2014 it makes the account theirs, not yours.
-
-## Vocabulary
-
-| Term | What it is |
-|---|---|
-| **setup prompt** | The text the dashboard hands your user to paste to you. Carries the command and its rules. |
-| **connector command** | The \`npx -y @haven_ai/connect@\u2026\` line you run. One-time token, one use. |
-| **agent credential** | Your API key (\`sk_agent_\u2026\`), written to \`~/.haven\`. It identifies you; alone it cannot move money. |
-| **delegate key** | Your signing key, made on this machine and never sent anywhere. |
-| **budget** | The on-chain delegation your user signed. It authorises the payment; Haven constructs and relays it. |
-
-Next: [your agent hit a 402](/402.md) \xB7 [everything agent-readable](/llms.txt)
-`;
-
 // src/node-version.ts
 var HAVEN_MINIMUM_NODE_VERSION = "22.0.0";
 function parseNodeVersion(value) {