@inline-chat/hermes-agent-adapter 1.0.1 → 1.1.0

package/README.md

@@ -35,6 +35,7 @@ Supported:
 - Native Inline `/` command-menu sync for Hermes slash commands, including `/threads`, `/follow`, `/unfollow`, `/inline_sync`, `/inline_version`, and `/update`; typed slash commands continue to work even if menu sync is disabled or rejected.
 - Inline-native buttons for clarify prompts, command approvals, slash confirmations, and model selection.
 - Agent-created `send_message`/`edit_message` button rows with opaque callback data. A callback is acknowledged after its target and access checks succeed, then enters Hermes as a normal turn naming the source message and exact action fields. The normal response edits that source message and clears omitted buttons; the agent can instead call `edit_message` with replacement buttons and finish with `NO_REPLY` so the explicit edit remains authoritative.
+- Message widgets: sandboxed HTML (charts, diagrams, mockups, small pickers) through the `inline` tool's `send_widget` action, or an `<iframe title="…" id="…" height="…">HTML</iframe>` block in a Markdown reply. Long replies are split around widgets, never inside one, with at most one widget per message; a widget longer than the 4,000-character chunk goes alone, up to Inline's 100,000-character limit. Streaming previews hide a widget until its closing tag arrives. `send_widget` returns Inline's reason when the server rejects a widget. A viewer's `inline.action(name, payload)` call becomes a turn naming the widget ID, call name, and untrusted JSON payload, and the answer replies below the widget instead of replacing it. Call names and payloads need realtime SDK 0.0.22 or later; with an older bundled SDK, the turn names only the widget.
 - Outbound local photo, video, voice, and document uploads with configurable size caps.
 - Inbound photo, video, voice, and document summaries, with URL-backed media cached locally for Hermes when available.
 - Reactions on bot messages, plus opt-in lifecycle/system events as synthetic Hermes messages.
@@ -51,6 +52,24 @@ Unsupported or intentionally limited:
 - Live voice sessions or calls. Voice file messages are supported, but realtime audio is not.
 - Media without a usable Inline CDN/local URL. Those messages still produce text summaries, but Hermes may not receive a local file path.
 
+## Release 1.1.0
+
+Command approvals show Allow and Deny buttons again on every supported Hermes. A
+tap answers only the request its card was sent for, and on Hermes versions with
+`approvals.approvers` only the people that setting allows can answer. Hermes now
+writes the card, so a long command arrives in full before its buttons. Gateways
+with many Inline bots no longer hang during startup or keep the old process alive
+on restart. Scheduled posts can mention their recipient with `cron_mention_prefix`
+(see Scheduled mentions below). The agent settings show how full the session's
+context window is, which Inline's composer draws as its context circle. When a
+later part of a long reply is refused, the parts already sent are no longer posted
+again as a plain-text copy. Tested on Hermes `0.23.0`.
+
+```sh
+npm install -g @inline-chat/hermes-agent-adapter@1.1.0
+inline-hermes install --force
+```
+
 ## Release 1.0.0
 
 A major release with breaking changes. Bots join a thread through its first
@@ -197,8 +216,8 @@ mismatch, rerun the same command after rebuilding or upgrading the package.
 
 - Hermes Agent: requires the external user plugin registry and native platform
   plugin loader available in Hermes Agent `>=0.21.3`. This package was validated
-  against Hermes Agent `0.22.7` from source commit `b200f5bc60e31588ba2cb60e288029c4a54ba5fa` (tag
-  `v0.22.7`), and installs on the minimum `0.21.3`. Hermes `0.22.6` and later refuse
+  against Hermes Agent `0.23.0` from source commit `2bd378ed1b8d6bf2192cb26e0a55ff3091e6bd19` (tag
+  `v0.23.0`), and installs on the minimum `0.21.3`. Hermes `0.22.6` and later refuse
   every message from adapters before `1.0.0`; upgrade as in Release 1.0.0 above.
 - CI checks the minimum supported Hermes release, newest stable source, and upstream
   `main`, including a full inbound turn through Hermes' production gateway. A six-hour scheduled check also tests the published npm `latest` adapter.
