pushary 1.9.80 → 1.9.81

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.9.81
+
+- While setup waits for your phone, it no longer suggests `--connect browser`. That sign-in needs a terminal, so an AI agent running setup for you got "No API key" when it followed the hint. The Ctrl+C screen now offers the app download, or a key you already have. `--connect browser` and `--connect web` still work for scripts that use them, and a mistyped `--connect` value now suggests only `app` or `none`.
+- `setup --help` now says what happens without a terminal: setup asks nothing, configures the agents it detects and takes every default. It used to say such runs need `--agents` or `--yes`, which was not true.
+- The bundled Pushary skill tells agents to run setup in the background and show you the link while it waits, and to run `doctor --roundtrip` afterwards, because setup run by an agent sends only a test notification. It also names the approval modes as the app does and says new workspaces start on Always.
+
 ## 1.9.80
 
 - Setup no longer freezes while it installs the Pushary skill through skills.sh. The install takes about as long as before, but the terminal stays responsive, and each agent still gets its own install, so skills.sh records them as before.

package/README.md

@@ -91,7 +91,7 @@ pairing.
 For CI or another non-interactive install, pass an existing key explicitly:
 
 ```bash
-npx pushary@latest setup --key pk_xxx.sk_xxx --skip-phone
+npx pushary@latest setup --key pk_xxx.xxx --skip-phone
 ```
 
 Verify it worked:
@@ -229,9 +229,9 @@ Run `pushary <command> --help` for one command's options.
 
 ### Non-interactive setup
 
-`setup` asks which agents you use, so a run with no terminal on stdin needs to be
-told instead. `--agents` or `--yes` does that; without either, setup takes the
-defaults rather than waiting for a keypress that can never arrive.
+`setup` asks which agents you use at a terminal. With no terminal on stdin it asks
+nothing: it configures the agents it detects and takes every default. Pass
+`--agents` to choose the agents yourself.
 
 ```bash
 # Everything detected on this machine, no prompts

package/data/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pushary
-version: 0.12.0
+version: 0.12.1
 description: Push notifications and human-in-the-loop for AI agents. Use this whenever a running agent needs a human and nobody is at the terminal, such as before an irreversible or destructive action, before spending money, deploying, force-pushing or deleting, when blocked on a decision outside your authority, when running unattended and you hit a genuine ambiguity, when another skill's workflow says to confirm with the user, and when a long task finishes or fails with nobody watching. Also use it when the user says things like keep going and ping me on my phone if you need anything, notify me when my agent needs me, approve from my phone, ask me questions while I am away from the terminal, run this overnight, keep working while I am in a meeting, I am stepping away, do not wait for me, or wants a long task to run unattended. Send alerts when tasks finish or fail, ask questions (yes/no, multiple choice, or free text) via push, and get answers from their connected devices. Use these tools proactively - do not wait for the user to ask for notifications. Every question and answer is recorded, so an unattended run stays reviewable afterwards. Works with Claude Code, Codex, Cursor, VS Code, Windsurf, Hermes, Lovable, or any MCP client; no Claude Max subscription required. Pushary is a hosted, paid service; web and native store checkout have different price and trial terms.
 metadata:
   hermes:
@@ -301,7 +301,9 @@ npx pushary@latest setup
 
 Setup pairs first and configures MCP, hooks, permissions and the skill only once pairing succeeds. Until someone completes the steps below, nothing is written and this machine has no Pushary. Treat pairing as the task, not as a prompt to wait out.
 
-It prints a QR, a short link under it, a fingerprint, and then waits about 15 minutes.
+It prints a QR, a short link, a fingerprint, and then waits about 15 minutes.
+
+**Run it in the background.** Fifteen minutes is longer than a foreground command may run in most agents, and a killed setup kills the pairing code with it. Start setup as a background process that writes to a log, read the link, QR and fingerprint from that log, show them to the user, and keep checking the log until setup exits. Start while the user can still read your messages: until they approve, nothing is configured and you have no other way to reach them.
 
 **Do not summarise that output. Show it, and walk the user through all four steps:**
 
@@ -312,21 +314,15 @@ It prints a QR, a short link under it, a fingerprint, and then waits about 15 mi
 
 Never ask the user for an API key, and never send them to a signup page first. Both are the old flow and both are worse.
 
-If setup exits without pairing, nothing was configured. Say that plainly and offer the two fallbacks below rather than pretending the tools are available.
+If setup exits without pairing, nothing was configured. Say that plainly and offer the fallback below rather than pretending the tools are available.
 
 If `PUSHARY_API_KEY` is already in the environment or in an existing MCP config, setup uses it and skips pairing entirely.
 
-No app on their phone yet? They can get it at https://pushary.com/download. Or answer through the browser instead:
-
-```bash
-npx pushary@latest setup --connect browser
-```
-
-This is web push, not a login tab. It prints a QR for the user's own subscribe page, and it waits for a browser on that page to subscribe. On iOS the user must first add that page to the Home Screen, because iOS sends web push only from an installed page.
+No app on their phone yet? They can get it at https://pushary.com/download while setup keeps waiting. If the code expired, run setup again for a fresh one.
 
 Manual MCP configuration also works, but it needs a key, so the user signs up first at https://pushary.com/sign-up?utm_source=skill&utm_medium=setup and copies the key from the dashboard. Prefer `setup`: it needs neither.
 
-For CLI-owned setup with Node/npm and a CLI credential, explicitly test a synthetic question and answer with:
+When you run setup, it sends only a test notification, because it cannot tell whether the user is there to answer. Right after it finishes, while the user still has their phone in hand, test a synthetic question and answer. For CLI-owned setup with Node/npm and a CLI credential:
 
 ```bash
 npx pushary@latest doctor --roundtrip
