pushary 1.9.41 → 1.9.43

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 1.9.43
+
+- Agent and fx setup guidance uses Pushary’s durable personal reminders, which persist after the agent exits and deliver privately to their creator.
+
+## 1.9.42
+
+- Complete Mac cleanup removes the Partner enrollment and device-key slots introduced by the native Partner flow, alongside existing session state.
+- Bundled agent guidance preserves native Mac setup, explains store-specific checkout terms and returning to the pairing link after installation or restart, and distinguishes a synthetic question test from a real hook approval check.
+
 ## 1.9.41
 
 - Personal Codex sessions reject an invalid question set before asking anything on your phone. Malformed or repeated choices no longer disappear, and ordinary free-text replies, cancellation and host deadlines keep their existing behavior.

package/data/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: pushary
-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.
+version: 0.12.0
+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:
     tags: [notifications, push, human-in-the-loop, alerts, permissions, mcp]
@@ -50,8 +50,12 @@ action.
 
 ## Pricing and Free Alternatives
 
-Pushary is a hosted service. It costs $9.99/mo after a 3-day trial. The trial asks
-for a card up front. Say this plainly when the user asks what Pushary is.
+Pushary is a hosted, paid service. Eligible web signups offer a 3-day trial with
+a card required, then $9.99/mo for the Agent plan. Native app subscriptions use
+the local store price and any eligible intro offer shown in the app. Before
+checkout, tell the user it needs a paid plan and have them review the displayed
+price, trial eligibility and payment method; do not promise web terms inside
+the native app.
 
 Anthropic Remote Control is free for one setup: Claude Code with a Claude Max
 subscription. Recommend it when that is all the user needs.
@@ -302,8 +306,8 @@ It prints a QR, a short link under it, a fingerprint, and then waits about 15 mi
 **Do not summarise that output. Show it, and walk the user through all four steps:**
 
 1. **Show them the QR and the short link.** Both point at the same pairing. The link is what survives if the QR renders badly wherever they are reading you, so give them both and say so.
-2. **They need the Pushary app.** It is the thing that receives approvals. If they do not have it: https://pushary.com/download. Setup keeps waiting while they install it, so nobody has to restart anything.
-3. **They scan the QR, or open the link on the phone.** The app shows a fingerprint. Tell them it must match the one in your output before they approve. On a first install the app will also ask them to sign in and start a plan: $9.99/mo after a 3-day trial, card up front, all inside the app. Say this before they scan rather than letting them discover it mid-flow.
+2. **They need the Pushary app.** It is the thing that receives approvals. If they do not have it: https://pushary.com/download. Setup keeps waiting while they install it. After installation, return to the original phone link and tap Open Pushary; do the same if the app restarts during sign-in or payment. If the code expires, run setup again for a fresh one.
+3. **They scan the QR, or open the link on the phone.** The app shows a fingerprint. Tell them it must match the one in your output before they approve. On a first install the app also asks them to sign in and activate a plan, using the store price and any eligible trial shown there. They review and confirm the payment terms themselves. Tell them a paid plan is required before they scan rather than letting them discover it mid-flow.
 4. **They approve.** Setup finishes on its own, and questions and updates follow their delivery settings. Confirm notifications can offer lock-screen actions; choices and text open the app.
 
 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.
@@ -322,12 +326,18 @@ This is web push, not a login tab. It prints a QR for the user's own subscribe p
 
 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.
 
-After setup, verify with:
+For CLI-owned setup with Node/npm and a CLI credential, explicitly test a synthetic question and answer with:
 
 ```bash
-npx pushary@latest doctor
+npx pushary@latest doctor --roundtrip
 ```
 
+A returned answer proves the question path, not agent hook enforcement. Restart
+the intended agent and follow its real approval check at
+https://pushary.com/docs/agents/supported-agents. For Mac-owned setup, use the
+app's connection tests and ask a harmless question through the current agent;
+do not install Node/npm or infer native readiness from a CLI with no credential.
+
 ## Answer surfaces and account boundaries
 
 | Surface | What the user can do |
@@ -337,7 +347,7 @@ npx pushary@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@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. Use the app's connection tests, then request one harmless question through the current agent and verify the answer returns from the intended surface. Native setup does not need Node/npm. 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.
 
@@ -348,6 +358,12 @@ and every returned field, and it is always current. This section adds only what
 schema cannot say: when to use a tool, what its result means for your next step,
 and the shapes that are easy to get wrong.
 