@@ -207,8 +226,10 @@ mismatch, rerun the same command after rebuilding or upgrading the package.
 - Node.js: `>=20` is required for the bundled sidecar. Hermes-managed Node 22,
   system Node, or an explicit `INLINE_NODE_BIN` path all work.
 - Inbound recovery retries without waiting for another message or reconnect. Independent chats are consumed concurrently; same-chat order and delivery acknowledgements are preserved. Sender provenance lookups start with a short timeout and expand up to the existing SDK ceiling after timeouts; deferred inputs stay recoverable. Stream replacement wakes pending backpressure writes.
-- Inline transport: the sidecar uses `@inline-chat/realtime-sdk@0.0.18` and is
+- Inline transport: the 1.1.0 candidate sidecar uses `@inline-chat/realtime-sdk@0.0.22` and is
   bundled into the npm package, so Hermes startup does not run `npm install`.
+  This SDK includes widget calls and submitted forms; protocol `0.0.14` and SDK
+  `0.0.22` must be published before the adapter's registry-only release preflight.
 - Live sends require a valid Inline user or bot token in `INLINE_TOKEN`,
   `INLINE_BOT_TOKEN`, `platforms.inline.token`, or `inline.token`.
 
@@ -322,6 +343,7 @@ Access control follows Hermes' native platform model:
 | `INLINE_SETTINGS_PATH` | JSON settings file for per-chat `/threads` overrides. `/threads` shows native Auto/On buttons; `reset` clears the chat override back to the global default. Defaults next to `INLINE_STATE_PATH`; `.env`-like paths are refused. |
 | `INLINE_SYSTEM_EVENTS` | Delivers Inline lifecycle events such as edits, deletes, and participant changes as synthetic messages. Defaults to `false`. Reactions on bot messages are always delivered. |
 | `INLINE_REACTIONS` | Shows 👀 while Hermes handles an inbound message, then ✅ on success or ❌ on failure. Cancellation clears the working marker. Defaults to `false`. |
+| `INLINE_CRON_MENTION_PREFIX` | Opt-in Inline Markdown mention prepended once to scheduled gateway text deliveries, for example `[@You](inline://user?id=42)`. Defaults to empty. See [Scheduled mentions](#scheduled-mentions). |
 | `INLINE_PARSE_MARKDOWN` | Controls whether supported outbound Inline Markdown is parsed. Defaults to `true`; `false` preserves the supplied syntax literally. |
 | `INLINE_SYNC_COMMANDS` | Syncs Hermes slash commands into Inline's native `/` bot command menu on gateway connect. Defaults to `true`. |
 | `INLINE_COMMAND_LIMIT` | Caps native Inline bot command sync. Must be `1` through `100`; defaults to `100`. |
@@ -368,9 +390,10 @@ Equivalent Hermes YAML can use `allow_from`, `allowed_users`,
 `observed_context_limit`, `observe_unmentioned_messages`, `settings_path`, and
 `reactions` under the Inline platform config. Operational settings such
 as `base_url`, `parse_markdown`, `media_max_mb`, `upload_max_mb`,
-`state_path`, `sidecar_port`, `connect_timeout_ms`, `sync_commands`, and
-`command_limit` can also be set there.
+`state_path`, `sidecar_port`, `connect_timeout_ms`, `sync_commands`,
+`cron_mention_prefix`, and `command_limit` can also be set there.
 Prefer Hermes YAML for behavioral settings. Environment variables remain supported for compatibility and secret-backed deployment inputs.
+
 Use a JSON list for mention regexes that contain commas, for example
 `["hermes\\b[:,]?"]`.
 
@@ -455,6 +478,36 @@ what the bot may change. `delete_chat` always needs an explicit `chat_id`.
 The plugin id is `inline`, which is intentionally the same id an eventual
 bundled Hermes adapter should use.
 
+### Scheduled mentions
+
+To bring scheduled text posts back into your Inline sidebar, configure a mention
+for the person who should receive them, then restart the Hermes gateway:
+
+```yaml
+platforms:
+  inline:
+    cron_mention_prefix: "[@You](inline://user?id=42)"
+```
+
+Replace `42` with that person's Inline user ID. This setting applies to this
+profile's scheduled gateway text deliveries; set it to `""` to disable it,
+including when `INLINE_CRON_MENTION_PREFIX` is exported. A structured mention
+can reopen an eligible recipient's closed thread. Their notification settings
+still apply.
+
+The adapter uses Hermes' `job_id` delivery metadata to identify scheduled posts.
+It adds the prefix before splitting a long post and skips an existing leading
+prefix. `cron.delivery.notify: false` suppresses the added prefix and sends the
+text silently, using Inline's existing notification opt-out. Ordinary replies
+do not get a prefix, and the selected destination stays the same. Markdown
+parsing must be enabled (the default); with `parse_markdown: false` the setting
+is ignored with a warning, preserving the caller's literal text.
+
+Hermes currently omits cron identity from standalone/CLI fallback and media-only
+sends. Those deliveries remain unchanged. Media accompanied by scheduled text
+gets the mention in the text post. The required upstream metadata extension is
+described in [Hermes upstream seams](docs/hermes-upstream-seams.md#9-cron-delivery-metadata-across-transports).
+
 ## Shared transcripts in groups and threads
 
 To share one conversation transcript among admitted participants in a group

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inline-chat/hermes-agent-adapter",
-  "version": "1.0.1",
+  "version": "1.1.0",
   "description": "Hermes Agent platform adapter for Inline, with a native Python plugin and bundled Inline realtime sidecar.",
   "license": "Apache-2.0",
   "type": "module",
@@ -38,6 +38,7 @@
     "plugin/inline/profile.py",
     "plugin/inline/telemetry.py",
     "plugin/inline/tools.py",
+    "plugin/inline/widgets.py",
     "plugin/inline/sidecar/index.mjs"
   ],
   "bin": {
@@ -65,7 +66,7 @@
     "check": "bun run typecheck && bun run lint && bun run test"
   },
   "dependencies": {
-    "@inline-chat/realtime-sdk": "0.0.20",
+    "@inline-chat/realtime-sdk": "0.0.22",
     "yaml": "2.9.0"
   },
   "devDependencies": {
@@ -91,12 +92,12 @@
     },
     "machineSetupProtocol": 1,
     "minHermesVersion": "0.21.3",
-    "testedHermesVersion": "0.22.7",
-    "testedHermesCommit": "b200f5bc60e31588ba2cb60e288029c4a54ba5fa"
+    "testedHermesVersion": "0.23.0",
+    "testedHermesCommit": "2bd378ed1b8d6bf2192cb26e0a55ff3091e6bd19"
   },