@@ -607,14 +603,14 @@ else:
 
 If the user answers in chat before the push response arrives, call `cancel_question` before acting. If it returns `handoffAction: "stop"`, stop. Otherwise, if it returns false, poll once for 1 second and honor any phone answer that won the race.
 
-**How long `ask_user` blocks.** The user sets the delivery mode for their site. You do not set it. The mode decides how long the call waits, and whether it waits at all.
+**How long `ask_user` blocks.** The user sets the delivery mode for their site. You do not set it. The mode decides how long the call waits, and whether it waits at all. New workspaces start on **Always**; the user can pick any of the four in the app.
 
 | Mode | The phone | The call |
 |---|---|---|
-| **When I'm out** (`push_first`, default) | Asked only when the user is away from the terminal and the Mac | Waits for the push-first window. 20 seconds by default. |
-| **Every time** (`push_only`) | Always asked | Waits for the policy timeout. |
-| **Updates** (`notify_only`) | Told, not asked | Returns at once with `answered: false`. Decide in the current client. |
-| **Terminal** (`terminal_only`) | Nothing is sent | Returns at once with `answered: false`. |
+| **When away** (`push_first`) | Asked only when the user is away from the terminal and the Mac | Waits for the push-first window. 20 seconds by default. |
+| **Always** (`push_only`) | Always asked | Waits for the policy timeout. |
+| **Alert only** (`notify_only`) | Told, not asked | Returns at once with `answered: false`. Decide in the current client. |
+| **In agent** (`terminal_only`) | Nothing is sent | Returns at once with `answered: false`. |
 
 Always read `answered`. Never assume the call waited. Pass `timeoutMs` only when you want a shorter wait than the site policy.
 

package/data/cursor-plugin/README.md

@@ -57,7 +57,7 @@ The plugin and CLI installer use the same decision service. Manual MCP-only conf
 The plugin reads your key from the `PUSHARY_API_KEY` environment variable. Get a key at https://pushary.com, then add it to your shell profile:
 
 ```bash
-echo 'export PUSHARY_API_KEY="pk_xxx.sk_xxx"' >> ~/.zshrc
+echo 'export PUSHARY_API_KEY="pk_xxx.xxx"' >> ~/.zshrc
 source ~/.zshrc
 ```
 

package/data/cursor-plugin/skills/pushary/SKILL.md

