pushary 1.9.86 → 1.9.88

package/dist/{chunk-NFQCFVKJ.js → chunk-Z2LYELNQ.js}

@@ -5,12 +5,12 @@ import {
   hermesAppWiringRecord,
   hermesConfigReceipt,
   hermesSetupReceipt
-} from "./chunk-YLWPJ2MP.js";
+} from "./chunk-NOGDU4XS.js";
 import {
   readJsonSafe,
   resolvePathBinary,
   writeJsonAtomic
-} from "./chunk-5YDIHB67.js";
+} from "./chunk-QOMIFKQL.js";
 import {
   isNewerVersion,
   isReleaseVersion
@@ -1463,7 +1463,7 @@ def record_plugin_load(approval_transport_registered, home=None, pid=None, now=N
         logger.debug("[pushary] could not record the plugin load: %s", exc)
         return None
 ` },
-  { path: "plugin.yaml", contents: "name: pushary\nversion: 0.9.1\ndescription: Push notifications and human-in-the-loop for Hermes Agent via Pushary\nauthor: RalphNex OU\nrequires_env:\n  - name: PUSHARY_API_KEY\n    description: Your Pushary API key\n    url: https://pushary.com/sign-up?from=hermes\n    secret: true\nprovides_tools:\n  - pushary_remind\n  - pushary_notify\n  - pushary_ask\n  - pushary_wait\n  - pushary_cancel\n  - pushary_propose_scope\n  - pushary_enroll\n  - pushary_ask_end_user\nprovides_hooks:\n  - pre_llm_call\n  - pre_tool_call\n  - post_tool_call\n  - on_session_start\n  - on_session_end\n  - on_session_finalize\nprovides_approval_transports:\n  - pushary\n" },
+  { path: "plugin.yaml", contents: "name: pushary\nversion: 0.9.2\ndescription: Push notifications and human-in-the-loop for Hermes Agent via Pushary\nauthor: RalphNex OU\nrequires_env:\n  - name: PUSHARY_API_KEY\n    description: Your Pushary API key\n    url: https://pushary.com/sign-up?from=hermes\n    secret: true\nprovides_tools:\n  - pushary_remind\n  - pushary_notify\n  - pushary_ask\n  - pushary_wait\n  - pushary_cancel\n  - pushary_propose_scope\n  - pushary_enroll\n  - pushary_ask_end_user\nprovides_hooks:\n  - pre_llm_call\n  - pre_tool_call\n  - post_tool_call\n  - on_session_start\n  - on_session_end\n  - on_session_finalize\nprovides_approval_transports:\n  - pushary\n" },
   { path: "schemas.py", contents: `PUSHARY_REMIND = {
     "name": "pushary_remind",
     "description": "Schedule a one-time personal reminder on Pushary, even after Hermes exits. Use body plus in_minutes or at (ISO timestamp with explicit UTC offset, within 30 days). Never guess the user's timezone. Confirm the returned time. No arguments lists pending reminders; cancel_reminder_id cancels a scheduled one. Use Hermes cron for agent work; use this for reminding the operator.",
@@ -1504,7 +1504,7 @@ PUSHARY_NOTIFY = {
             },
             "body": {
                 "type": "string",
-                "description": "Notification body (max 500 chars, aim for under 200)",
+                "description": "Notification body (max 500 chars; the phone shows the first 180)",
             },
             "agent_name": {
                 "type": "string",
@@ -1818,7 +1818,7 @@ PUSHARY_ASK_END_USER = {
     },
 }
 ` },
-  { path: "skills/pushary/SKILL.md", contents: '---\nname: pushary-hermes\nversion: 0.9.0\ndescription: Push notifications and human-in-the-loop for Hermes Agent. Use this whenever a running agent needs a human and no chat session is active, 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. Send alerts when tasks finish, ask questions (yes/no, multiple choice, or free text) via web push, and get answers from their connected devices. Use these tools proactively when the user is not actively in a chat session. Works alongside Hermes\'s built-in messaging platforms (Telegram, Discord, etc.) as a universal fallback channel.\nmetadata:\n  hermes:\n    tags: [notifications, push, human-in-the-loop, alerts, permissions]\n    category: productivity\n    requires_toolsets: []\n    config:\n      - key: PUSHARY_API_KEY\n        description: "Your Pushary API key for push notifications"\n        default: ""\n  tags: notifications, push, mcp, human-in-the-loop, hermes, alerts, permissions\n---\n\n# Pushary - Push Notifications for Hermes Agent\n\nPushary adds mobile, Mac and browser delivery for Hermes. Use it when the user is not actively monitoring a chat platform, or when you need to reach them on their phone\'s lock screen for a time-sensitive decision.\n\n## Ask in as Few Interruptions as Possible\n\nHonor authorization already granted in this session. Ask only for a missing decision or an action outside that authorization, or when an enforced host policy requires it. A multi-step task alone does not require plan approval. Never ask again merely because the next authorized step deletes, deploys or publishes something. These skills guide the agent; supported hooks and runtime approval gates enforce policy. Do not bypass an enforced gate.\n\nEvery question costs the user their attention wherever they are. Before a run of more than a step or two, work out where you will need a human and fold those points together: one `select` carrying the real options beats three `confirm`s in a row, ask once at a boundary rather than once per instance, and never ask what you can determine yourself from the task or from a tool call you can make.\n\n## When to Use Pushary vs Hermes Platforms\n\n**Use Pushary when:**\n- The user has no active chat session (Telegram, Discord, etc.)\n- You need to reach the user\'s phone lock screen for a quick decision\n- A background task finishes and the user may have walked away\n- Permission escalation - a dangerous command needs approval\n- Another skill\'s workflow says to confirm with the user, and no chat session is active to confirm in\n- The user explicitly asked for push notifications\n\n**Use the active Hermes platform when:**\n- The user is currently in a Telegram/Discord/Slack conversation with you\n- The question is part of an ongoing dialog\n- The user prefers responses in their current platform\n\nUse an extra push only when the user requested it or a meaningful unattended result needs attention. Do not assume you can detect whether a Telegram or Discord message was read.\n\n## Setup\n\nOn a Mac, the Pushary app connects Hermes: it puts this plugin in `~/.hermes/plugins/pushary` and selects Pushary as the approval transport. On any computer, `npx pushary@latest setup --agents hermes` does the same. The plugin can also come from the Hermes catalog with `hermes plugins install pushary`. Never install a second copy over one that is already there. No MCP server configuration is needed. Keep credentials out of chat and verify the paired account and device.\n\nIf the `pushary_*` tools are missing from a Hermes session, the plugin did not load. Do not pip-install it into Hermes\'s Python: current Hermes does not load packages added that way. Ask the user to open the Pushary app and repair Hermes, or to run `npx pushary@latest setup --agents hermes`. Then they restart Hermes with `hermes gateway restart`.\n\n## Approvals Go to the Phone\n\nThe plugin registers `pushary` as a Hermes **approval transport**, so the dangerous-command approvals Hermes already asks for open in the app with the same four choices the terminal offers: allow once, allow for this session, always allow, deny. Hermes owns the timeout (300 seconds by default) and remembers session and always decisions exactly as it would have.\n\n```yaml\nsecurity:\n  approval:\n    transport: pushary\n    transport_fallback: builtin\n```\n\nHermes denies by default when Pushary is unreachable. Only an operator who sets `transport_fallback: builtin` enables its built-in prompt after a safe local handoff; cancellation or an unverifiable withdrawal still stops the action. You do not call this yourself; it fires when Hermes decides a command needs a human.\n\n## Answer surfaces and account boundaries\n\n| Surface | What the user can do |\n| --- | --- |\n| Mobile app | Answer confirm, select and input questions. Supported confirm notifications offer approve/deny actions on the lock screen; arbitrary choices and text open the app. |\n| Mac notch | Answer personal account questions with confirm, select, input and question-set controls, including keyboard controls. Presence and delivery policy determine when the phone is also reached. |\n| Slack | Answer through buttons, menus or text modals when the integration and intended recipient are configured. |\n| Browser | Open the decision page as a fallback; browser notification delivery requires permission. |\n\nPersonal setup connects the operator\'s devices. For a Mac, the operator installs from https://pushary.com/download, signs in to the same personal account and connects their agents in the app. 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.\n\nPartner 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.\n\n## Tools\n\nTool names below are the native plugin names. An MCP client without the plugin sees the same capabilities as `send_notification`, `schedule_reminder`, `ask_user`, `wait_for_answer`, `cancel_question`, and `propose_scope`.\n\n### pushary_remind\n\nFor personal reminders later, use `pushary_remind` with `body` and `in_minutes`, or `at` with an explicit UTC offset. Never guess the timezone; confirm the returned time. Pushary saves it and delivers after Hermes exits. Use Hermes cron for future agent work. No arguments lists pending reminders; `cancel_reminder_id` cancels a scheduled one. One-time only, up to 30 days ahead, and delivery can be about a minute late. A connected phone is required. Do not use `pushary_ask` for reminders.\n\n### pushary_notify\n\n\nSend a one-way push notification. Optionally include structured context for a rich detail page.\n\n**Parameters:**\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| title | string | Yes | Notification title (max 100 chars, aim for under 60) |\n| body | string | Yes | Notification body (max 500 chars, aim for under 200) |\n| agent_name | string | No | Identifies this Hermes instance (e.g., "Hermes - daily-briefing") |\n| context_type | "task_complete" / "error" / "info" | Yes for task updates | Marks the notification for task-update routing. |\n| summary | string | No | Short summary of the result. |\n| details / files_changed | string[] | No | Result details or changed paths. |\n| error_message / next_steps | string | No | Error or suggested follow-up. |\n\n**Example - cron task completed:**\n\n```json\n{\n  "title": "Daily briefing ready",\n  "body": "Compiled 12 news items and 3 calendar events",\n  "agent_name": "Hermes - daily-briefing",\n  "context_type": "task_complete",\n  "summary": "Morning briefing compiled from RSS feeds and Google Calendar",\n  "details": ["12 tech news items", "3 meetings today", "2 PRs awaiting review"],\n  "next_steps": "Say \'read briefing\' in Telegram to hear the full summary"\n}\n```\n\n### pushary_ask\n\nAsk a question via push notification and **wait for the answer** (blocks by default). Three question types: confirm (yes/no), select (multiple choice), input (free text).\n\n**Parameters:**\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| question | string | Yes | The complete question (max 8000 chars; notifications show a short preview) |\n| type | "confirm" / "select" / "input" | No | Question type (default: confirm) |\n| options | string[] | No | Choices for select type (2-6 options) |\n| placeholder | string | No | Placeholder text for input type |\n| context | string | No | What you\'re working on, shown above the question |\n| agent_name | string | No | Identifies this Hermes instance |\n| wait | boolean | No | Wait for answer before returning (default: true) |\n| timeout_ms | integer | No | Max wait in ms (max 55000). Defaults to 30000 per poll attempt; server policy may hand off earlier. |\n\n**Returns:**\n- `{ "answered": true, "value": "yes" }` - user responded\n- `{ "answered": false, "timedOut": true }` - no response within timeout\n\n**Example - dangerous command approval:**\n\n```json\n{\n  "question": "Allow: rm -rf /tmp/build-artifacts/*",\n  "type": "confirm",\n  "context": "Cleaning up 2.3GB of stale build artifacts from last week",\n  "agent_name": "Hermes - server-maintenance",\n  "timeout_ms": 12000\n}\n```\n\n### pushary_wait\n\nPoll once for a response when `pushary_ask` was called with `wait: false`. Not needed with default blocking mode.\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| correlation_id | string | Yes | The correlationId from pushary_ask |\n| timeout_ms | integer | No | How long to wait (default 30000, max 55000) |\n\n### pushary_cancel\n\nCancel a pending question that\'s no longer relevant.\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| correlation_id | string | Yes | The correlationId to cancel |\n\n### pushary_propose_scope\n\nAgree the boundary of a multi-step run in one tap, before doing the work, instead of asking file by file. Use it once when a boundary needs agreement or the user requests an enforced scope. Skip a redundant proposal for already authorized work.\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| done_when | string | Yes | What "finished" means for this run |\n| allowed_paths | string[] | No | Globs you intend to change, e.g. `["src/**"]` |\n| off_limits_paths | string[] | No | Globs you promise not to touch; these win on overlap |\n| promises | string[] | No | Boundaries that are not file paths: recipients, channels, spend, systems you will not open |\n| agent_name | string | No | Identifies this Hermes instance |\n\nOnly file paths are enforced, and only on tool calls that carry one. Shell commands, reads, web requests and MCP tools carry no path, so the contract says nothing about them. A run that changes no files belongs in `promises`, which is shown to the user and recorded but never checked. A word that is not a path in `allowed_paths` matches no file and makes every change ask instead.\n\nRead `enforces` in the result. An empty list means nothing here is checked automatically, and you must say so rather than report that a scope is in force.\n\nReturns `ratified: true` only on an explicit yes. Anything else means proceed as if no scope was agreed; do not describe it as ratified.\n\n## Human-in-the-Loop Flow\n\n`pushary_ask` performs its initial wait and at most one server-directed poll within that tool call. If the returned status is still pending, continue with `pushary_wait` and the same correlationId. With `wait: false`, start that polling yourself. Follow an explicit handoff instead when one is returned.\n\nRead `answered`, `status` and `handoffAction` (falling back to `nextAction`) on every response. Only `pending` is live; expired, cancelled, missing and unavailable are not new timeouts. Keep waiting with the same correlationId while pending. A poll ending does not expire the question; never cancel just because a poll returned without an answer. Before moving a live question to the current chat, cancel it. If cancellation says `stop`, stop; if it loses a race, poll once for one second and honor the winning answer. Silence is never consent. A select or input value containing \u201Cyes\u201D is answer data, not approval of a separate action.\n\nDelivery is controlled by the user\'s policy: `push_first` uses presence, `push_only` requests push every time, `notify_only` leaves the decision in the current client, and `terminal_only` avoids push. Do not override the mode or duplicate a question on every surface. The runtime owns delivery, expiry and settlement; do not claim that a reply can restart an ended agent turn.\n\nEach call returns an answer, a pending wait, or an explicit handoff:\n\n```\nresult = pushary_ask({\n  question: "Deploy the updated config to production?",\n  type: "confirm",\n  context: "nginx config updated with new rate limits",\n  tool_name: "terminal",\n  tool_target: "systemctl reload",\n  agent_name: "Hermes - devops"\n})\n\nif result.answered:\n    if result.value == "yes":\n        // proceed with deployment\n    else:\n        // abort and notify via active platform\nelse:\n    // follow handoffAction when present, otherwise nextAction\n```\n\nPass `tool_name` and `tool_target` whenever the question is about a specific operation. They are what let the user turn a repeated approval into a standing rule, and what group the decision in their ledger.\n\n## Identifying Your Instance\n\nAlways pass `agent_name` so the user knows which Hermes profile or task is asking.\n\n**Format:** `"Hermes - {profile or task}"`\n\n**Examples:**\n- `"Hermes - daily-briefing"`\n- `"Hermes - server-maintenance"`\n- `"Hermes - code-review"`\n- `"Hermes - personal-assistant"`\n\n## Notification Etiquette\n\n- **Titles under 60 characters.** Phone lock screens truncate aggressively.\n- **Bodies under 200 characters.** Use the flat `summary`, `details` and `next_steps` fields.\n- **Max 3 push notifications per task.** If the user is in an active chat, prefer that channel.\n- **Don\'t duplicate.** If you already sent the message via Telegram/Discord, send another push only if requested or needed for an unattended result.\n' },
+  { path: "skills/pushary/SKILL.md", contents: '---\nname: pushary-hermes\nversion: 0.9.1\ndescription: Push notifications and human-in-the-loop for Hermes Agent. Use this whenever a running agent needs a human and no chat session is active, 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. Send alerts when tasks finish, ask questions (yes/no, multiple choice, or free text) via web push, and get answers from their connected devices. Use these tools proactively when the user is not actively in a chat session. Works alongside Hermes\'s built-in messaging platforms (Telegram, Discord, etc.) as a universal fallback channel.\nmetadata:\n  hermes:\n    tags: [notifications, push, human-in-the-loop, alerts, permissions]\n    category: productivity\n    requires_toolsets: []\n    config:\n      - key: PUSHARY_API_KEY\n        description: "Your Pushary API key for push notifications"\n        default: ""\n  tags: notifications, push, mcp, human-in-the-loop, hermes, alerts, permissions\n---\n\n# Pushary - Push Notifications for Hermes Agent\n\nPushary adds mobile, Mac and browser delivery for Hermes. Use it when the user is not actively monitoring a chat platform, or when you need to reach them on their phone\'s lock screen for a time-sensitive decision.\n\n## Ask in as Few Interruptions as Possible\n\nHonor authorization already granted in this session. Ask only for a missing decision or an action outside that authorization, or when an enforced host policy requires it. A multi-step task alone does not require plan approval. Never ask again merely because the next authorized step deletes, deploys or publishes something. These skills guide the agent; supported hooks and runtime approval gates enforce policy. Do not bypass an enforced gate.\n\nEvery question costs the user their attention wherever they are. Before a run of more than a step or two, work out where you will need a human and fold those points together: one `select` carrying the real options beats three `confirm`s in a row, ask once at a boundary rather than once per instance, and never ask what you can determine yourself from the task or from a tool call you can make.\n\n## When to Use Pushary vs Hermes Platforms\n\n**Use Pushary when:**\n- The user has no active chat session (Telegram, Discord, etc.)\n- You need to reach the user\'s phone lock screen for a quick decision\n- A background task finishes and the user may have walked away\n- Permission escalation - a dangerous command needs approval\n- Another skill\'s workflow says to confirm with the user, and no chat session is active to confirm in\n- The user explicitly asked for push notifications\n\n**Use the active Hermes platform when:**\n- The user is currently in a Telegram/Discord/Slack conversation with you\n- The question is part of an ongoing dialog\n- The user prefers responses in their current platform\n\nUse an extra push only when the user requested it or a meaningful unattended result needs attention. Do not assume you can detect whether a Telegram or Discord message was read.\n\n## Setup\n\nOn a Mac, the Pushary app connects Hermes: it puts this plugin in `~/.hermes/plugins/pushary` and selects Pushary as the approval transport. On any computer, `npx pushary@latest setup --agents hermes` does the same. The plugin can also come from the Hermes catalog with `hermes plugins install pushary`. Never install a second copy over one that is already there. No MCP server configuration is needed. Keep credentials out of chat and verify the paired account and device.\n\nIf the `pushary_*` tools are missing from a Hermes session, the plugin did not load. Do not pip-install it into Hermes\'s Python: current Hermes does not load packages added that way. Ask the user to open the Pushary app and repair Hermes, or to run `npx pushary@latest setup --agents hermes`. Then they restart Hermes with `hermes gateway restart`.\n\n## Approvals Go to the Phone\n\nThe plugin registers `pushary` as a Hermes **approval transport**, so the dangerous-command approvals Hermes already asks for open in the app with the same four choices the terminal offers: allow once, allow for this session, always allow, deny. Hermes owns the timeout (300 seconds by default) and remembers session and always decisions exactly as it would have.\n\n```yaml\nsecurity:\n  approval:\n    transport: pushary\n    transport_fallback: builtin\n```\n\nHermes denies by default when Pushary is unreachable. Only an operator who sets `transport_fallback: builtin` enables its built-in prompt after a safe local handoff; cancellation or an unverifiable withdrawal still stops the action. You do not call this yourself; it fires when Hermes decides a command needs a human.\n\n## Answer surfaces and account boundaries\n\n| Surface | What the user can do |\n| --- | --- |\n| Mobile app | Answer confirm, select and input questions. Supported confirm notifications offer approve/deny actions on the lock screen; arbitrary choices and text open the app. |\n| Mac notch | Answer confirm, select, input and question-set questions, including keyboard controls. Presence and delivery policy determine when the phone is also reached. |\n| Slack | Answer through buttons, menus or text modals when the integration and intended recipient are configured. |\n| Browser | Open the decision page as a fallback; browser notification delivery requires permission. |\n\nPersonal setup connects the operator\'s devices. For a Mac, the operator installs from https://pushary.com/download, signs in to the same personal account and connects their agents in the app. 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.\n\nPartner 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. They answer on their enrolled phone, and in the Mac notch once they connect the Mac from the phone app. See https://pushary.com/docs/agents/embed for Partner setup.\n\n## Tools\n\nTool names below are the native plugin names. An MCP client without the plugin sees the same capabilities as `send_notification`, `schedule_reminder`, `ask_user`, `wait_for_answer`, `cancel_question`, and `propose_scope`.\n\n### pushary_remind\n\nFor personal reminders later, use `pushary_remind` with `body` and `in_minutes`, or `at` with an explicit UTC offset. Never guess the timezone; confirm the returned time. Pushary saves it and delivers after Hermes exits. Use Hermes cron for future agent work. No arguments lists pending reminders; `cancel_reminder_id` cancels a scheduled one. One-time only, up to 30 days ahead, and delivery can be about a minute late. It goes to the phone and the Pushary Mac app; with no phone connected, only to the Mac app if they have one. Tell the user any `warning`. Do not use `pushary_ask` for reminders.\n\n### pushary_notify\n\n\nSend a one-way push notification. Optionally include structured context for a rich detail page.\n\n**Parameters:**\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| title | string | Yes | Notification title (max 100 chars, aim for under 60) |\n| body | string | Yes | Notification body (max 500 chars; the phone shows the first 180) |\n| agent_name | string | No | Identifies this Hermes instance (e.g., "Hermes - daily-briefing") |\n| context_type | "task_complete" / "error" / "info" | Yes for task updates | Marks the notification for task-update routing. |\n| summary | string | No | Short summary of the result. |\n| details / files_changed | string[] | No | Result details or changed paths. |\n| error_message / next_steps | string | No | Error or suggested follow-up. |\n\n**Example - cron task completed:**\n\n```json\n{\n  "title": "Daily briefing ready",\n  "body": "Compiled 12 news items and 3 calendar events",\n  "agent_name": "Hermes - daily-briefing",\n  "context_type": "task_complete",\n  "summary": "Morning briefing compiled from RSS feeds and Google Calendar",\n  "details": ["12 tech news items", "3 meetings today", "2 PRs awaiting review"],\n  "next_steps": "Say \'read briefing\' in Telegram to hear the full summary"\n}\n```\n\n### pushary_ask\n\nAsk a question via push notification and **wait for the answer** (blocks by default). Three question types: confirm (yes/no), select (multiple choice), input (free text).\n\n**Parameters:**\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| question | string | Yes | The complete question (max 8000 chars; notifications show a short preview) |\n| type | "confirm" / "select" / "input" | No | Question type (default: confirm) |\n| options | string[] | No | Choices for select type (2-6 options) |\n| placeholder | string | No | Placeholder text for input type |\n| context | string | No | What you\'re working on, shown above the question |\n| agent_name | string | No | Identifies this Hermes instance |\n| wait | boolean | No | Wait for answer before returning (default: true) |\n| timeout_ms | integer | No | Max wait in ms (max 55000). Defaults to 30000 per poll attempt; server policy may hand off earlier. |\n\n**Returns:**\n- `{ "answered": true, "value": "yes" }` - user responded\n- `{ "answered": false, "timedOut": true }` - no response within timeout\n\n**Example - dangerous command approval:**\n\n```json\n{\n  "question": "Allow: rm -rf /tmp/build-artifacts/*",\n  "type": "confirm",\n  "context": "Cleaning up 2.3GB of stale build artifacts from last week",\n  "agent_name": "Hermes - server-maintenance",\n  "timeout_ms": 12000\n}\n```\n\n### pushary_wait\n\nPoll once for a response when `pushary_ask` was called with `wait: false`. Not needed with default blocking mode.\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| correlation_id | string | Yes | The correlationId from pushary_ask |\n| timeout_ms | integer | No | How long to wait (default 30000, max 55000) |\n\n### pushary_cancel\n\nCancel a pending question that\'s no longer relevant.\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| correlation_id | string | Yes | The correlationId to cancel |\n\n### pushary_propose_scope\n\nAgree the boundary of a multi-step run in one tap, before doing the work, instead of asking file by file. Use it once when a boundary needs agreement or the user requests an enforced scope. Skip a redundant proposal for already authorized work.\n\n| Name | Type | Required | Description |\n|------|------|----------|-------------|\n| done_when | string | Yes | What "finished" means for this run |\n| allowed_paths | string[] | No | Globs you intend to change, e.g. `["src/**"]` |\n| off_limits_paths | string[] | No | Globs you promise not to touch; these win on overlap |\n| promises | string[] | No | Boundaries that are not file paths: recipients, channels, spend, systems you will not open |\n| agent_name | string | No | Identifies this Hermes instance |\n\nOnly file paths are enforced, and only on tool calls that carry one. Shell commands, reads, web requests and MCP tools carry no path, so the contract says nothing about them. A run that changes no files belongs in `promises`, which is shown to the user and recorded but never checked. A word that is not a path in `allowed_paths` matches no file and makes every change ask instead.\n\nRead `enforces` in the result. An empty list means nothing here is checked automatically, and you must say so rather than report that a scope is in force.\n\nReturns `ratified: true` only on an explicit yes. Anything else means proceed as if no scope was agreed; do not describe it as ratified.\n\n## Human-in-the-Loop Flow\n\n`pushary_ask` performs its initial wait and at most one server-directed poll within that tool call. If the returned status is still pending, continue with `pushary_wait` and the same correlationId. With `wait: false`, start that polling yourself. Follow an explicit handoff instead when one is returned.\n\nRead `answered`, `status` and `handoffAction` (falling back to `nextAction`) on every response. Only `pending` is live; expired, cancelled, missing and unavailable are not new timeouts. Keep waiting with the same correlationId while pending. A poll ending does not expire the question; never cancel just because a poll returned without an answer. Before moving a live question to the current chat, cancel it. If cancellation says `stop`, stop; if it loses a race, poll once for one second and honor the winning answer. Silence is never consent. A select or input value containing \u201Cyes\u201D is answer data, not approval of a separate action.\n\nDelivery is controlled by the user\'s policy: `push_first` (When away) still sends your questions to the phone and lets only hook approvals skip it while the user is at the computer, `push_only` requests push every time, `notify_only` leaves the decision in the current client, and `terminal_only` avoids push. Do not override the mode or duplicate a question on every surface. The runtime owns delivery, expiry and settlement; do not claim that a reply can restart an ended agent turn.\n\nEach call returns an answer, a pending wait, or an explicit handoff:\n\n```\nresult = pushary_ask({\n  question: "Deploy the updated config to production?",\n  type: "confirm",\n  context: "nginx config updated with new rate limits",\n  tool_name: "terminal",\n  tool_target: "systemctl reload",\n  agent_name: "Hermes - devops"\n})\n\nif result.answered:\n    if result.value == "yes":\n        // proceed with deployment\n    else:\n        // abort and notify via active platform\nelse:\n    // follow handoffAction when present, otherwise nextAction\n```\n\nPass `tool_name` and `tool_target` whenever the question is about a specific operation. They are what let the user turn a repeated approval into a standing rule, and what group the decision in their ledger.\n\n## Identifying Your Instance\n\nAlways pass `agent_name` so the user knows which Hermes profile or task is asking.\n\n**Format:** `"Hermes - {profile or task}"`\n\n**Examples:**\n- `"Hermes - daily-briefing"`\n- `"Hermes - server-maintenance"`\n- `"Hermes - code-review"`\n- `"Hermes - personal-assistant"`\n\n## Notification Etiquette\n\n- **Titles under 60 characters.** Phone lock screens truncate aggressively.\n- **Bodies under 180 characters,** where the phone cuts them. Use the flat `summary`, `details` and `next_steps` fields.\n- **Max 3 push notifications per task.** If the user is in an active chat, prefer that channel.\n- **Don\'t duplicate.** If you already sent the message via Telegram/Discord, send another push only if requested or needed for an unattended result.\n' },
   { path: "tools.py", contents: `import json
 import time
 import uuid

package/dist/{chunk-2CJNGJQS.js → chunk-ZEPS4KIK.js}

@@ -1,9 +1,9 @@
 import {
   keyCheckFromResponse
-} from "./chunk-VADZ6C26.js";
+} from "./chunk-4TT2ZFWZ.js";
 import {
   installNetworkDefaults
-} from "./chunk-XGW7J7KT.js";
+} from "./chunk-A2F7T3IR.js";
 import {
   getBaseUrl
 } from "./chunk-NP65LEAY.js";

package/dist/{chunk-GPP7AUCM.js → chunk-ZP5AB6R5.js}

@@ -1,13 +1,13 @@
 import {
   APPROVAL_RULES_PATH,
   canChangeApprovalSettings
-} from "./chunk-YRQWA4ZS.js";
+} from "./chunk-6RFDH4JU.js";
 import {
   callMcpTool
-} from "./chunk-2CJNGJQS.js";
+} from "./chunk-ZEPS4KIK.js";
 import {
   absoluteUrl
-} from "./chunk-VADZ6C26.js";
+} from "./chunk-4TT2ZFWZ.js";
 import {
   getBaseUrl
 } from "./chunk-NP65LEAY.js";

package/dist/{chunk-WJ2APMU5.js → chunk-ZXDHPPGI.js}

@@ -1,13 +1,13 @@
 import {
   notificationAnswerStep
-} from "./chunk-GPP7AUCM.js";
+} from "./chunk-ZP5AB6R5.js";
 import {
   canChangeApprovalSettings
-} from "./chunk-YRQWA4ZS.js";
+} from "./chunk-6RFDH4JU.js";
 import {
   matchMacAccountStep,
   retryAgentCommand
-} from "./chunk-UOM5SUWJ.js";
+} from "./chunk-N7OMDSXK.js";
 import {
   EXIT
 } from "./chunk-KZERVKTD.js";

package/dist/{codex-app-cards-switch-ARYZG5DV.js → codex-app-cards-switch-XLSLVXDP.js}

@@ -22,18 +22,18 @@ import {
   turnCodexAppCardsOff,
   turnCodexAppCardsOn,
   whyLaunchctlFailed
-} from "./chunk-GVZAEST7.js";
-import "./chunk-M66W7UD7.js";
+} from "./chunk-NWLGRSGE.js";
+import "./chunk-GJXRYXMC.js";
 import "./chunk-XCEN33UP.js";
 import "./chunk-QCGNGEGE.js";
-import "./chunk-FE3I7SCA.js";
+import "./chunk-FUVVGIXZ.js";
 import "./chunk-XHKBHWLX.js";
-import "./chunk-TQ43EX2E.js";
+import "./chunk-2HTE4ECJ.js";
 import "./chunk-E46NE7FB.js";
-import "./chunk-7SY2F6JA.js";
+import "./chunk-BC2HT6JP.js";
 import "./chunk-DWUD47H5.js";
-import "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+import "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-NP65LEAY.js";
 import "./chunk-KWWHFTNJ.js";
 import "./chunk-ZVU6WMMU.js";

package/dist/{codex-desktop-launch-6P2IXUIZ.js → codex-desktop-launch-HRE6YP56.js}

@@ -11,7 +11,7 @@ import {
   installedCodexApp,
   shellQuoted,
   writeDesktopProxy
-} from "./chunk-M66W7UD7.js";
+} from "./chunk-GJXRYXMC.js";
 import "./chunk-XCEN33UP.js";
 import {
   CODEX_APP_LAUNCH_VARIABLE

package/dist/{codex-session-launch-WUZSHGSI.js → codex-session-launch-7RGYGW32.js}

@@ -11,27 +11,27 @@ import {
   isCodexQuestionLeftWithTheLocalClient,
   planCodexElicitation,
   reportOwnedQuestion
-} from "./chunk-6OVWYAET.js";
+} from "./chunk-3ZE7VQOU.js";
 import "./chunk-P4W5TP2X.js";
-import "./chunk-UAB3K3TA.js";
-import "./chunk-VNROKR2K.js";
+import "./chunk-4C7OJLSL.js";
+import "./chunk-WBZA72O5.js";
 import "./chunk-N5P2FLOJ.js";
-import "./chunk-NFKB7ZHA.js";
-import "./chunk-3ZWJBPQ5.js";
+import "./chunk-OBS7O22Q.js";
+import "./chunk-B4NVYPX5.js";
 import "./chunk-4PS27SCG.js";
 import "./chunk-XMSDA5WA.js";
 import "./chunk-XHKBHWLX.js";
 import "./chunk-OUIUIJV4.js";
 import {
   writeDegraded
-} from "./chunk-7AH6F44G.js";
+} from "./chunk-3XJL2M7H.js";
 import "./chunk-POFBE6ZY.js";
-import "./chunk-2CJNGJQS.js";
-import "./chunk-VADZ6C26.js";
-import "./chunk-XGW7J7KT.js";
-import "./chunk-7SY2F6JA.js";
-import "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+import "./chunk-ZEPS4KIK.js";
+import "./chunk-4TT2ZFWZ.js";
+import "./chunk-A2F7T3IR.js";
+import "./chunk-BC2HT6JP.js";
+import "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-NP65LEAY.js";
 import "./chunk-PPY5N2E6.js";
 import "./chunk-KZERVKTD.js";

package/dist/{global-upgrade-QGHGUP5V.js → global-upgrade-VR76ZRWG.js}

@@ -7,15 +7,15 @@ import {
   recordUnfinishedUpgrade,
   upgradeInstalledPackage,
   withUpgradeLock
-} from "./chunk-42KJLBX2.js";
-import "./chunk-QN2EFKXV.js";
-import "./chunk-UAB3K3TA.js";
-import "./chunk-VNROKR2K.js";
-import "./chunk-3ZWJBPQ5.js";
-import "./chunk-K34J2V5G.js";
+} from "./chunk-6GDZ4RYR.js";
+import "./chunk-FRUKY6KV.js";
+import "./chunk-4C7OJLSL.js";
+import "./chunk-WBZA72O5.js";
+import "./chunk-B4NVYPX5.js";
+import "./chunk-BSTZ66FA.js";
 import "./chunk-POFBE6ZY.js";
-import "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+import "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-KZERVKTD.js";
 import "./chunk-KWWHFTNJ.js";
 import "./chunk-ZVU6WMMU.js";

package/dist/{identity-WRUYTQ4O.js → identity-NJAXA45Q.js}

@@ -2,9 +2,9 @@ import {
   getMachineId,
   getOrCreateMachineId,
   readExistingMachineId
-} from "./chunk-7SY2F6JA.js";
-import "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+} from "./chunk-BC2HT6JP.js";
+import "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-ZVU6WMMU.js";
 import "./chunk-5TLDFPW6.js";
 import "./chunk-MLKGABMK.js";

package/dist/{live-capabilities-AJJILIIZ.js → live-capabilities-5UTM55OC.js}

@@ -22,10 +22,10 @@ import {
   resolveControlPolicy,
   resolveProviderBinary,
   trackProviderInventory
-} from "./chunk-UAB3K3TA.js";
-import "./chunk-VNROKR2K.js";
-import "./chunk-3ZWJBPQ5.js";
-import "./chunk-5YDIHB67.js";
+} from "./chunk-4C7OJLSL.js";
+import "./chunk-WBZA72O5.js";
+import "./chunk-B4NVYPX5.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-ZVU6WMMU.js";
 import "./chunk-5TLDFPW6.js";
 import "./chunk-MLKGABMK.js";

package/dist/{paths-Q5A6GBRA.js → paths-BX4DXC3B.js}

@@ -37,8 +37,8 @@ import {
   serviceOwedBackMark,
   vscodePluginDir,
   vscodePluginMcp
-} from "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+} from "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-ZVU6WMMU.js";
 import "./chunk-5TLDFPW6.js";
 import "./chunk-MLKGABMK.js";

package/dist/{reapply-BMNUBJ3Z.js → reapply-PMCMNTED.js}

@@ -12,34 +12,34 @@ import {
   reapplyOpenCodePlugin,
   reapplyVsCodePlugin,
   repairCodexHolds
-} from "./chunk-VNYSGRCL.js";
-import "./chunk-GVMOTYFU.js";
-import "./chunk-NFQCFVKJ.js";
-import "./chunk-XPE745FL.js";
-import "./chunk-UOM5SUWJ.js";
-import "./chunk-UDYWZ4DI.js";
-import "./chunk-MY6CX7WE.js";
-import "./chunk-VNROKR2K.js";
-import "./chunk-3ZWJBPQ5.js";
-import "./chunk-4VHT5SWU.js";
-import "./chunk-K4I2LESS.js";
+} from "./chunk-LH3SNS6H.js";
+import "./chunk-IXOCJHJW.js";
+import "./chunk-Z2LYELNQ.js";
+import "./chunk-CAXE3TYX.js";
+import "./chunk-N7OMDSXK.js";
+import "./chunk-QQCGYHYG.js";
+import "./chunk-TBPMI4LY.js";
+import "./chunk-WBZA72O5.js";
+import "./chunk-B4NVYPX5.js";
+import "./chunk-O53SJBBB.js";
+import "./chunk-DM5LNEGJ.js";
 import "./chunk-D7ZJ3AUK.js";
-import "./chunk-7TZDVGMC.js";
+import "./chunk-OMLR56J5.js";
 import "./chunk-NMUI3ZWG.js";
 import "./chunk-XHKBHWLX.js";
-import "./chunk-TQ43EX2E.js";
-import "./chunk-4RZXECJS.js";
+import "./chunk-2HTE4ECJ.js";
+import "./chunk-DHVVEH2K.js";
 import "./chunk-TXJ65MIV.js";
 import "./chunk-OUIUIJV4.js";
-import "./chunk-7AH6F44G.js";
+import "./chunk-3XJL2M7H.js";
 import "./chunk-POFBE6ZY.js";
-import "./chunk-2CJNGJQS.js";
-import "./chunk-VADZ6C26.js";
-import "./chunk-XGW7J7KT.js";
-import "./chunk-7SY2F6JA.js";
+import "./chunk-ZEPS4KIK.js";
+import "./chunk-4TT2ZFWZ.js";
+import "./chunk-A2F7T3IR.js";
+import "./chunk-BC2HT6JP.js";
 import "./chunk-DWUD47H5.js";
-import "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+import "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-NP65LEAY.js";
 import "./chunk-PPY5N2E6.js";
 import "./chunk-KZERVKTD.js";

package/dist/src/index.js

@@ -1,25 +1,25 @@
 import {
   handlePreToolUse
-} from "../chunk-X5INK4OE.js";
-import "../chunk-LXTTFH4P.js";
+} from "../chunk-FFIDXKQ7.js";
+import "../chunk-RX5FSSQK.js";
 import "../chunk-KXGKUV2F.js";
-import "../chunk-FQ2EBMDA.js";
-import "../chunk-S33CCO4J.js";
-import "../chunk-JILOKJ3W.js";
-import "../chunk-VU5PKE2N.js";
-import "../chunk-4VHT5SWU.js";
-import "../chunk-FE3I7SCA.js";
-import "../chunk-K4I2LESS.js";
+import "../chunk-BOWXZWHG.js";
+import "../chunk-MQKXQWXA.js";
+import "../chunk-JQMOQLM2.js";
+import "../chunk-I6MNMAS7.js";
+import "../chunk-O53SJBBB.js";
+import "../chunk-FUVVGIXZ.js";
+import "../chunk-DM5LNEGJ.js";
 import "../chunk-D7ZJ3AUK.js";
-import "../chunk-7TZDVGMC.js";
+import "../chunk-OMLR56J5.js";
 import "../chunk-NMUI3ZWG.js";
 import {
   fetchAccountPublicKey
 } from "../chunk-4PS27SCG.js";
 import "../chunk-XMSDA5WA.js";
-import "../chunk-IOJZPPDB.js";
+import "../chunk-JOULYVW6.js";
 import "../chunk-XHKBHWLX.js";
-import "../chunk-TQ43EX2E.js";
+import "../chunk-2HTE4ECJ.js";
 import {
   fetchModeOverride,
   fetchModeState,
@@ -28,22 +28,22 @@ import {
   handlePostToolUse,
   handleStop,
   reportEvent
-} from "../chunk-4RZXECJS.js";
+} from "../chunk-DHVVEH2K.js";
 import "../chunk-TXJ65MIV.js";
 import "../chunk-OUIUIJV4.js";
 import {
   askUser,
   cancelQuestion,
   waitForAnswer
-} from "../chunk-7AH6F44G.js";
+} from "../chunk-3XJL2M7H.js";
 import "../chunk-POFBE6ZY.js";
-import "../chunk-2CJNGJQS.js";
-import "../chunk-VADZ6C26.js";
-import "../chunk-XGW7J7KT.js";
-import "../chunk-7SY2F6JA.js";
+import "../chunk-ZEPS4KIK.js";
+import "../chunk-4TT2ZFWZ.js";
+import "../chunk-A2F7T3IR.js";
+import "../chunk-BC2HT6JP.js";
 import "../chunk-DWUD47H5.js";
-import "../chunk-YLWPJ2MP.js";
-import "../chunk-5YDIHB67.js";
+import "../chunk-NOGDU4XS.js";
+import "../chunk-QOMIFKQL.js";
 import {
   getApiKey,
   getBaseUrl

package/dist/{upgrade-lock-NGCFJRRN.js → upgrade-lock-2G2S3FH7.js}

@@ -4,9 +4,9 @@ import {
   installWithUpgradeLock,
   ownsUpgradeLock,
   releaseAutoUpdateLock
-} from "./chunk-QN2EFKXV.js";
-import "./chunk-YLWPJ2MP.js";
-import "./chunk-5YDIHB67.js";
+} from "./chunk-FRUKY6KV.js";
+import "./chunk-NOGDU4XS.js";
+import "./chunk-QOMIFKQL.js";
 import "./chunk-ZVU6WMMU.js";
 import "./chunk-5TLDFPW6.js";
 import "./chunk-MLKGABMK.js";

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pushary",
-  "version": "1.9.86",
-  "description": "Permission hooks for AI coding agents: route tool approvals through Pushary push notifications",
+  "version": "1.9.88",
+  "description": "Human-in-the-loop (HITL) for AI agents: ask a person for approvals or answers by push notification. One command connects Claude Code, Codex, Cursor, Gemini CLI and more.",
   "keywords": [
     "pushary",
     "claude-code",