@haven_ai/cli 0.1.35-alpha.0 → 0.1.37-alpha.0

package/README.md

@@ -27,12 +27,16 @@ npm i -g @haven_ai/cli@alpha   # or run ad hoc: npx @haven_ai/cli@alpha <command
 haven --help
 ```
 
-A bare `npx @haven_ai/cli` resolves to the **same version** as `@alpha`: the
-`latest` dist-tag now tracks the newest published release (owner decision
-2026-09-04, mechanism in `publish.yml` since #2536). Verified on 2026-09-06 from
-a clean directory — `@alpha` and the bare form both `0.1.34-alpha.0`, `@dev` the
-snapshot `0.0.0-dev.202609061037.7cf43bb`. The pinned `@alpha` stays in the
-one-liner above because every generated artifact quotes that string verbatim.
+A bare `npx @haven_ai/cli` resolves to the `latest` dist-tag, which may be an
+**older build** than the one your deployment's docs describe — `latest` tracks
+the newest *published* release and nothing guarantees it matches the channel a
+given deployment serves (owner decision 2026-09-04 put the mechanism behind a
+release; issue [#2617](https://github.com/d-hinders/Haven-AI/issues/2617) is
+the reason the runbook and the manifest now name the channel explicitly). The
+runbook (`/for-agents.md`, printed by `haven guide`) and the manifest
+(`/.well-known/haven.json`, field `packages.cli.channel`) name the channel the
+deployment serves as `@<channel>`: read the tag from there, never pick one.
+`<channel>` below is that tag; `@alpha` is only a concrete example.
 
 The CLI talks to the hosted Haven backend by default. Point it elsewhere with
 `--api <url>` or `HAVEN_API_URL` (e.g. a local backend at
@@ -52,7 +56,8 @@ are your user's; these are the two that are yours.
 
 ```bash
 # 1. Get a scoped session. Prints a code and a link for your user to approve in
-#    a browser — you never see or ask for their password.
+#    a browser — you never see or ask for their password. @alpha is an example:
+#    run the tag your deployment names (see "Install" above).
 npx -y @haven_ai/cli@alpha login --api <api-url>
 
 # 2. Create the agent and its budget. Prints the connector command the backend
@@ -94,6 +99,8 @@ checks a command against. `haven --help` prints the same list.
 # auth
 haven login                              # browser device-code approval (the default)
 haven login --email you@example.com      # password path instead (prompt or HAVEN_PASSWORD)
+haven login --no-wait --json             # print the link object and exit — resume with --poll
+haven login --poll <device_code>         # one poll round: 0 approved, 3 pending, 4 denied
 haven whoami                             # user, session expiry, API URL
 haven guide                              # the agent onboarding runbook
 haven logout
@@ -238,16 +245,33 @@ driving this CLI must never hold its user's password.
 ```bash
 haven login --json
 # {"ok":true,"verification_url":"https://app.haven…/device?code=ABCD-2345",
-#  "user_code":"ABCD-2345","expires_at":"…"}
+#  "user_code":"ABCD-2345","device_code":"…","interval":5,"expires_at":"…"}
 ```
 
 Under `--json` that object is printed **before** polling begins, so an agent
 can hand its user the link immediately rather than after the flow completes.
-Add `--no-wait` to stop there and poll later; without it the CLI waits at the
-interval the server names, widening it when the server says `slow_down`.
+Without `--no-wait` the CLI then polls until approved, widening the interval
+when the server says `slow_down`.
 
-Exit codes carry the outcome an agent acts on: **3** when the code expired
-(ask for a new one), **4** when the human denied it (stop asking).
+**Non-blocking (for agents).** Under `--json` the wait is capped at **30
+seconds**: on timeout the CLI emits
+`{ "status": "pending", "device_code": "…", "retry_after": 5 }` and exits
+**3** — the flow is still alive, poll again. `--no-wait` skips even that wait
+and returns the link object at once. Either way, finish the flow with one
+poll round per invocation, so nothing holds your turn open:
+
+```bash
+haven login --api <api-url> --json --no-wait
+# { "ok": true, "verification_url": "…", "user_code": "ABCD-2345",
+#   "device_code": "…", "interval": 5, "expires_at": "…" } <- hand your user the link
+haven login --poll <device_code>                   # wait interval seconds first; repeat until it stops saying pending
+```
+
+Exit codes carry the outcome an agent acts on: **0** once approved (the same
+success object as the blocking path; the session is saved), **3** while still
+pending — the object carries `retry_after`, widened when the server says
+`slow_down` — and on an expired code, which means start over with a fresh
+`login`. **4** when the human denied it (stop asking).
 
 `haven login --email <address>` keeps the password path for a human who wants
 it. It is not removed — it is simply no longer what an agent gets by asking to