@@ -294,7 +294,9 @@ npx pushary@latest setup
 
 Setup pairs first and configures MCP, hooks, permissions and the skill only once pairing succeeds. Until someone completes the steps below, nothing is written and this machine has no Pushary. Treat pairing as the task, not as a prompt to wait out.
 
-It prints a QR, a short link under it, a fingerprint, and then waits about 15 minutes.
+It prints a QR, a short link, a fingerprint, and then waits about 15 minutes.
+
+**Run it in the background.** Fifteen minutes is longer than a foreground command may run in most agents, and a killed setup kills the pairing code with it. Start setup as a background process that writes to a log, read the link, QR and fingerprint from that log, show them to the user, and keep checking the log until setup exits. Start while the user can still read your messages: until they approve, nothing is configured and you have no other way to reach them.
 
 **Do not summarise that output. Show it, and walk the user through all four steps:**
 
@@ -305,21 +307,15 @@ It prints a QR, a short link under it, a fingerprint, and then waits about 15 mi
 
 Never ask the user for an API key, and never send them to a signup page first. Both are the old flow and both are worse.
 
-If setup exits without pairing, nothing was configured. Say that plainly and offer the two fallbacks below rather than pretending the tools are available.
+If setup exits without pairing, nothing was configured. Say that plainly and offer the fallback below rather than pretending the tools are available.
 
 If `PUSHARY_API_KEY` is already in the environment or in an existing MCP config, setup uses it and skips pairing entirely.
 
-No app on their phone yet? They can get it at https://pushary.com/download. Or answer through the browser instead:
-
-```bash
-npx pushary@latest setup --connect browser
-```
-
-This is web push, not a login tab. It prints a QR for the user's own subscribe page, and it waits for a browser on that page to subscribe. On iOS the user must first add that page to the Home Screen, because iOS sends web push only from an installed page.
+No app on their phone yet? They can get it at https://pushary.com/download while setup keeps waiting. If the code expired, run setup again for a fresh one.
 
 Manual MCP configuration also works, but it needs a key, so the user signs up first at https://pushary.com/sign-up?utm_source=skill&utm_medium=setup and copies the key from the dashboard. Prefer `setup`: it needs neither.
 
-For CLI-owned setup with Node/npm and a CLI credential, explicitly test a synthetic question and answer with:
+When you run setup, it sends only a test notification, because it cannot tell whether the user is there to answer. Right after it finishes, while the user still has their phone in hand, test a synthetic question and answer. For CLI-owned setup with Node/npm and a CLI credential:
 
 ```bash
 npx pushary@latest doctor --roundtrip
@@ -600,14 +596,14 @@ else:
 
 If the user answers in chat before the push response arrives, call `cancel_question` before acting. If it returns `handoffAction: "stop"`, stop. Otherwise, if it returns false, poll once for 1 second and honor any phone answer that won the race.
 
-**How long `ask_user` blocks.** The user sets the delivery mode for their site. You do not set it. The mode decides how long the call waits, and whether it waits at all.
+**How long `ask_user` blocks.** The user sets the delivery mode for their site. You do not set it. The mode decides how long the call waits, and whether it waits at all. New workspaces start on **Always**; the user can pick any of the four in the app.
 
 | Mode | The phone | The call |
 |---|---|---|
-| **When I'm out** (`push_first`, default) | Asked only when the user is away from the terminal and the Mac | Waits for the push-first window. 20 seconds by default. |
-| **Every time** (`push_only`) | Always asked | Waits for the policy timeout. |
-| **Updates** (`notify_only`) | Told, not asked | Returns at once with `answered: false`. Decide in the current client. |
-| **Terminal** (`terminal_only`) | Nothing is sent | Returns at once with `answered: false`. |
+| **When away** (`push_first`) | Asked only when the user is away from the terminal and the Mac | Waits for the push-first window. 20 seconds by default. |
+| **Always** (`push_only`) | Always asked | Waits for the policy timeout. |
+| **Alert only** (`notify_only`) | Told, not asked | Returns at once with `answered: false`. Decide in the current client. |
+| **In agent** (`terminal_only`) | Nothing is sent | Returns at once with `answered: false`. |
 
 Always read `answered`. Never assume the call waited. Pass `timeoutMs` only when you want a shorter wait than the site policy.
 

package/data/vscode-plugin/README.md

@@ -73,7 +73,7 @@ The source plugin and CLI installer use the same decision service. The Mac app c
 The plugin reads your key from the `PUSHARY_API_KEY` environment variable, falling back to the key `pushary setup` writes to `~/.pushary/config.json`.
 
 ```bash