+### schedule_reminder
+
+When the user asks “remind me later,” set a one-time personal reminder with `body` and either `inMinutes` (from the server clock) or `at` (ISO timestamp with explicit UTC offset or Z). Confirm the returned `fireAt` in their local time. Never guess their timezone. For example, `{"body":"Check the deploy","inMinutes":30}`. Pushary persists it and delivers to the authenticated creator even after the agent exits. It does not schedule agent work.
+
+Call with no arguments to list pending reminders. Pass `cancelReminderId` to cancel a scheduled reminder; `cancelled:false` means it was not cancelled and it may already be dispatching. Limits: 30 days ahead, 25 pending per user/site. Delivery normally follows within about a minute, requires a connected phone, and respects current account access, membership and stop/mute. Test reminders never notify. Do not use `ask_user` for reminders or promise exact delivery time.
+
 ### send_notification
 
 Send a one-way push notification to the user. Optionally include structured context for a rich detail page.

package/data/cowork/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: pushary-cowork
-version: 0.5.0
+version: 0.6.0
 description: Use Pushary in Claude Chat, Cowork, or Claude Code when the user asks for phone updates, a missing decision blocks work, an action needs approval outside existing authorization, or meaningful unattended work finishes or fails. Send task updates and confirm, choice, or text questions to the user's connected devices, then read the returned answer and handoff. Requires the Pushary connector and a paid Pushary account. This skill does not install native permission hooks.
 metadata:
   tags: notifications, push, mcp, human-in-the-loop, cowork, claude, alerts, approvals
@@ -18,6 +18,8 @@ Every question costs the user their attention wherever they are. Before a run of
 
 ## When to reach out
 
+For a personal reminder later, call `schedule_reminder` with `body` and `inMinutes`, or `at` with an explicit UTC offset. Never guess the timezone; confirm the returned time. Pushary saves the reminder and delivers after this conversation ends. It does not reopen Claude or perform future agent work. No arguments lists pending reminders; `cancelReminderId` cancels a scheduled one. Delivery can be about a minute late and requires a connected phone. Do not use `ask_user` for reminders.
+
 - **You need a decision or a clarifying answer.** Call `ask_user` instead of guessing or stalling. Use type `confirm` for yes or no, `select` for a fixed set of options, and `input` for free text.
 - **An action outside your existing authorization is risky or irreversible.** Deleting or overwriting files, spending money, sending anything external, bulk changes: call `ask_user` with type `confirm` first and wait for approval.
 - **Meaningful work finishes while the user is away, or they requested an alert.** Call `send_notification` with a short summary of what changed, and pass `context.type` as `task_complete`. That is what marks it a task update, and the user's setting for where task updates land can only route one that says so. Keep a reply channel open only for a specific unresolved decision needed to finish, as described below.

package/data/cursor-plugin/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "pushary",
   "displayName": "Pushary — Control Panel for AI Agents",
   "description": "Push notifications, human-in-the-loop questions, and permission gating for your AI coding agent. Get a push when a task finishes, answer the agent from your phone, and approve risky commands before they run.",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "author": { "name": "Pushary", "email": "business@pushary.com" },
   "homepage": "https://pushary.com",
   "repository": "https://github.com/Pushary/cursor-plugin",

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

@@ -1,6 +1,6 @@
 ---
 name: pushary
-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.
+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.
 ---
 
 # Pushary - Push Notifications for AI Agents
@@ -43,8 +43,12 @@ action.
 
 ## Pricing and Free Alternatives
 
-Pushary is a hosted service. It costs $9.99/mo after a 3-day trial. The trial asks
-for a card up front. Say this plainly when the user asks what Pushary is.
+Pushary is a hosted, paid service. Eligible web signups offer a 3-day trial with
+a card required, then $9.99/mo for the Agent plan. Native app subscriptions use
+the local store price and any eligible intro offer shown in the app. Before
+checkout, tell the user it needs a paid plan and have them review the displayed
+price, trial eligibility and payment method; do not promise web terms inside
+the native app.
 
 Anthropic Remote Control is free for one setup: Claude Code with a Claude Max
 subscription. Recommend it when that is all the user needs.