@@ -313,7 +337,7 @@ describes how to get out of. The string is generated from
 `packages/sdk/src/agent-guidance.ts` by
 `node packages/cli/scripts/sync-agent-guidance.mjs` and byte-pinned to it by a
 test; the copy exists so this package keeps **zero runtime dependencies** and
-`npx @haven_ai/cli` stays a small install for an agent.
+`npx @haven_ai/cli@<channel>` stays a small install for an agent.
 
 ## Config
 

package/dist/cli.cjs

@@ -27,7 +27,8 @@ var VALUE_FLAGS = /* @__PURE__ */ new Set([
   "--status",
   "--amount",
   "--recipient",
-  "--expires"
+  "--expires",
+  "--poll"
 ]);
 function parseArgs(argv) {
   const positionals = [];
@@ -90,6 +91,8 @@ function parseArgs(argv) {
       } else if (arg === "--format") {
         if (value !== "csv" && value !== "sie") throw new Error('--format must be "csv" or "sie"');
         flags.format = value;
+      } else if (arg === "--poll") {
+        flags.poll = value;
       } else if (arg === "--from") flags.from = value;
       else if (arg === "--to") flags.to = value;
       else if (arg === "--company") flags.company = value;
@@ -112,6 +115,11 @@ function helpText() {
     "  login                   Sign in. Opens a browser device-code approval by default \u2014",
     "                          it prints a code and a link, and never asks for a password",
     "  login --email <e>       Password path instead (prompt, or HAVEN_PASSWORD)",
+    "  login --no-wait         Print the link and exit instead of polling. Under --json,",
+    "                          pass it: you get the object back at once (it carries",
+    "                          device_code) and finish with `login --poll <device_code>`",
+    "  login --poll <code>     One poll round of a started device flow: exit 0 approved,",
+    "                          3 still pending (the object carries retry_after), 4 denied",
     "  logout                  Clear the saved session",
     "  whoami                  Show the signed-in user, session expiry and API URL",
     "",
@@ -374,7 +382,12 @@ function toFailure(err) {
         code: "not_authenticated",
         exit: EXIT.notAuthenticated,
         message: err.message,
-        hint: "Run `haven login` (or set HAVEN_EMAIL and HAVEN_PASSWORD)."
+        // #2618: the device flow is named FIRST because it is the path an
+        // agent can actually run — an agent never holds its user's password,
+        // which is the runbook's first rule; the previous hint led with the
+        // credentials as if they were the normal route. HAVEN_EMAIL and
+        // HAVEN_PASSWORD remain for a HUMAN scripting non-interactively.
+        hint: "Run `haven login` (device flow \u2014 it never asks for a password; under --json pass --no-wait, then resume with `login --poll <device_code>`). HAVEN_EMAIL and HAVEN_PASSWORD are the human, non-interactive path."
       };
     }
     if (err.status >= 400 && err.status < 500) {
@@ -416,7 +429,7 @@ ${failure.hint}` : failure.message);
 }
 
 // src/agent-guidance-text.ts
-var HAVEN_AGENT_RUNBOOK_MD = "# Haven for agents \u2014 set your user up to let you pay\n\nYou are an AI agent whose user has no Haven account yet, or has one but has not connected you.\n\n> Links below are paths on this same host: resolve them against the URL you fetched this file from.\n\n## What Haven is, in three sentences\n\nYour 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.\n\n## The sequence\n\nFour 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.\n\n1. **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 --api <api-url>` afterwards gets you a scoped session for steps 3-4 (that flag or `HAVEN_API_URL`, on the first command \u2014 the session then remembers the backend; **the CLI's built-in default is Haven's hosted production backend**, so on any other deployment an omitted flag connects you somewhere real and wrong rather than failing) \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.\n2. **HUMAN \u2014 fund it.** USDC only, no ETH: Haven sponsors the gas. `haven wallets funding` prints the address, the amount **and which chain** in one place; without a CLI session, the dashboard's funding card shows the address and amount and its Receive-funds screen names the chain. Read the chain off whichever you used and put it in your message \u2014 never assume one: a testnet deployment and production both call themselves Haven.\n3. **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.\n4. **YOU \u2014 run the connector command** in that prompt (below). It makes your signing key locally, registering only the public address.\n5. **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.\n6. **YOU \u2014 verify, then pay.**\n\n## Budget changes later (second token, raise, revoke)\n\nThe first budget rides the setup above. After the agent exists, a CLI session can construct the LATER changes \u2014 a second token, a bigger amount, a recipient pin, a stop \u2014 and hand your user a link; the human still signs, every time:\n\n```\nhaven budget grant <agentId> --amount <n> --token USDC --period <minutes> [--recipient <address>] [--wait]\nhaven budget revoke <agentId> <delegationHash> [--wait]\n```\n\nThe CLI never signs: it prints a dashboard link, your user opens it and signs with their passkey or wallet. `--wait` polls until the human's signature lands. The hash for `revoke` is in `haven agents show <agentId>`.\n\n## Hand-off scripts\n\nSend 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.\n\n**Before signup** (step 1):\n\n> 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`.\n\n**At the passkey step:**\n\n> 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.\n\n**At funding** (step 2):\n\n> Your Haven account needs USDC before I can pay for anything \u2014 USDC only, no ETH: Haven sponsors the gas. Before you send anything, let me get you the exact address **and network** \u2014 `haven wallets funding` prints both, and the funding card on `<host>/dashboard` shows the same. Please do not send to an address or a chain I have not confirmed with you; a small amount first is fine.\n\n**At the budget** (step 3):\n\n> 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.\n\n**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.\n\n> Setup is done on my side. Approve the budget here: <approval.url>. Approve it with your passkey; nothing can be spent until you do.\n\n> 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.\n\n## What you run\n\nThe setup prompt carries a **connector command** shaped like this:\n\n```\nnpx -y @haven_ai/connect@<channel> --setup EXAMPLE-SETUP-TOKEN-NOT-REAL --api <api-url> --ack-local-tools\n```\n\nRun 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.\n\n- 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.\n- 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.\n- 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.\n- 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.\n- Do not print private keys, API keys, credential file contents, or config secrets in chat or logs.\n\nIf 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.\n\n## How to verify\n\nCall `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`:\n\n- `ready` \u2014 a budget is live; you can pay.\n- `needs_approval` \u2014 the connector finished, nobody approved yet. Ask your user again, in their Haven tab; there is no queue to wait in.\n- `revoked` \u2014 the credential is not active; ask your user to create a new agent.\n\n`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.\n\n## If you cannot open a browser\n\nNothing 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.\n\n## Vocabulary\n\n| Term | What it is |\n|---|---|\n| **setup prompt** | The text the dashboard hands your user to paste to you. Carries the command and its rules. |\n| **connector command** | The `npx -y @haven_ai/connect@\u2026` line you run. One-time token, one use. |\n| **agent credential** | Your API key (`sk_agent_\u2026`), written to `~/.haven`. It identifies you; alone it cannot move money. |\n| **delegate key** | Your signing key, made on this machine and never sent anywhere. |\n| **budget** | The on-chain delegation your user signed. It authorises the payment; Haven constructs and relays it. |\n\nNext: [your agent hit a 402](/402.md) \xB7 [everything agent-readable](/llms.txt)\n";
+var HAVEN_AGENT_RUNBOOK_MD = "# Haven for agents \u2014 set your user up to let you pay\n\nYou are an AI agent whose user has no Haven account yet, or has one but has not connected you.\n\n> Links below are paths on this same host: resolve them against the URL you fetched this file from.\n\n## What Haven is, in three sentences\n\nYour 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.\n\n## The sequence\n\nFour 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.\n\n1. **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@<channel> login --api <api-url>` afterwards gets you a scoped session for steps 3-4 (that flag or `HAVEN_API_URL`, on the first command \u2014 the session then remembers the backend; **the CLI's built-in default is Haven's hosted production backend**, so on any other deployment an omitted flag connects you somewhere real and wrong rather than failing) \u2014 they approve a code in the browser, you never hold their password. The `<channel>` in that command is the tag your deployment names \u2014 read it from `/.well-known/haven.json` (`packages.cli.channel`), never a tag you pick. Do not hold the process open while you wait: under `--json`, pass `--no-wait` to get the link object back at once, then poll it with `haven login --poll <device_code>` \u2014 one round per invocation, exit 3 while it is still pending, 0 once approved. It can set up agents and read the account; it cannot sign, approve a budget, move funds, or rotate any agent's keys.\n2. **HUMAN \u2014 fund it.** USDC only, no ETH: Haven sponsors the gas. `/.well-known/haven.json` names `chains.default` as the deployment's expected chain, but after login `haven wallets funding` prints the address, the amount and which chain in one place; confirm that chain before you message your user. Without a CLI session, the dashboard's funding card shows the address and amount and its Receive-funds screen names the chain; never assume one: a testnet deployment and production both call themselves Haven. Before you write that message, read the manifest: `environment` says whether this deployment is `production`, and each `chains.supported` entry says whether that chain is a `testnet`. Real money is at stake only on a non-testnet chain of a `production` deployment \u2014 tell your user which case theirs is.\n3. **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.\n4. **YOU \u2014 run the connector command** in that prompt (below). It makes your signing key locally, registering only the public address.\n5. **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.\n6. **YOU \u2014 verify, then pay.**\n\n## Budget changes later (second token, raise, revoke)\n\nThe first budget rides the setup above. After the agent exists, a CLI session can construct the LATER changes \u2014 a second token, a bigger amount, a recipient pin, a stop \u2014 and hand your user a link; the human still signs, every time:\n\n```\nhaven budget grant <agentId> --amount <n> --token USDC --period <minutes> [--recipient <address>] [--wait]\nhaven budget revoke <agentId> <delegationHash> [--wait]\n```\n\nThe CLI never signs: it prints a dashboard link, your user opens it and signs with their passkey or wallet. `--wait` polls until the human's signature lands. The hash for `revoke` is in `haven agents show <agentId>`.\n\n## Hand-off scripts\n\nSend 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.\n\n**Before signup** (step 1):\n\n> 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`.\n\n**At the passkey step:**\n\n> 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.\n\n**At funding** (step 2):\n\n> Your Haven account needs USDC before I can pay for anything \u2014 USDC only, no ETH: Haven sponsors the gas. Before you send anything, let me get you the exact address **and network** \u2014 `haven wallets funding` prints both, and the funding card on `<host>/dashboard` shows the same. Please do not send to an address or a chain I have not confirmed with you; a small amount first is fine.\n\n**At the budget** (step 3):\n\n> 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.\n\n**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.\n\n> Setup is done on my side. Approve the budget here: <approval.url>. Approve it with your passkey; nothing can be spent until you do.\n\n> 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.\n\n## What you run\n\nThe setup prompt carries a **connector command** shaped like this:\n\n```\nnpx -y @haven_ai/connect@<channel> --setup EXAMPLE-SETUP-TOKEN-NOT-REAL --api <api-url> --ack-local-tools\n```\n\nRun 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.\n\n- 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.\n- 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.\n- 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.\n- 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.\n- Do not print private keys, API keys, credential file contents, or config secrets in chat or logs.\n\nIf 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.\n\n## How to verify\n\nCall `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`:\n\n- `ready` \u2014 a budget is live; you can pay.\n- `needs_approval` \u2014 the connector finished, nobody approved yet. Ask your user again, in their Haven tab; there is no queue to wait in.\n- `revoked` \u2014 the credential is not active; ask your user to create a new agent.\n\n`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.\n\n## If you cannot open a browser\n\nNothing 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.\n\n## Vocabulary\n\n| Term | What it is |\n|---|---|\n| **setup prompt** | The text the dashboard hands your user to paste to you. Carries the command and its rules. |\n| **connector command** | The `npx -y @haven_ai/connect@\u2026` line you run. One-time token, one use. |\n| **agent credential** | Your API key (`sk_agent_\u2026`), written to `~/.haven`. It identifies you; alone it cannot move money. |\n| **delegate key** | Your signing key, made on this machine and never sent anywhere. |\n| **budget** | The on-chain delegation your user signed. It authorises the payment; Haven constructs and relays it. |\n\nNext: [your agent hit a 402](/402.md) \xB7 [everything agent-readable](/llms.txt)\n";
 
 // src/token.ts
 function sessionExpiry(token) {
@@ -591,7 +604,7 @@ async function runConnector(connectorCommand, spawner, onStderr) {
 
 // src/commands.ts
 var DEFAULT_API = "https://havenbackend-production-8a00.up.railway.app";
-var CLI_VERSION = "0.1.35-alpha.0";
+var CLI_VERSION = "0.1.37-alpha.0";
 async function run(argv, deps = {}) {
   const out = deps.out ?? ((l) => process.stdout.write(`${l}
 `));
@@ -717,6 +730,8 @@ async function deviceLogin(args, d, baseUrl) {
       ok: true,
       verification_url: start.verification_url,
       user_code: start.user_code,
+      device_code: start.device_code,
+      interval: start.interval,
       expires_at: new Date(deadline).toISOString()
     },
     () => `Open ${start.verification_url}
@@ -724,11 +739,20 @@ and approve the code ${start.user_code}.
 It expires in ${Math.round(start.expires_in / 60)} minutes.`
   );
   if (args.flags.noWait) return EXIT.ok;
+  const jsonWaitMs = args.flags.json ? 3e4 : start.expires_in * 1e3;
+  const waitUntil = Date.now() + jsonWaitMs;
   let interval = start.interval * 1e3;
   for (; ; ) {
     if (Date.now() >= deadline) {
       throw new HavenCliError("The code expired before it was approved.", EXIT.notAuthenticated);
     }
+    if (Date.now() >= waitUntil) {
+      d.o.data(
+        { status: "pending", device_code: start.device_code, retry_after: Math.round(interval / 1e3) },
+        () => "Still waiting for approval \u2014 run the same command again to keep waiting."
+      );
+      return EXIT.notAuthenticated;
+    }
     await d.sleep(interval);
     let res = null;
     try {
@@ -764,7 +788,55 @@ function deviceErrorCode(err) {
   const body = err?.body;
   return typeof body?.error === "string" ? body.error : null;
 }
+var POLL_RETRY_AFTER_SECONDS = 5;
+async function devicePollOnce(args, d, baseUrl, deviceCode) {
+  const api = d.makeApi(baseUrl);
+  let res = null;
+  try {
+    res = await api.post("/auth/device/token", {
+      device_code: deviceCode
+    });
+  } catch (err) {
+    const code = deviceErrorCode(err);
+    if (code === "authorization_pending") {
+      d.o.data(
+        { status: "pending", device_code: deviceCode, retry_after: POLL_RETRY_AFTER_SECONDS },
+        () => "Not approved yet \u2014 poll again shortly."
+      );
+      return EXIT.notAuthenticated;
+    }
+    if (code === "slow_down") {
+      d.o.data(
+        {
+          status: "pending",
+          device_code: deviceCode,
+          retry_after: POLL_RETRY_AFTER_SECONDS + 5
+        },
+        () => "Polling too fast \u2014 wait a moment longer, then poll again."
+      );
+      return EXIT.notAuthenticated;
+    }
+    if (code === "access_denied") {
+      throw new HavenCliError("The request was denied.", EXIT.refused);
+    }
+    if (code === "expired_token") {
+      throw new HavenCliError("The code expired before it was approved.", EXIT.notAuthenticated);
+    }
+    throw err;
+  }
+  await d.sessionStore.save({ token: res.token, apiBaseUrl: baseUrl, user: res.user });
+  emit(
+    d,
+    args.flags.json,
+    { ok: true, email: res.user.email, expires_at: sessionExpiry(res.token), user: res.user, apiBaseUrl: baseUrl },
+    () => `Signed in as ${res.user.email}.`
+  );
+  return EXIT.ok;
+}
 async function cmdLogin(args, d) {
+  if (args.flags.poll) {
+    return devicePollOnce(args, d, baseUrlFor(args, d, null), args.flags.poll);
+  }
   const email = args.flags.email ?? d.env.HAVEN_EMAIL;
   if (!email) {
     return deviceLogin(args, d, baseUrlFor(args, d, null));
@@ -1244,7 +1316,7 @@ async function cmdActivityExport(args, d) {
   return EXIT.ok;
 }
 function exportType(t) {
-  if (t.activityType === "delegate_sweep") return "allowance funding";
+  if (t.activityType === "delegate_sweep") return "sweep";
   if (t.source === "x402") return "x402";
   if (t.source === "mpp_demo") return "mpp";
   return t.direction === "in" ? "receive" : "send";