-echo 'export PUSHARY_API_KEY="pk_xxx.sk_xxx"' >> ~/.zshrc
+echo 'export PUSHARY_API_KEY="pk_xxx.xxx"' >> ~/.zshrc
 source ~/.zshrc
 ```
 

package/data/vscode-plugin/skills/pushary/SKILL.md

@@ -294,7 +294,9 @@ npx pushary@latest setup
 
 Setup pairs first and configures MCP, hooks, permissions and the skill only once pairing succeeds. Until someone completes the steps below, nothing is written and this machine has no Pushary. Treat pairing as the task, not as a prompt to wait out.
 
-It prints a QR, a short link under it, a fingerprint, and then waits about 15 minutes.
+It prints a QR, a short link, a fingerprint, and then waits about 15 minutes.
+
+**Run it in the background.** Fifteen minutes is longer than a foreground command may run in most agents, and a killed setup kills the pairing code with it. Start setup as a background process that writes to a log, read the link, QR and fingerprint from that log, show them to the user, and keep checking the log until setup exits. Start while the user can still read your messages: until they approve, nothing is configured and you have no other way to reach them.
 
 **Do not summarise that output. Show it, and walk the user through all four steps:**
 
@@ -305,21 +307,15 @@ It prints a QR, a short link under it, a fingerprint, and then waits about 15 mi
 
 Never ask the user for an API key, and never send them to a signup page first. Both are the old flow and both are worse.
 
-If setup exits without pairing, nothing was configured. Say that plainly and offer the two fallbacks below rather than pretending the tools are available.
+If setup exits without pairing, nothing was configured. Say that plainly and offer the fallback below rather than pretending the tools are available.
 
 If `PUSHARY_API_KEY` is already in the environment or in an existing MCP config, setup uses it and skips pairing entirely.
 
-No app on their phone yet? They can get it at https://pushary.com/download. Or answer through the browser instead:
-
-```bash
-npx pushary@latest setup --connect browser
-```
-
-This is web push, not a login tab. It prints a QR for the user's own subscribe page, and it waits for a browser on that page to subscribe. On iOS the user must first add that page to the Home Screen, because iOS sends web push only from an installed page.
+No app on their phone yet? They can get it at https://pushary.com/download while setup keeps waiting. If the code expired, run setup again for a fresh one.
 
 Manual MCP configuration also works, but it needs a key, so the user signs up first at https://pushary.com/sign-up?utm_source=skill&utm_medium=setup and copies the key from the dashboard. Prefer `setup`: it needs neither.
 
-For CLI-owned setup with Node/npm and a CLI credential, explicitly test a synthetic question and answer with:
+When you run setup, it sends only a test notification, because it cannot tell whether the user is there to answer. Right after it finishes, while the user still has their phone in hand, test a synthetic question and answer. For CLI-owned setup with Node/npm and a CLI credential:
 
 ```bash
 npx pushary@latest doctor --roundtrip
@@ -600,14 +596,14 @@ else:
 
 If the user answers in chat before the push response arrives, call `cancel_question` before acting. If it returns `handoffAction: "stop"`, stop. Otherwise, if it returns false, poll once for 1 second and honor any phone answer that won the race.
 
-**How long `ask_user` blocks.** The user sets the delivery mode for their site. You do not set it. The mode decides how long the call waits, and whether it waits at all.
+**How long `ask_user` blocks.** The user sets the delivery mode for their site. You do not set it. The mode decides how long the call waits, and whether it waits at all. New workspaces start on **Always**; the user can pick any of the four in the app.
 
 | Mode | The phone | The call |
 |---|---|---|