@@ -295,8 +299,8 @@ It prints a QR, a short link under it, a fingerprint, and then waits about 15 mi
 **Do not summarise that output. Show it, and walk the user through all four steps:**
 
 1. **Show them the QR and the short link.** Both point at the same pairing. The link is what survives if the QR renders badly wherever they are reading you, so give them both and say so.
-2. **They need the Pushary app.** It is the thing that receives approvals. If they do not have it: https://pushary.com/download. Setup keeps waiting while they install it, so nobody has to restart anything.
-3. **They scan the QR, or open the link on the phone.** The app shows a fingerprint. Tell them it must match the one in your output before they approve. On a first install the app will also ask them to sign in and start a plan: $9.99/mo after a 3-day trial, card up front, all inside the app. Say this before they scan rather than letting them discover it mid-flow.
+2. **They need the Pushary app.** It is the thing that receives approvals. If they do not have it: https://pushary.com/download. Setup keeps waiting while they install it. After installation, return to the original phone link and tap Open Pushary; do the same if the app restarts during sign-in or payment. If the code expires, run setup again for a fresh one.
+3. **They scan the QR, or open the link on the phone.** The app shows a fingerprint. Tell them it must match the one in your output before they approve. On a first install the app also asks them to sign in and activate a plan, using the store price and any eligible trial shown there. They review and confirm the payment terms themselves. Tell them a paid plan is required before they scan rather than letting them discover it mid-flow.
 4. **They approve.** Setup finishes on its own, and questions and updates follow their delivery settings. Confirm notifications can offer lock-screen actions; choices and text open the app.
 
 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.
@@ -315,12 +319,18 @@ This is web push, not a login tab. It prints a QR for the user's own subscribe p
 
 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.
 
-After setup, verify with:
+For CLI-owned setup with Node/npm and a CLI credential, explicitly test a synthetic question and answer with:
 
 ```bash
-npx pushary@latest doctor
+npx pushary@latest doctor --roundtrip
 ```
 
+A returned answer proves the question path, not agent hook enforcement. Restart
+the intended agent and follow its real approval check at
+https://pushary.com/docs/agents/supported-agents. For Mac-owned setup, use the
+app's connection tests and ask a harmless question through the current agent;
+do not install Node/npm or infer native readiness from a CLI with no credential.
+
 ## Answer surfaces and account boundaries
 
 | Surface | What the user can do |
@@ -330,7 +340,7 @@ npx pushary@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@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. Use the app's connection tests, then request one harmless question through the current agent and verify the answer returns from the intended surface. Native setup does not need Node/npm. 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.
 
@@ -341,6 +351,12 @@ and every returned field, and it is always current. This section adds only what
 schema cannot say: when to use a tool, what its result means for your next step,
 and the shapes that are easy to get wrong.
 
+### schedule_reminder
+
+When the user asks “remind me later,” set a one-time personal reminder with `body` and either `inMinutes` (from the server clock) or `at` (ISO timestamp with explicit UTC offset or Z). Confirm the returned `fireAt` in their local time. Never guess their timezone. For example, `{"body":"Check the deploy","inMinutes":30}`. Pushary persists it and delivers to the authenticated creator even after the agent exits. It does not schedule agent work.
+
+Call with no arguments to list pending reminders. Pass `cancelReminderId` to cancel a scheduled reminder; `cancelled:false` means it was not cancelled and it may already be dispatching. Limits: 30 days ahead, 25 pending per user/site. Delivery normally follows within about a minute, requires a connected phone, and respects current account access, membership and stop/mute. Test reminders never notify. Do not use `ask_user` for reminders or promise exact delivery time.
+
 ### send_notification
 
 Send a one-way push notification to the user. Optionally include structured context for a rich detail page.

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

@@ -1,6 +1,6 @@
 ---
 name: pushary
-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.
+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.
 ---
 
 # Pushary - Push Notifications for AI Agents
@@ -43,8 +43,12 @@ action.
 
 ## Pricing and Free Alternatives
 
-Pushary is a hosted service. It costs $9.99/mo after a 3-day trial. The trial asks
-for a card up front. Say this plainly when the user asks what Pushary is.
+Pushary is a hosted, paid service. Eligible web signups offer a 3-day trial with
+a card required, then $9.99/mo for the Agent plan. Native app subscriptions use
+the local store price and any eligible intro offer shown in the app. Before
+checkout, tell the user it needs a paid plan and have them review the displayed
+price, trial eligibility and payment method; do not promise web terms inside
+the native app.
 
 Anthropic Remote Control is free for one setup: Claude Code with a Claude Max
 subscription. Recommend it when that is all the user needs.
