pushary 1.8.0 → 1.8.1

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 1.8.1
+
+- The CLI is now also published as `pushary`, from the same build as `@pushary/agent-hooks`, and the commands it prints now show `npx pushary@latest`. `npx @pushary/agent-hooks@latest` keeps working.
+
 ## 1.8.0
 
 - **An approval you give after auto mode blocks a call is no longer lost when the agent rewords the call.** Your approval covers only the exact call that was blocked. Claude Code tells the agent only that it may retry, and an agent that sent a changed command was blocked again, so the approval you gave from your phone or the Mac notch did nothing. Pushary now refuses the first changed call and tells the agent to send the blocked call again unchanged. If the agent ends its turn without sending it, Pushary tells it to send it.

package/README.md

@@ -1,15 +1,15 @@
 # Pushary
 
-[![npm version](https://img.shields.io/npm/v/@pushary/agent-hooks.svg)](https://www.npmjs.com/package/@pushary/agent-hooks)
-[![npm downloads](https://img.shields.io/npm/dm/@pushary/agent-hooks.svg)](https://www.npmjs.com/package/@pushary/agent-hooks)
-[![license](https://img.shields.io/npm/l/@pushary/agent-hooks.svg)](./LICENSE)
+[![npm version](https://img.shields.io/npm/v/pushary.svg)](https://www.npmjs.com/package/pushary)
+[![npm downloads](https://img.shields.io/npm/dm/pushary.svg)](https://www.npmjs.com/package/pushary)
+[![license](https://img.shields.io/npm/l/pushary.svg)](./LICENSE)
 
 Push notifications, questions, and permission approvals for AI agents. Get a push when your agent finishes work, answer its questions from your phone, and approve risky commands before they run. Works with Claude Code, Codex, Cursor, VS Code, OpenCode, Gemini CLI, Hermes, and fx.
 
 Your agent froze waiting for a yes. This is how it reaches you.
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 One command wires up the MCP server, the permission hooks, and the agent instruction files. Then you close your laptop and the agent still reaches you.
@@ -30,7 +30,7 @@ If your agent runs in front of you and you only need to know when it finishes,
 you do not need any of the above and you should not pay for it:
 
 ```bash
-npx @pushary/agent-hooks@latest bell
+npx pushary@latest bell
 ```
 
 That is the whole thing. It makes a noise in your terminal and raises a desktop
@@ -80,7 +80,7 @@ talking. Set `PUSHARY_BELL_QUIET=1` if you would rather it never mentioned it.
 Run setup:
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 It shows a QR code and short link. Open either in the Pushary app, check that the
@@ -91,13 +91,13 @@ pairing.
 For CI or another non-interactive install, pass an existing key explicitly:
 
 ```bash
-npx @pushary/agent-hooks@latest setup --key pk_xxx.sk_xxx --skip-phone
+npx pushary@latest setup --key pk_xxx.sk_xxx --skip-phone
 ```
 
 Verify it worked:
 
 ```bash
-npx @pushary/agent-hooks@latest doctor
+npx pushary@latest doctor
 ```
 
 Setup installs this package globally with npm, at the version you ran, because the
@@ -106,12 +106,20 @@ hooks run from that install. You never install it by hand.
 ## Remove it
 
 ```bash
-npx @pushary/agent-hooks@latest clean
+npx pushary@latest clean
 ```
 
 It removes the hooks, the MCP entries, the stored key and the background service.
 Add `--dry-run` to see what it would remove first.
 
+## One package, two names
+
+`pushary` and `@pushary/agent-hooks` are the same build, published at the same
+version. Every older command keeps working: `npx @pushary/agent-hooks@latest setup`
+does exactly what `npx pushary@latest setup` does.
+
+`pip install pushary` is a different package: the Pushary Python SDK.
+
 ## Supported agents
 
 | Agent | Notify | Ask | Gate |
@@ -227,19 +235,19 @@ defaults rather than waiting for a keypress that can never arrive.
 
 ```bash
 # Everything detected on this machine, no prompts
-npx @pushary/agent-hooks@latest setup --key-stdin --yes --skip-phone < key.txt
+npx pushary@latest setup --key-stdin --yes --skip-phone < key.txt
 
 # Named agents only
-npx @pushary/agent-hooks@latest setup --agents claude_code,codex --yes --skip-phone
+npx pushary@latest setup --agents claude_code,codex --yes --skip-phone
 
 # Store the key and configure nothing
-npx @pushary/agent-hooks@latest setup --agents none --yes
+npx pushary@latest setup --agents none --yes
 
 # Show what would be written, change nothing
-npx @pushary/agent-hooks@latest setup --agents auto --dry-run
+npx pushary@latest setup --agents auto --dry-run
 
 # One machine-readable object on stdout; every human line goes to stderr
-npx @pushary/agent-hooks@latest setup --agents auto --yes --json
+npx pushary@latest setup --agents auto --yes --json
 ```
 
 Prefer `--key-stdin` over `--key` in CI: `--key` puts the secret in argv, where
@@ -252,9 +260,9 @@ that failed), `130` cancelled with Ctrl-C.
 Examples:
 
 ```bash
-npx @pushary/agent-hooks@latest mode push_only --for 30m
-npx @pushary/agent-hooks@latest wait 45
-npx @pushary/agent-hooks@latest clean
+npx pushary@latest mode push_only --for 30m
+npx pushary@latest wait 45
+npx pushary@latest clean
 ```
 
 ## Updates
@@ -266,7 +274,7 @@ already run from, then refreshes each agent's config the way `pushary upgrade` d
 The session does not wait for it, and the new version runs from the next hook call.
 
 - It stays within the same major version. A new major shows in `pushary doctor`, and
-  you move to it with `npx @pushary/agent-hooks@latest upgrade`.
+  you move to it with `npx pushary@latest upgrade`.
 - It only updates a global npm install. A copy run through `npx`, a plugin, or the Mac
   app updates by its own route.
 - It never uses `sudo`. If npm cannot write to the global folder, the attempt is
@@ -323,7 +331,7 @@ MIT
 
 ## Claude Desktop and Cowork
 
-Run `pushary cowork` (or `npx @pushary/agent-hooks@latest cowork`) for connector setup. `pushary setup --agents cowork` opens the same setup path without storing a CLI key or writing hooks. Add the OAuth URL in Claude and sign in with the account used by your Pushary phone/Mac app.
+Run `pushary cowork` (or `npx pushary@latest cowork`) for connector setup. `pushary setup --agents cowork` opens the same setup path without storing a CLI key or writing hooks. Add the OAuth URL in Claude and sign in with the account used by your Pushary phone/Mac app.
 
 Use `pushary cowork --instructions` for standing instructions or `pushary cowork --skill > SKILL.md` to export the bundled skill for upload. `--json` reports `manual_setup_required`; printing a link does not prove a connection. Ask a test question in Claude, answer it in Pushary, and verify Claude receives it.
 

package/data/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pushary
-version: 0.11.1
+version: 0.11.2
 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 service, $9.99/mo after a 3-day card-first trial.
 metadata:
   hermes:
@@ -203,7 +203,7 @@ into the agent configuration files it wires, not into `~/.pushary/config.json`.
 machine the app set up therefore prints `mac-app` and nothing else. Treat it as
 ready.
 
-Check it with `npx @pushary/agent-hooks@latest status --json`. The exit code is the answer:
+Check it with `npx pushary@latest status --json`. The exit code is the answer:
 
 | Code | Meaning |
 | --- | --- |
@@ -214,7 +214,7 @@ Check it with `npx @pushary/agent-hooks@latest status --json`. The exit code is
 | 6 | No device can answer |
 | 8 | Pushary could not be reached |
 
-On 6, the user needs to connect a phone: `npx @pushary/agent-hooks@latest connect`. That adds a phone and rewrites no agent configuration.
+On 6, the user needs to connect a phone: `npx pushary@latest connect`. That adds a phone and rewrites no agent configuration.
 
 If `mac-app` printed, the Mac app is installed here and it may also own the hooks. Read the hook command to know, because the command is the record:
 
@@ -241,7 +241,7 @@ The command line works on macOS too. Offer it if the user prefers the terminal,
 There is no Mac app for these machines. Use the command line. It is fully supported.
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 Node 20.17+, 22.13+ or 23.5+ is necessary. Then the user needs a phone to answer on:
@@ -258,7 +258,7 @@ Run `setup`. It reads the key the app signed in with, so it mints no second key,
 ### What setup does
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+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.
@@ -281,7 +281,7 @@ If `PUSHARY_API_KEY` is already in the environment or in an existing MCP config,
 No app on their phone yet? They can get it at https://pushary.com/download. Or answer through the browser instead:
 
 ```bash
-npx @pushary/agent-hooks@latest setup --connect browser
+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.
@@ -291,7 +291,7 @@ Manual MCP configuration also works, but it needs a key, so the user signs up fi
 After setup, verify with:
 
 ```bash
-npx @pushary/agent-hooks@latest doctor
+npx pushary@latest doctor
 ```
 
 ## Answer surfaces and account boundaries
@@ -303,7 +303,7 @@ npx @pushary/agent-hooks@latest doctor
 | Slack | Answer through buttons, menus or text modals when the integration and intended recipient are configured. |
 | Browser | Open the decision page as a fallback; browser notification delivery requires permission. |
 
-Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx @pushary/agent-hooks@latest doctor`, then request one harmless test question and verify it reaches the intended surface. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
+Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx pushary@latest doctor`, then request one harmless test question and verify it reaches the intended surface. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
 
 Partner customers use scoped enrollment links issued by their application. Do not enroll them into the operator's account or send their decisions through personal tools. The Mac notch currently uses the personal account/session API; do not promise a Partner customer inbox on Mac. See https://pushary.com/docs/agents/embed for Partner setup.
 

package/data/cowork/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pushary-cowork
-version: 0.4.2
+version: 0.4.3
 description: Phone notifications and human-in-the-loop for Claude Cowork through the Pushary connector. Use inside a Cowork session whenever you need a human and nobody is watching the session, 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 task finishes or fails with nobody watching. Also use it when the user says things like ping me on my phone when this is done, ask me before doing anything risky, keep me in the loop while I am away, or notify me if you get stuck. Sends completion alerts, asks questions (yes/no, multiple choice, or free text) via push, and gets answers from connected devices. This Pushary connector is cooperative; it does not install native Cowork permission hooks. Pushary is a hosted service, $9.99/mo after a 3-day card-first trial.
 metadata:
   tags: notifications, push, mcp, human-in-the-loop, cowork, claude, alerts, approvals
@@ -55,7 +55,7 @@ Delivery is controlled by the user's policy: `push_first` uses presence, `push_o
 | Slack | Answer through buttons, menus or text modals when the integration and intended recipient are configured. |
 | Browser | Open the decision page as a fallback; browser notification delivery requires permission. |
 
-Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx @pushary/agent-hooks@latest cowork` for connector setup, then ask one harmless test question inside Cowork, answer it from Pushary, and verify Cowork receives the answer. CLI doctor checks do not verify a hosted connector. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
+Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx pushary@latest cowork` for connector setup, then ask one harmless test question inside Cowork, answer it from Pushary, and verify Cowork receives the answer. CLI doctor checks do not verify a hosted connector. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
 
 Partner customers use scoped enrollment links issued by their application. Do not enroll them into the operator's account or send their decisions through personal tools. The Mac notch currently uses the personal account/session API; do not promise a Partner customer inbox on Mac. See https://pushary.com/docs/agents/embed for Partner setup.
 

package/data/cursor-plugin/README.md

@@ -35,7 +35,7 @@ Open the Marketplace panel in Cursor, search for Pushary, and click install. The
 This also sets up Claude Code, Codex, and Hermes if you use them.
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 ### Option 3: Manual MCP
@@ -94,7 +94,7 @@ Timeout approvals apply only after the configured wait actually elapsed. Short e
 
 ## Development
 
-`skills/pushary/SKILL.md` mirrors the Pushary skill that ships with `@pushary/agent-hooks`. Keep the two the same.
+`skills/pushary/SKILL.md` mirrors the Pushary skill that ships with the Pushary CLI (`pushary` on npm). Keep the two the same.
 
 Test the plugin locally before publishing:
 

package/data/cursor-plugin/scripts/redaction.mjs

@@ -11,12 +11,14 @@ const credentialAssignmentRule = (key, doubleQuoted, singleQuoted, bare) => ({
     replacement: '$1$2$3$4[redacted]$2$3',
 });
 const DISPLAYED_SECRET_SHAPES = {
+    separator: String.raw `[ \t]`,
     privateKeyBody: String.raw `${PEM_LINE_BREAK}?(?:(?:Proc-Type|DEK-Info): [A-Za-z0-9,-]+${PEM_LINE_BREAK})*(?:[A-Za-z0-9+/=\r\n]|\\[rn])*?`,
     urlPassword: `${SHELL_INERT_URL_PASSWORD_UNIT}+`,
     authorizationValue: `${SHELL_INERT_UNIT}+`,
     credentialAssignment: credentialAssignmentRule(DISPLAYED_CREDENTIAL_KEY, `${SHELL_INERT_UNIT}*"`, `${SHELL_INERT_SINGLE_QUOTED_UNIT}*'`, `${SHELL_INERT_UNIT}+`),
 };
 const CUT_OFF_SECRET_SHAPES = {
+    separator: String.raw `\s`,
     privateKeyBody: String.raw `[\s\S]*?`,
     urlPassword: String.raw `[^\s@/]+`,
     authorizationValue: String.raw `\S+`,
@@ -38,8 +40,8 @@ const secretRedactionRules = (shapes) => [
     { pattern: /\bxai-[A-Za-z0-9]{16,}\b/g, replacement: '[redacted]' },
     { pattern: /\beyJ[A-Za-z0-9_-]{8,}\.[A-Za-z0-9_-]{8,}\.[A-Za-z0-9_-]{8,}\b/g, replacement: '[redacted]' },
     { pattern: new RegExp(String.raw `\b([a-z][a-z0-9+.-]*:\/\/[^\s:/@]+:)${shapes.urlPassword}@`, 'gi'), replacement: '$1[redacted]@' },
-    { pattern: /\bbearer\s+[A-Za-z0-9._~+/=-]+/gi, replacement: 'bearer [redacted]' },
-    { pattern: new RegExp(String.raw `\bauthorization:\s*${shapes.authorizationValue}`, 'gi'), replacement: 'authorization: [redacted]' },
+    { pattern: new RegExp(String.raw `\bbearer${shapes.separator}+[A-Za-z0-9._~+/=-]+`, 'gi'), replacement: 'bearer [redacted]' },
+    { pattern: new RegExp(String.raw `\bauthorization:${shapes.separator}*${shapes.authorizationValue}`, 'gi'), replacement: 'authorization: [redacted]' },
     shapes.credentialAssignment,
 ];
 export const SECRET_REDACTION_RULES = secretRedactionRules(DISPLAYED_SECRET_SHAPES);

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

@@ -196,7 +196,7 @@ into the agent configuration files it wires, not into `~/.pushary/config.json`.
 machine the app set up therefore prints `mac-app` and nothing else. Treat it as
 ready.
 
-Check it with `npx @pushary/agent-hooks@latest status --json`. The exit code is the answer:
+Check it with `npx pushary@latest status --json`. The exit code is the answer:
 
 | Code | Meaning |
 | --- | --- |
@@ -207,7 +207,7 @@ Check it with `npx @pushary/agent-hooks@latest status --json`. The exit code is
 | 6 | No device can answer |
 | 8 | Pushary could not be reached |
 
-On 6, the user needs to connect a phone: `npx @pushary/agent-hooks@latest connect`. That adds a phone and rewrites no agent configuration.
+On 6, the user needs to connect a phone: `npx pushary@latest connect`. That adds a phone and rewrites no agent configuration.
 
 If `mac-app` printed, the Mac app is installed here and it may also own the hooks. Read the hook command to know, because the command is the record:
 
@@ -234,7 +234,7 @@ The command line works on macOS too. Offer it if the user prefers the terminal,
 There is no Mac app for these machines. Use the command line. It is fully supported.
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 Node 20.17+, 22.13+ or 23.5+ is necessary. Then the user needs a phone to answer on:
@@ -251,7 +251,7 @@ Run `setup`. It reads the key the app signed in with, so it mints no second key,
 ### What setup does
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+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.
@@ -274,7 +274,7 @@ If `PUSHARY_API_KEY` is already in the environment or in an existing MCP config,
 No app on their phone yet? They can get it at https://pushary.com/download. Or answer through the browser instead:
 
 ```bash
-npx @pushary/agent-hooks@latest setup --connect browser
+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.
@@ -284,7 +284,7 @@ Manual MCP configuration also works, but it needs a key, so the user signs up fi
 After setup, verify with:
 
 ```bash
-npx @pushary/agent-hooks@latest doctor
+npx pushary@latest doctor
 ```
 
 ## Answer surfaces and account boundaries
@@ -296,7 +296,7 @@ npx @pushary/agent-hooks@latest doctor
 | Slack | Answer through buttons, menus or text modals when the integration and intended recipient are configured. |
 | Browser | Open the decision page as a fallback; browser notification delivery requires permission. |
 
-Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx @pushary/agent-hooks@latest doctor`, then request one harmless test question and verify it reaches the intended surface. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
+Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx pushary@latest doctor`, then request one harmless test question and verify it reaches the intended surface. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
 
 Partner customers use scoped enrollment links issued by their application. Do not enroll them into the operator's account or send their decisions through personal tools. The Mac notch currently uses the personal account/session API; do not promise a Partner customer inbox on Mac. See https://pushary.com/docs/agents/embed for Partner setup.
 

package/data/vscode-plugin/README.md

@@ -35,13 +35,13 @@ There are three things.
 This installs the plugin, registers it with VS Code, and links your API key. It also sets up Claude Code, Codex, Cursor, and Hermes if you use them.
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 To configure only VS Code:
 
 ```bash
-npx @pushary/agent-hooks@latest setup --agents vscode
+npx pushary@latest setup --agents vscode
 ```
 
 ### Option 2: Install from source
@@ -106,11 +106,11 @@ This repository uses the `.claude-plugin/plugin.json` layout, which VS Code, Git
 
 The layout is portable; this plugin is not meant to be. `hooks/hooks.json` uses VS Code's flat hook form, and the gate speaks VS Code's tool names, so treat this as a VS Code plugin that happens to sit in a portable folder shape.
 
-Claude Code users are served by `npx @pushary/agent-hooks@latest setup --agents claude_code`, which installs a hook built for Claude Code's own tool names and matcher format. Do not install this directory as a Claude Code plugin as well: at best it duplicates the MCP server, and the two installs would fight over the same approvals.
+Claude Code users are served by `npx pushary@latest setup --agents claude_code`, which installs a hook built for Claude Code's own tool names and matcher format. Do not install this directory as a Claude Code plugin as well: at best it duplicates the MCP server, and the two installs would fight over the same approvals.
 
 ## Development
 
-`skills/pushary/SKILL.md` mirrors the Pushary skill that ships with `@pushary/agent-hooks`. Keep the two the same.
+`skills/pushary/SKILL.md` mirrors the Pushary skill that ships with the Pushary CLI (`pushary` on npm). Keep the two the same.
 
 Test the gate without VS Code:
 

package/data/vscode-plugin/scripts/pushary-gate.mjs

@@ -703,9 +703,9 @@ const main = async () => {
 
   const apiKey = resolveApiKey()
   if (!apiKey) {
-    diag('no API key found (PUSHARY_API_KEY, the plugin .mcp.json, or ~/.pushary/config.json). Run: npx @pushary/agent-hooks@latest setup')
+    diag('no API key found (PUSHARY_API_KEY, the plugin .mcp.json, or ~/.pushary/config.json). Run: npx pushary@latest setup')
     return respond(
-      unresolved(input.tool_name, 'Pushary is not configured: run `npx @pushary/agent-hooks@latest setup` (get a key at https://pushary.com) to route this approval to your phone.')
+      unresolved(input.tool_name, 'Pushary is not configured: run `npx pushary@latest setup` (get a key at https://pushary.com) to route this approval to your phone.')
     )
   }
 

package/data/vscode-plugin/scripts/redaction.mjs

@@ -11,12 +11,14 @@ const credentialAssignmentRule = (key, doubleQuoted, singleQuoted, bare) => ({
     replacement: '$1$2$3$4[redacted]$2$3',
 });
 const DISPLAYED_SECRET_SHAPES = {
+    separator: String.raw `[ \t]`,
     privateKeyBody: String.raw `${PEM_LINE_BREAK}?(?:(?:Proc-Type|DEK-Info): [A-Za-z0-9,-]+${PEM_LINE_BREAK})*(?:[A-Za-z0-9+/=\r\n]|\\[rn])*?`,
     urlPassword: `${SHELL_INERT_URL_PASSWORD_UNIT}+`,
     authorizationValue: `${SHELL_INERT_UNIT}+`,
     credentialAssignment: credentialAssignmentRule(DISPLAYED_CREDENTIAL_KEY, `${SHELL_INERT_UNIT}*"`, `${SHELL_INERT_SINGLE_QUOTED_UNIT}*'`, `${SHELL_INERT_UNIT}+`),
 };
 const CUT_OFF_SECRET_SHAPES = {
+    separator: String.raw `\s`,
     privateKeyBody: String.raw `[\s\S]*?`,
     urlPassword: String.raw `[^\s@/]+`,
     authorizationValue: String.raw `\S+`,
@@ -38,8 +40,8 @@ const secretRedactionRules = (shapes) => [
     { pattern: /\bxai-[A-Za-z0-9]{16,}\b/g, replacement: '[redacted]' },
     { pattern: /\beyJ[A-Za-z0-9_-]{8,}\.[A-Za-z0-9_-]{8,}\.[A-Za-z0-9_-]{8,}\b/g, replacement: '[redacted]' },
     { pattern: new RegExp(String.raw `\b([a-z][a-z0-9+.-]*:\/\/[^\s:/@]+:)${shapes.urlPassword}@`, 'gi'), replacement: '$1[redacted]@' },
-    { pattern: /\bbearer\s+[A-Za-z0-9._~+/=-]+/gi, replacement: 'bearer [redacted]' },
-    { pattern: new RegExp(String.raw `\bauthorization:\s*${shapes.authorizationValue}`, 'gi'), replacement: 'authorization: [redacted]' },
+    { pattern: new RegExp(String.raw `\bbearer${shapes.separator}+[A-Za-z0-9._~+/=-]+`, 'gi'), replacement: 'bearer [redacted]' },
+    { pattern: new RegExp(String.raw `\bauthorization:${shapes.separator}*${shapes.authorizationValue}`, 'gi'), replacement: 'authorization: [redacted]' },
     shapes.credentialAssignment,
 ];
 export const SECRET_REDACTION_RULES = secretRedactionRules(DISPLAYED_SECRET_SHAPES);

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

@@ -196,7 +196,7 @@ into the agent configuration files it wires, not into `~/.pushary/config.json`.
 machine the app set up therefore prints `mac-app` and nothing else. Treat it as
 ready.
 
-Check it with `npx @pushary/agent-hooks@latest status --json`. The exit code is the answer:
+Check it with `npx pushary@latest status --json`. The exit code is the answer:
 
 | Code | Meaning |
 | --- | --- |
@@ -207,7 +207,7 @@ Check it with `npx @pushary/agent-hooks@latest status --json`. The exit code is
 | 6 | No device can answer |
 | 8 | Pushary could not be reached |
 
-On 6, the user needs to connect a phone: `npx @pushary/agent-hooks@latest connect`. That adds a phone and rewrites no agent configuration.
+On 6, the user needs to connect a phone: `npx pushary@latest connect`. That adds a phone and rewrites no agent configuration.
 
 If `mac-app` printed, the Mac app is installed here and it may also own the hooks. Read the hook command to know, because the command is the record:
 
@@ -234,7 +234,7 @@ The command line works on macOS too. Offer it if the user prefers the terminal,
 There is no Mac app for these machines. Use the command line. It is fully supported.
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+npx pushary@latest setup
 ```
 
 Node 20.17+, 22.13+ or 23.5+ is necessary. Then the user needs a phone to answer on:
@@ -251,7 +251,7 @@ Run `setup`. It reads the key the app signed in with, so it mints no second key,
 ### What setup does
 
 ```bash
-npx @pushary/agent-hooks@latest setup
+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.
@@ -274,7 +274,7 @@ If `PUSHARY_API_KEY` is already in the environment or in an existing MCP config,
 No app on their phone yet? They can get it at https://pushary.com/download. Or answer through the browser instead:
 
 ```bash
-npx @pushary/agent-hooks@latest setup --connect browser
+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.
@@ -284,7 +284,7 @@ Manual MCP configuration also works, but it needs a key, so the user signs up fi
 After setup, verify with:
 
 ```bash
-npx @pushary/agent-hooks@latest doctor
+npx pushary@latest doctor
 ```
 
 ## Answer surfaces and account boundaries
@@ -296,7 +296,7 @@ npx @pushary/agent-hooks@latest doctor
 | Slack | Answer through buttons, menus or text modals when the integration and intended recipient are configured. |
 | Browser | Open the decision page as a fallback; browser notification delivery requires permission. |
 
-Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx @pushary/agent-hooks@latest doctor`, then request one harmless test question and verify it reaches the intended surface. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
+Personal setup connects the operator's devices. For a Mac, install from https://pushary.com/download, sign in to the same personal account and connect your agents in the app. Run `npx pushary@latest doctor`, then request one harmless test question and verify it reaches the intended surface. Test phone fallback while away from the Mac; do not infer delivery from a successful API call alone.
 
 Partner customers use scoped enrollment links issued by their application. Do not enroll them into the operator's account or send their decisions through personal tools. The Mac notch currently uses the personal account/session API; do not promise a Partner customer inbox on Mac. See https://pushary.com/docs/agents/embed for Partner setup.
 

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

@@ -1,38 +1,38 @@
 #!/usr/bin/env node
 import {
   handleBell
-} from "../chunk-IPVKH2ST.js";
+} from "../chunk-HMNR7B2F.js";
 import {
   readHookInput
-} from "../chunk-KGDWDSNL.js";
-import "../chunk-JZTHGAPA.js";
+} from "../chunk-FLQPM2GQ.js";
+import "../chunk-6TK4IY3A.js";
 import "../chunk-SGZJ5LYH.js";
-import "../chunk-EYK3GSRH.js";
-import "../chunk-ZVSKMPBZ.js";
-import "../chunk-C2WCPBF7.js";
-import "../chunk-6J2JC2RT.js";
-import "../chunk-WE2J62NC.js";
-import "../chunk-3EVPNIBE.js";
-import "../chunk-OKXS7WDZ.js";
-import "../chunk-MPWXGONV.js";
-import "../chunk-SAXBC4AZ.js";
-import "../chunk-OLQRRFBX.js";
+import "../chunk-GBNQXYN4.js";
+import "../chunk-DLEKCAQL.js";
+import "../chunk-MYHG7PX2.js";
+import "../chunk-OCVVSRDA.js";
+import "../chunk-EIGJYCOE.js";
+import "../chunk-HTEGMMT3.js";
+import "../chunk-HOEB6AKG.js";
+import "../chunk-URNXU3FO.js";
+import "../chunk-UMMCHS6P.js";
+import "../chunk-72WOCX22.js";
 import "../chunk-XHKBHWLX.js";
-import "../chunk-EPCXUP3P.js";
-import "../chunk-CVQYGMSR.js";
+import "../chunk-VFFHQC7W.js";
+import "../chunk-KB2FTO4O.js";
 import "../chunk-POFBE6ZY.js";
 import "../chunk-GMXKITVA.js";
-import "../chunk-P7WQEVWA.js";
-import "../chunk-2OY3ZZ5N.js";
-import "../chunk-LXQ5FBBD.js";
+import "../chunk-TJMAXQ5Q.js";
+import "../chunk-2SLCHCVN.js";
+import "../chunk-4A3UQERT.js";
 import "../chunk-7QLSKOSU.js";
 import "../chunk-KZERVKTD.js";
-import "../chunk-DB3ONZB4.js";
-import "../chunk-A2A2YTMG.js";
+import "../chunk-5Y2DY6X4.js";
+import "../chunk-UPLV5AJF.js";
 import "../chunk-T7E75EKA.js";
-import "../chunk-GPEGOGRJ.js";
-import "../chunk-E4FJTUH4.js";
-import "../chunk-NQTHFF4W.js";
+import "../chunk-ON5JW2HP.js";
+import "../chunk-35X5UDML.js";
+import "../chunk-5YY3IJT4.js";
 
 // bin/pushary-bell-hook.ts
 var main = async () => {

package/dist/bin/pushary-bell.js

@@ -5,37 +5,37 @@ import {
   liveAgentCount,
   ring,
   upgradeThreshold
-} from "../chunk-IPVKH2ST.js";
+} from "../chunk-HMNR7B2F.js";
 import {
   addBellHooks,
   bellInstalled,
   removeBellHooks
-} from "../chunk-OKXS7WDZ.js";
+} from "../chunk-HOEB6AKG.js";
 import {
   createIo
 } from "../chunk-U4TMAANR.js";
 import {
   exitOnHelpFlag
-} from "../chunk-HZVVNGEW.js";
+} from "../chunk-CB23AO4D.js";
 import {
   parseFlags
 } from "../chunk-GMXKITVA.js";
-import "../chunk-P7WQEVWA.js";
+import "../chunk-TJMAXQ5Q.js";
 import "../chunk-7QLSKOSU.js";
 import {
   EXIT
 } from "../chunk-KZERVKTD.js";
-import "../chunk-DB3ONZB4.js";
+import "../chunk-5Y2DY6X4.js";
 import {
   claudeSettings
-} from "../chunk-A2A2YTMG.js";
+} from "../chunk-UPLV5AJF.js";
 import {
   readJsonSafe,
   writeJsonAtomic
 } from "../chunk-T7E75EKA.js";
-import "../chunk-GPEGOGRJ.js";
-import "../chunk-E4FJTUH4.js";
-import "../chunk-NQTHFF4W.js";
+import "../chunk-ON5JW2HP.js";
+import "../chunk-35X5UDML.js";
+import "../chunk-5YY3IJT4.js";
 
 // bin/pushary-bell.ts
 exitOnHelpFlag("bell");