-| **When I'm out** (`push_first`, default) | Asked only when the user is away from the terminal and the Mac | Waits for the push-first window. 20 seconds by default. |
-| **Every time** (`push_only`) | Always asked | Waits for the policy timeout. |
-| **Updates** (`notify_only`) | Told, not asked | Returns at once with `answered: false`. Decide in the current client. |
-| **Terminal** (`terminal_only`) | Nothing is sent | Returns at once with `answered: false`. |
+| **When away** (`push_first`) | Asked only when the user is away from the terminal and the Mac | Waits for the push-first window. 20 seconds by default. |
+| **Always** (`push_only`) | Always asked | Waits for the policy timeout. |
+| **Alert only** (`notify_only`) | Told, not asked | Returns at once with `answered: false`. Decide in the current client. |
+| **In agent** (`terminal_only`) | Nothing is sent | Returns at once with `answered: false`. |
 
 Always read `answered`. Never assume the call waited. Pass `timeoutMs` only when you want a shorter wait than the site policy.
 

package/dist/{api-FPA2PPXY.js → api-VFUZ5HBR.js}

@@ -17,23 +17,23 @@ import {
   waitForQuestion,
   waitsForThePhone,
   withdrawQuestion
-} from "./chunk-UAADLSK5.js";
+} from "./chunk-IQQQ2LGB.js";
 import "./chunk-POFBE6ZY.js";
-import "./chunk-EUZ73S73.js";
-import "./chunk-S5MRKUSX.js";
-import "./chunk-LK343VAG.js";
-import "./chunk-QBI4KSTQ.js";
-import "./chunk-7QYERUTD.js";
-import "./chunk-IRE7HPNI.js";
-import "./chunk-AFCKBLEG.js";
+import "./chunk-SEVGKJ7K.js";
+import "./chunk-HNUK557P.js";
+import "./chunk-ID46TTYS.js";
+import "./chunk-WPGSQRMW.js";
+import "./chunk-B2HMISVL.js";
+import "./chunk-IS5YVKUX.js";
+import "./chunk-ONUAAXAW.js";
 import "./chunk-PPY5N2E6.js";
 import "./chunk-KZERVKTD.js";
-import "./chunk-35M6YE6T.js";
+import "./chunk-TTTK44RK.js";
 import "./chunk-QTOLNRET.js";
 import {
   DECISION_STOP_REASON,
   UNVERIFIABLE_APPROVAL_REASON
-} from "./chunk-HGCUZQUL.js";
+} from "./chunk-WG67W43Y.js";
 import "./chunk-MLKGABMK.js";
 export {
   ABANDONED_WAIT,

package/dist/bin/pushary-bell-hook.js

@@ -1,41 +1,41 @@
 #!/usr/bin/env node
 import {
   handleBell
-} from "../chunk-OSXIMNMJ.js";
+} from "../chunk-YNWEE2WC.js";
 import {
   readHookInput
-} from "../chunk-3BPSCYOE.js";
-import "../chunk-DN6QYNNC.js";
-import "../chunk-NOQGCGOR.js";
+} from "../chunk-7WCB2BC4.js";
+import "../chunk-BB4W35D6.js";
+import "../chunk-SFUJLUBM.js";
 import "../chunk-MHUKYYYR.js";
-import "../chunk-4OXYED6O.js";
-import "../chunk-FZJON3RK.js";
-import "../chunk-PE6JUMI2.js";
-import "../chunk-ZJGIJDWP.js";
-import "../chunk-DFW2JKHX.js";
+import "../chunk-UUASO2FU.js";
+import "../chunk-TJZIUFWK.js";
+import "../chunk-X772USE7.js";
+import "../chunk-JXE4UQFJ.js";
+import "../chunk-VK2CHU3L.js";
 import "../chunk-NMUI3ZWG.js";
-import "../chunk-XU2FL4B6.js";
+import "../chunk-W3VRQEL3.js";
 import "../chunk-XMSDA5WA.js";
-import "../chunk-WQNHWWVW.js";
+import "../chunk-RVC7OSC7.js";
 import "../chunk-XHKBHWLX.js";