@@ -295,8 +299,8 @@ It prints a QR, a short link under it, a fingerprint, and then waits about 15 mi
 **Do not summarise that output. Show it, and walk the user through all four steps:**
 
 1. **Show them the QR and the short link.** Both point at the same pairing. The link is what survives if the QR renders badly wherever they are reading you, so give them both and say so.
-2. **They need the Pushary app.** It is the thing that receives approvals. If they do not have it: https://pushary.com/download. Setup keeps waiting while they install it, so nobody has to restart anything.
-3. **They scan the QR, or open the link on the phone.** The app shows a fingerprint. Tell them it must match the one in your output before they approve. On a first install the app will also ask them to sign in and start a plan: $9.99/mo after a 3-day trial, card up front, all inside the app. Say this before they scan rather than letting them discover it mid-flow.
+2. **They need the Pushary app.** It is the thing that receives approvals. If they do not have it: https://pushary.com/download. Setup keeps waiting while they install it. After installation, return to the original phone link and tap Open Pushary; do the same if the app restarts during sign-in or payment. If the code expires, run setup again for a fresh one.
+3. **They scan the QR, or open the link on the phone.** The app shows a fingerprint. Tell them it must match the one in your output before they approve. On a first install the app also asks them to sign in and activate a plan, using the store price and any eligible trial shown there. They review and confirm the payment terms themselves. Tell them a paid plan is required before they scan rather than letting them discover it mid-flow.
 4. **They approve.** Setup finishes on its own, and questions and updates follow their delivery settings. Confirm notifications can offer lock-screen actions; choices and text open the app.
 
 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.
@@ -315,12 +319,18 @@ This is web push, not a login tab. It prints a QR for the user's own subscribe p
 
 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.
 
-After setup, verify with:
+For CLI-owned setup with Node/npm and a CLI credential, explicitly test a synthetic question and answer with:
 
 ```bash
-npx pushary@latest doctor
+npx pushary@latest doctor --roundtrip
 ```
 
+A returned answer proves the question path, not agent hook enforcement. Restart
+the intended agent and follow its real approval check at
+https://pushary.com/docs/agents/supported-agents. For Mac-owned setup, use the
+app's connection tests and ask a harmless question through the current agent;
+do not install Node/npm or infer native readiness from a CLI with no credential.
+
 ## Answer surfaces and account boundaries
 
 | Surface | What the user can do |
@@ -330,7 +340,7 @@ npx pushary@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@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. Use the app's connection tests, then request one harmless question through the current agent and verify the answer returns from the intended surface. Native setup does not need Node/npm. 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.
 
@@ -341,6 +351,12 @@ and every returned field, and it is always current. This section adds only what
 schema cannot say: when to use a tool, what its result means for your next step,
 and the shapes that are easy to get wrong.
 
+### schedule_reminder
+
+When the user asks “remind me later,” set a one-time personal reminder with `body` and either `inMinutes` (from the server clock) or `at` (ISO timestamp with explicit UTC offset or Z). Confirm the returned `fireAt` in their local time. Never guess their timezone. For example, `{"body":"Check the deploy","inMinutes":30}`. Pushary persists it and delivers to the authenticated creator even after the agent exits. It does not schedule agent work.
+
+Call with no arguments to list pending reminders. Pass `cancelReminderId` to cancel a scheduled reminder; `cancelled:false` means it was not cancelled and it may already be dispatching. Limits: 30 days ahead, 25 pending per user/site. Delivery normally follows within about a minute, requires a connected phone, and respects current account access, membership and stop/mute. Test reminders never notify. Do not use `ask_user` for reminders or promise exact delivery time.
+
 ### send_notification
 
 Send a one-way push notification to the user. Optionally include structured context for a rich detail page.

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

@@ -1,41 +1,41 @@
 #!/usr/bin/env node
 import {
   handleBell
-} from "../chunk-ASXBYX2N.js";
+} from "../chunk-JE6GG3OV.js";
 import {
   readHookInput
-} from "../chunk-6PABNQVH.js";
-import "../chunk-RTM5GVRZ.js";
+} from "../chunk-CIERFMQT.js";
+import "../chunk-S4QT3YFG.js";
 import "../chunk-DWQYCOPI.js";