-  "gitHead": "ec95e9296b83c13d2179b47019d915b16783c186",
+  "gitHead": "a24298dc55d21eb2655c25cb6c83b7a133321838",
   "inlineRelease": {
-    "tag": "hermes-agent-v1.0.1",
-    "sha": "ec95e9296b83c13d2179b47019d915b16783c186"
+    "tag": "hermes-agent-v1.1.0",
+    "sha": "a24298dc55d21eb2655c25cb6c83b7a133321838"
   }
 }

package/plugin/inline/README.md

@@ -44,6 +44,10 @@ inbound message delivery; confirm that the bot replies.
 - `/inline_sync` republishes Hermes commands and skills to Inline.
 - `/inline_version` reports the loaded plugin version and last catalog sync.
 
+The agent can send sandboxed HTML message widgets (charts, diagrams, small
+pickers) with the `inline` tool's `send_widget` action or an `<iframe>` block
+in its reply; viewer widget calls come back as turns.
+
 Access controls, group mentions, media limits, native message actions, and
 additional setup options are described in the
 [adapter documentation](https://github.com/inline-chat/inline/tree/main/plugins/hermes-agent#readme).
@@ -53,4 +57,23 @@ with `hermes plugins update inline-platform` after a new pin is accepted, then
 restart the gateway. A newer npm version does not automatically change a
 catalog installation.
 
+### Scheduled mentions
+
+To reopen your closed Inline threads when scheduled text arrives, add an opt-in
+mention to your Hermes config and restart the gateway:
+
+```yaml
+platforms:
+  inline:
+    cron_mention_prefix: "[@You](inline://user?id=42)"
+```
+
+Use your Inline user ID in place of `42`. `INLINE_CRON_MENTION_PREFIX` is the
+environment equivalent; an explicit empty YAML value disables it. Markdown
+parsing must stay enabled. The prefix applies once to each scheduled gateway
+text delivery, respects Hermes' cron notification opt-out, and leaves ordinary
+replies alone. Recipient notification settings still apply. Current Hermes
+hosts do not identify standalone fallback or media-only sends as cron deliveries,
+so those paths cannot add the prefix; scheduled text accompanying media does.
+
 The plugin is distributed under the Apache-2.0 license; see [LICENSE](LICENSE).