-import "../chunk-3GZRNHH5.js";
-import "../chunk-FNBGGKRK.js";
-import "../chunk-7R5ZKOQ4.js";
-import "../chunk-UAADLSK5.js";
+import "../chunk-3YOXBN7V.js";
+import "../chunk-KXSZ43Z6.js";
+import "../chunk-M5XNFUXN.js";
+import "../chunk-IQQQ2LGB.js";
 import "../chunk-POFBE6ZY.js";
-import "../chunk-EUZ73S73.js";
-import "../chunk-S5MRKUSX.js";
-import "../chunk-LK343VAG.js";
-import "../chunk-QBI4KSTQ.js";
-import "../chunk-GXW43S4A.js";
-import "../chunk-7QYERUTD.js";
-import "../chunk-IRE7HPNI.js";
-import "../chunk-AFCKBLEG.js";
+import "../chunk-SEVGKJ7K.js";
+import "../chunk-HNUK557P.js";
+import "../chunk-ID46TTYS.js";
+import "../chunk-WPGSQRMW.js";
+import "../chunk-NPBPH7KI.js";
+import "../chunk-B2HMISVL.js";
+import "../chunk-IS5YVKUX.js";
+import "../chunk-ONUAAXAW.js";
 import "../chunk-PPY5N2E6.js";
 import "../chunk-KZERVKTD.js";
-import "../chunk-35M6YE6T.js";
+import "../chunk-TTTK44RK.js";
 import "../chunk-QTOLNRET.js";
-import "../chunk-HGCUZQUL.js";
+import "../chunk-WG67W43Y.js";
 import "../chunk-MLKGABMK.js";
 
 // bin/pushary-bell-hook.ts

package/dist/bin/pushary-bell.js

@@ -5,40 +5,40 @@ import {
   liveAgentCount,
   ring,
   upgradeThreshold
-} from "../chunk-OSXIMNMJ.js";
+} from "../chunk-YNWEE2WC.js";
 import {
   createIo
 } from "../chunk-FO3MDD26.js";
 import {
   exitOnHelpFlag
-} from "../chunk-SNQ5HQHE.js";
+} from "../chunk-CRKODLLY.js";
 import {
   addBellHooks,
   bellInstalled,
   removeBellHooks
-} from "../chunk-DFW2JKHX.js";
+} from "../chunk-VK2CHU3L.js";
 import {
   parseFlags
 } from "../chunk-NMUI3ZWG.js";
-import "../chunk-3GZRNHH5.js";
-import "../chunk-GXW43S4A.js";
+import "../chunk-3YOXBN7V.js";
+import "../chunk-NPBPH7KI.js";
 import {
   claudeSettings
-} from "../chunk-7QYERUTD.js";
+} from "../chunk-B2HMISVL.js";
 import {
   readJsonSafe,
   writeJsonAtomic
-} from "../chunk-IRE7HPNI.js";
-import "../chunk-AFCKBLEG.js";
+} from "../chunk-IS5YVKUX.js";
+import "../chunk-ONUAAXAW.js";
 import "../chunk-PPY5N2E6.js";
 import {
   EXIT
 } from "../chunk-KZERVKTD.js";
-import "../chunk-35M6YE6T.js";
+import "../chunk-TTTK44RK.js";
 import "../chunk-QTOLNRET.js";
 import {
   isRecord
-} from "../chunk-HGCUZQUL.js";
+} from "../chunk-WG67W43Y.js";
 import "../chunk-MLKGABMK.js";
 
 // bin/pushary-bell.ts

package/dist/bin/pushary-claude.js