-import "../chunk-STETTN4K.js";
-import "../chunk-X7TNLYNZ.js";
-import "../chunk-MAB6CGL5.js";
-import "../chunk-QRNNIDGY.js";
+import "../chunk-SCYAXV7U.js";
+import "../chunk-MSUMSXTI.js";
+import "../chunk-J6MVBWF2.js";
+import "../chunk-VQL62ECJ.js";
 import "../chunk-XHKBHWLX.js";
-import "../chunk-IVUP2EE4.js";
-import "../chunk-NRSTNZYJ.js";
-import "../chunk-3U3FU6ZX.js";
-import "../chunk-KYFWYPHN.js";
-import "../chunk-Y3HTWB5S.js";
+import "../chunk-V5SUKRRI.js";
+import "../chunk-PIZ65U3D.js";
+import "../chunk-IMD5FN6Y.js";
+import "../chunk-Q7CUTGT4.js";
+import "../chunk-55FB6OSG.js";
 import "../chunk-GMXKITVA.js";
 import "../chunk-6ICPEJY5.js";
-import "../chunk-M7VKFAAK.js";
-import "../chunk-CGRVIUKE.js";
-import "../chunk-K2SSNAUW.js";
-import "../chunk-I7EZMNKI.js";
+import "../chunk-C3RVRTHS.js";
+import "../chunk-YRE6GUFZ.js";
+import "../chunk-O7ADPLBF.js";
+import "../chunk-4T2TGP4T.js";
 import "../chunk-POFBE6ZY.js";
-import "../chunk-AW4TDBUJ.js";
-import "../chunk-ZV56INA6.js";
-import "../chunk-4UCTKLHY.js";
-import "../chunk-QPT4PTUG.js";
+import "../chunk-53KLSE2F.js";
+import "../chunk-C54VJJ37.js";
+import "../chunk-H6V5S52A.js";
+import "../chunk-W3BO56VE.js";
 import "../chunk-7QLSKOSU.js";
 import "../chunk-KZERVKTD.js";
-import "../chunk-ODPULZZG.js";
-import "../chunk-EBZK2SJ2.js";
+import "../chunk-LAAOHBLO.js";
+import "../chunk-S3OWTQ6Z.js";
 import "../chunk-AQFEP65J.js";
-import "../chunk-CHD6IUNM.js";
-import "../chunk-DIJ532S7.js";
-import "../chunk-ORLTWJ2O.js";
+import "../chunk-GTOBOC6M.js";
+import "../chunk-LDCRV6HG.js";
+import "../chunk-RXXKFM22.js";
 
 // bin/pushary-bell-hook.ts
 var main = async () => {

package/dist/bin/pushary-bell.js

@@ -5,39 +5,39 @@ import {
   liveAgentCount,
   ring,
   upgradeThreshold
-} from "../chunk-ASXBYX2N.js";
+} from "../chunk-JE6GG3OV.js";
 import {
   createIo
 } from "../chunk-FO3MDD26.js";
 import {
   exitOnHelpFlag
-} from "../chunk-F43LAKAK.js";
+} from "../chunk-XLHFWG2E.js";
 import {
   addBellHooks,
   bellInstalled,
   removeBellHooks
-} from "../chunk-Y3HTWB5S.js";
+} from "../chunk-55FB6OSG.js";
 import {
   parseFlags
 } from "../chunk-GMXKITVA.js";
-import "../chunk-M7VKFAAK.js";
+import "../chunk-C3RVRTHS.js";
 import "../chunk-7QLSKOSU.js";
 import {
   EXIT
 } from "../chunk-KZERVKTD.js";
-import "../chunk-ODPULZZG.js";
+import "../chunk-LAAOHBLO.js";
 import {
   claudeSettings
-} from "../chunk-EBZK2SJ2.js";
+} from "../chunk-S3OWTQ6Z.js";
 import {
   readJsonSafe,
   writeJsonAtomic
 } from "../chunk-AQFEP65J.js";
-import "../chunk-CHD6IUNM.js";
-import "../chunk-DIJ532S7.js";
+import "../chunk-GTOBOC6M.js";
+import "../chunk-LDCRV6HG.js";
 import {
   isRecord
-} from "../chunk-ORLTWJ2O.js";
+} from "../chunk-RXXKFM22.js";
 
 // bin/pushary-bell.ts
 exitOnHelpFlag("bell");