@@ -2,7 +2,7 @@
 import {
   WRAPPER_ACTIVE_ENV,
   findClaudeBinary
-} from "../chunk-4WCPDCKA.js";
+} from "../chunk-FIMSM5SW.js";
 import {
   CommandReceipts,
   controllerCommandSchema
@@ -12,40 +12,40 @@ import {
   describeIdleWindow,
   startProcessOwnership,
   withSpawnProcessOwnership
-} from "../chunk-EU67IKIQ.js";
-import "../chunk-J5BCHHCB.js";
+} from "../chunk-7JU6DPO7.js";
+import "../chunk-QNEWV4JV.js";
 import {
   announceSubscriptionRequired,
   isDeferAnswer
-} from "../chunk-Z4PNECON.js";
+} from "../chunk-ZIJKTWNO.js";
 import {
   claudeTranscriptPath,
   redactDraft,
   registerTranscript,
   registeredTranscriptEnabled,
   startDraftPublisher
-} from "../chunk-DN6QYNNC.js";
-import "../chunk-NOQGCGOR.js";
+} from "../chunk-BB4W35D6.js";
+import "../chunk-SFUJLUBM.js";
 import "../chunk-MHUKYYYR.js";
 import {
   ensureDaemonRunning
-} from "../chunk-FZJON3RK.js";
-import "../chunk-PE6JUMI2.js";
-import "../chunk-ZJGIJDWP.js";
-import "../chunk-DFW2JKHX.js";
+} from "../chunk-TJZIUFWK.js";
+import "../chunk-X772USE7.js";
+import "../chunk-JXE4UQFJ.js";
+import "../chunk-VK2CHU3L.js";
 import "../chunk-NMUI3ZWG.js";
-import "../chunk-XU2FL4B6.js";
+import "../chunk-W3VRQEL3.js";
 import {
   external_exports
 } from "../chunk-XMSDA5WA.js";
 import {
   transcriptsEnabled
-} from "../chunk-WQNHWWVW.js";
+} from "../chunk-RVC7OSC7.js";
 import {
   needsShell,
   spawnClaude
 } from "../chunk-XHKBHWLX.js";
-import "../chunk-3GZRNHH5.js";
+import "../chunk-3YOXBN7V.js";
 import {
   DEFAULT_SESSION,
   UNNAMED_ACTION,
@@ -62,10 +62,10 @@ import {
   reportEvent,
   savePendingCommand,
   scopePathFor
-} from "../chunk-FNBGGKRK.js";
+} from "../chunk-KXSZ43Z6.js";
 import {
   repoKeyFor
-} from "../chunk-7R5ZKOQ4.js";
+} from "../chunk-M5XNFUXN.js";
 import {
   askUser,
   cancelQuestion,
@@ -77,30 +77,30 @@ import {
   waitForAnswer,
   waitsForThePhone,
   withdrawQuestion
-} from "../chunk-UAADLSK5.js";
+} from "../chunk-IQQQ2LGB.js";
 import "../chunk-POFBE6ZY.js";
 import {
   SubscriptionRequiredError
-} from "../chunk-EUZ73S73.js";
-import "../chunk-S5MRKUSX.js";
-import "../chunk-LK343VAG.js";
+} from "../chunk-SEVGKJ7K.js";
+import "../chunk-HNUK557P.js";
+import "../chunk-ID46TTYS.js";
 import {
   getMachineId
-} from "../chunk-QBI4KSTQ.js";
-import "../chunk-GXW43S4A.js";
+} from "../chunk-WPGSQRMW.js";
+import "../chunk-NPBPH7KI.js";
 import {
   claudeConfigDir
-} from "../chunk-7QYERUTD.js";
-import "../chunk-IRE7HPNI.js";
+} from "../chunk-B2HMISVL.js";
+import "../chunk-IS5YVKUX.js";
 import {
   getApiKey,
   getBaseUrl
-} from "../chunk-AFCKBLEG.js";
+} from "../chunk-ONUAAXAW.js";
 import "../chunk-PPY5N2E6.js";
 import "../chunk-KZERVKTD.js";
 import {
   NPX_LATEST_COMMAND
-} from "../chunk-35M6YE6T.js";
+} from "../chunk-TTTK44RK.js";
 import "../chunk-QTOLNRET.js";
 import {
   DECISION_STOP_REASON,
@@ -113,7 +113,7 @@ import {
   refusesWhenUnanswered,
   resolveGate,
   timeoutActionWithoutLocalPrompt
-} from "../chunk-HGCUZQUL.js";
+} from "../chunk-WG67W43Y.js";
 import "../chunk-MLKGABMK.js";
 
 // src/wrapper/localPassthrough.ts