package/dist/bin/pushary-claude.js

@@ -8,39 +8,39 @@ import {
   describeIdleWindow,
   startProcessOwnership,
   withSpawnProcessOwnership
-} from "../chunk-4WM7IVVQ.js";
+} from "../chunk-LWW7SBK3.js";
 import {
   announceSubscriptionRequired,
   isDeferAnswer
-} from "../chunk-ZX3PFROQ.js";
+} from "../chunk-ZJXEQV3A.js";
 import {
   claudeTranscriptPath,
   loadSessionKey,
   registerTranscript,
   registeredTranscriptEnabled
-} from "../chunk-RTM5GVRZ.js";
+} from "../chunk-S4QT3YFG.js";
 import "../chunk-DWQYCOPI.js";
 import {
   ensureDaemonRunning
-} from "../chunk-STETTN4K.js";
+} from "../chunk-SCYAXV7U.js";
 import {
   encryptRecord
-} from "../chunk-X7TNLYNZ.js";
-import "../chunk-MAB6CGL5.js";
+} from "../chunk-MSUMSXTI.js";
+import "../chunk-J6MVBWF2.js";
 import {
   transcriptsEnabled
-} from "../chunk-QRNNIDGY.js";
+} from "../chunk-VQL62ECJ.js";
 import {
   needsShell,
   spawnClaude
 } from "../chunk-XHKBHWLX.js";
-import "../chunk-NRSTNZYJ.js";
-import "../chunk-3U3FU6ZX.js";
-import "../chunk-KYFWYPHN.js";
-import "../chunk-Y3HTWB5S.js";
+import "../chunk-PIZ65U3D.js";
+import "../chunk-IMD5FN6Y.js";
+import "../chunk-Q7CUTGT4.js";
+import "../chunk-55FB6OSG.js";
 import "../chunk-GMXKITVA.js";
 import "../chunk-6ICPEJY5.js";
-import "../chunk-M7VKFAAK.js";
+import "../chunk-C3RVRTHS.js";
 import {
   DEFAULT_SESSION,
   UNNAMED_ACTION,
@@ -58,8 +58,8 @@ import {
   reportEvent,
   savePendingCommand,
   scopePathFor
-} from "../chunk-CGRVIUKE.js";
-import "../chunk-K2SSNAUW.js";
+} from "../chunk-YRE6GUFZ.js";
+import "../chunk-O7ADPLBF.js";
 import {
   askUser,
   cancelQuestion,
@@ -70,28 +70,28 @@ import {
   waitForAnswer,
   waitsForThePhone,
   withdrawQuestion
-} from "../chunk-I7EZMNKI.js";
+} from "../chunk-4T2TGP4T.js";
 import "../chunk-POFBE6ZY.js";
 import {
   SubscriptionRequiredError
-} from "../chunk-AW4TDBUJ.js";
-import "../chunk-ZV56INA6.js";
-import "../chunk-4UCTKLHY.js";
+} from "../chunk-53KLSE2F.js";
+import "../chunk-C54VJJ37.js";
+import "../chunk-H6V5S52A.js";
 import {
   getMachineId
-} from "../chunk-QPT4PTUG.js";
+} from "../chunk-W3BO56VE.js";
 import "../chunk-7QLSKOSU.js";
 import "../chunk-KZERVKTD.js";
-import "../chunk-ODPULZZG.js";
-import "../chunk-EBZK2SJ2.js";
+import "../chunk-LAAOHBLO.js";
+import "../chunk-S3OWTQ6Z.js";
 import "../chunk-AQFEP65J.js";
 import {
   getApiKey,
   getBaseUrl
-} from "../chunk-CHD6IUNM.js";
+} from "../chunk-GTOBOC6M.js";
 import {
   NPX_LATEST_COMMAND
-} from "../chunk-DIJ532S7.js";
+} from "../chunk-LDCRV6HG.js";
 import {
   DECISION_STOP_REASON,
   HAND_BACK_WITHOUT_A_PROMPT,
@@ -101,7 +101,7 @@ import {
   redactSecretsFromContent,
   resolveGate,
   timeoutActionWithoutLocalPrompt
-} from "../chunk-ORLTWJ2O.js";
+} from "../chunk-RXXKFM22.js";
 
 // src/wrapper/localPassthrough.ts
 var SIGNAL_NUMBERS = {