@inline-chat/hermes-agent-adapter 0.0.18-alpha.0 → 0.0.19

package/README.md

@@ -31,7 +31,7 @@ Supported:
 - Cached, privacy-safe sender names/usernames plus chat/thread IDs, selective reply/thread/observed context, and parent-thread context, with first-name/username Markdown mention guidance and current chat/thread links.
 - OpenClaw-style entity summaries for live turns and tool-fetched history, including mentions, text links, thread links, thread-title links, code/pre blocks, bot commands, and group mentions as untrusted Hermes context.
 - DM and group policies, user allowlists, group sender allowlists, mention requirements, strict mention mode, allowed chats, and free-response chats.
-- Native Inline `/` command-menu sync for Hermes slash commands, including `/threads`, `/follow`, `/unfollow`, `/inline_update`, `/inline_sync`, `/inline_version`, and `/update`; typed slash commands continue to work even if menu sync is disabled or rejected.
+- 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 immediately and becomes a normal Hermes 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.
 - Outbound local photo, video, voice, and document uploads with configurable size caps.
@@ -61,9 +61,8 @@ hermes gateway setup
 
 When installation runs as root but the Hermes home belongs to its service user,
 the installer automatically aligns the plugin directory ownership with that
-service user. Subsequent `/inline_update` commands replace the durable plugin
-directly; users do not need to maintain a second npm prefix or repeat the
-host-side install commands for routine updates.
+service user. Use the same service user and Hermes home when applying manual
+npm updates.
 
 Select Inline in the messaging-platform picker. The default path is: go to
 **Inline → Settings → Bots → Create a new bot**, then paste its token. See the
@@ -157,7 +156,7 @@ uv run ./hermes plugins list --plain --no-bundled
 Expected local output includes:
 
 ```text
-enabled      user     0.0.18-alpha.0   inline-platform
+enabled      user     0.0.19   inline-platform
 ```
 
 ## Update Or Reinstall
@@ -179,13 +178,17 @@ mismatch, rerun the same command after rebuilding or upgrading the package.
 ## Compatibility
 
 - Hermes Agent: requires the external user plugin registry and native platform
-  plugin loader available in Hermes Agent `>=0.17.0`. This package was validated
-  against Hermes Agent `0.21.0` from source commit `29112bef` (tag
-  `v2026.8.31`).
+  plugin loader available in Hermes Agent `>=0.21.4`. This package was validated
+  against Hermes Agent `0.21.5` from source commit `f97608f178d1ffeca59860195ab7da295f7c8e5f` (tag
+  `v2026.9.24`).
+- CI checks the minimum supported Hermes release, newest stable source, and upstream
+  `main`. A six-hour scheduled check also tests the published npm `latest` adapter.
+  `inline-hermes doctor` requires successful host loading and compatibility validation;
+  unavailable Hermes diagnostics no longer count as healthy.
 - 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.19-alpha.0` and is
+- Inline transport: the sidecar uses `@inline-chat/realtime-sdk@0.0.18` and is
   bundled into the npm package, so Hermes startup does not run `npm install`.
 - Live sends require a valid Inline user or bot token in `INLINE_TOKEN`,
   `INLINE_BOT_TOKEN`, `platforms.inline.token`, or `inline.token`.
@@ -382,17 +385,18 @@ choice. Hermes accepts that form only when the suffix matches its own username,
 then removes the suffix before command dispatch; commands addressed to another
 bot are ignored.
 
-Run `/inline_update` to install the newest adapter from the plugin's current
-npm release channel. Stable installs continue following `latest`, while
-prerelease installs continue following their existing channel such as `alpha`
-or `beta`. Before changing files, the command checks the selected release's
-minimum Hermes version against the running agent and refuses incompatible or
-unverifiable updates. The update runs in the background without exposing the
-Inline token to npm, then asks you to run `/restart` so Hermes loads the
-installed version. Development symlink installs are left untouched.
-Unexpected precheck or installer failures write bounded, credential-redacted
-diagnostics to the standard Hermes log stream under the `[inline-update]`
-marker, so `hermes logs` and Hermes debug reports can surface the root cause.
+Plugin updates are managed on the Hermes host. For a catalog installation, use
+`hermes plugins update inline-platform` after a new reviewed catalog pin is
+available, then restart the gateway. For an npm installation:
+
+```sh
+npm install -g @inline-chat/hermes-agent-adapter@latest
+inline-hermes install --force
+```
+
+Restart the gateway after refreshing the plugin. Version 0.0.19 removes the
+in-chat updater so the same plugin can comply with the catalog's exact-commit
+trust policy. Hermes's own `/update` command is unchanged.
 
 Run `/follow` in an Inline DM, group, or reply thread to explicitly opt into
 eligible unmentioned activity waking Hermes. Run `/unfollow` to explicitly opt

package/dist/install.js

@@ -7174,6 +7174,12 @@ async function inspectInstall(params) {
   if (!node.ok) {
     issues.push(node.error || `${node.source} is not usable: ${node.path}`);
   }
+  if (params.opts.command === "doctor" && !activation.hermesCompatibilityVerified) {
+    issues.push("Hermes could not validate the installed plugin compatibility; check `hermes inline status --json --check-compatibility` and update or repair the plugin");
+  }
+  if (params.opts.command === "doctor" && !activation.hermesCredentialStoreChecked) {
+    issues.push("Hermes credential verification is unavailable; doctor cannot confirm runtime readiness");
+  }
   if (params.opts.command === "doctor" && !activation.pluginEnabled) {
     issues.push(`Hermes plugin '${pluginEnableKey}' is not enabled. Run: hermes plugins enable ${pluginEnableKey}`);
   }
@@ -7206,7 +7212,7 @@ async function inspectInstall(params) {
       warnings.push(message);
   }
   if (targetExists && !activation.installOwnershipAligned) {
-    warnings.push("Installed plugin ownership differs from the Hermes home owner; internal /inline_update may fail until inline-hermes install --force repairs it");
+    warnings.push("Installed plugin ownership differs from the Hermes home owner; manual updates may fail until inline-hermes install --force repairs it");
   }
   return {
     ok: installedReady && issues.length === 0,
@@ -7579,7 +7585,7 @@ async function inspectActivation(hermesHome, target, probeCredential) {
   }
   const tokenPresent = Boolean(process.env.INLINE_TOKEN || process.env.INLINE_BOT_TOKEN);
   const configTokenConfigured = configTokenIsConfigured(config, ["platforms", defaultPluginId, "token"]) || configTokenIsConfigured(config, [defaultPluginId, "token"]);
-  const machineCredential = inspectHermesCredential(hermesHome, probeCredential);
+  const machineCredential = inspectHermesCredential(hermesHome, probeCredential, target);
   const fallbackConfigured = tokenPresent || configTokenConfigured;
   const credentialState = (machineCredential.state === "unknown" || machineCredential.state === "not_configured") && fallbackConfigured ? "configured_unverified" : machineCredential.state;
   const installOwnershipAligned = await inspectInstallOwnership(hermesHome, target);
@@ -7589,6 +7595,7 @@ async function inspectActivation(hermesHome, target, probeCredential) {
     pluginEnabled: readConfigList(config, ["plugins", "enabled"]).includes(pluginEnableKey),
     platformConfigured: readConfigBoolean(config, ["platforms", defaultPluginId, "enabled"]) || readConfigBoolean(config, [defaultPluginId, "enabled"]),
     configTokenConfigured,
+    hermesCompatibilityVerified: machineCredential.compatible === true,
     hermesCredentialStoreChecked: machineCredential.checked,
     hermesCredentialStoreTokenConfigured: machineCredential.configured === true,
     credentialState,
@@ -7649,9 +7656,9 @@ async function chownTree(target, uid, gid) {
   }
   await chown(target, uid, gid);
 }
-function inspectHermesCredential(hermesHome, probe) {
+function inspectHermesCredential(hermesHome, probe, target) {
   const executable = normalizeToken(process.env.INLINE_HERMES_BIN) || "hermes";
-  const args = ["inline", "status", "--json", ...probe ? ["--probe"] : []];
+  const args = ["inline", "status", "--json", ...probe ? ["--probe", "--check-compatibility"] : []];
   const result = spawnSync(executable, args, {
     encoding: "utf8",
     timeout: hermesMachineTimeoutMs,
@@ -7675,11 +7682,13 @@ function inspectHermesCredential(hermesHome, probe) {
   if (record.action !== "inline.status" || typeof record.setupProtocolVersion !== "number" || record.setupProtocolVersion < 1 || typeof record.configured !== "boolean") {
     return { checked: false, configured: null, state: "unknown" };
   }
+  const compatibility = record.compatibility;
+  const compatible = result.status === 0 && compatibility?.ok === true && compatibility.pluginPath === safeRealpathSync(target);
   if (!record.configured) {
-    return { checked: true, configured: false, state: "not_configured" };
+    return { compatible, checked: true, configured: false, state: "not_configured" };
   }
   if (!probe) {
-    return { checked: true, configured: true, state: "configured_unverified" };
+    return { compatible, checked: true, configured: true, state: "configured_unverified" };
   }
   const probeResult = record.probe && typeof record.probe === "object" && !Array.isArray(record.probe) ? record.probe : null;
   if (probeResult?.ok === true) {
@@ -7688,6 +7697,7 @@ function inspectHermesCredential(hermesHome, probe) {
       return { checked: false, configured: true, state: "unknown" };
     const botUsername = typeof probeResult.botUsername === "string" && probeResult.botUsername.trim() ? probeResult.botUsername.trim() : undefined;
     return {
+      compatible,
       checked: true,
       configured: true,
       state: "verified",
@@ -7696,9 +7706,16 @@ function inspectHermesCredential(hermesHome, probe) {
     };
   }
   if (probeResult?.errorKind === "invalid_credential") {
-    return { checked: true, configured: true, state: "invalid" };
+    return { compatible, checked: true, configured: true, state: "invalid" };
+  }
+  return { compatible, checked: true, configured: true, state: "unknown" };
+}
+function safeRealpathSync(target) {
+  try {
+    return realpathSync(target);
+  } catch {
+    return null;
   }
-  return { checked: true, configured: true, state: "unknown" };
 }
 function readConfigList(config, pathParts) {
   const value = readConfigValue(config, pathParts);
@@ -8118,6 +8135,7 @@ Options:
     console.log(`Usage: inline-hermes ${topic} [options]
 
 ${topic === "doctor" ? "Diagnose" : "Inspect"} the installed Inline plugin, sidecar integrity, and Node runtime.
+${topic === "doctor" ? "Doctor also requires a successful Hermes loader compatibility check and credential probe." : ""}
 
 Options:
   --hermes-home <path>  Hermes home directory. Defaults to HERMES_HOME or ~/.hermes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inline-chat/hermes-agent-adapter",
-  "version": "0.0.18-alpha.0",
+  "version": "0.0.19",
   "description": "Hermes Agent platform adapter for Inline, with a native Python plugin and bundled Inline realtime sidecar.",
   "license": "Apache-2.0",
   "type": "module",
@@ -28,6 +28,8 @@
     "README.md",
     "dist/install.d.ts",
     "dist/install.js",
+    "plugin/inline/README.md",
+    "plugin/inline/LICENSE",
     "plugin/inline/__init__.py",
     "plugin/inline/adapter.py",
     "plugin/inline/cli.py",
@@ -62,7 +64,7 @@
     "check": "bun run typecheck && bun run lint && bun run test"
   },
   "dependencies": {
-    "@inline-chat/realtime-sdk": "0.0.19-alpha.0",
+    "@inline-chat/realtime-sdk": "0.0.18",
     "yaml": "2.9.0"
   },
   "devDependencies": {
@@ -81,8 +83,8 @@
       "npmSpec": "@inline-chat/hermes-agent-adapter"
     },
     "machineSetupProtocol": 1,
-    "minHermesVersion": "0.17.0",
-    "testedHermesVersion": "0.21.0",
-    "testedHermesCommit": "29112bef"
+    "minHermesVersion": "0.21.4",
+    "testedHermesVersion": "0.21.5",
+    "testedHermesCommit": "f97608f178d1ffeca59860195ab7da295f7c8e5f"
   }
 }

package/plugin/inline/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+    Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+    stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+    that You distribute, all copyright, patent, trademark, and
+    attribution notices from the Source form of the Work,
+    excluding those notices that do not pertain to any part of
+    the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+    distribution, then any Derivative Works that You distribute must
+    include a readable copy of the attribution notices contained
+    within such NOTICE file, excluding those notices that do not
+    pertain to any part of the Derivative Works, in at least one
+    of the following places: within a NOTICE text file distributed
+    as part of the Derivative Works; within the Source form or
+    documentation, if provided along with the Derivative Works; or,
+    within a display generated by the Derivative Works, if and
+    wherever such third-party notices normally appear. The contents
+    of the NOTICE file are for informational purposes only and
+    do not modify the License. You may add Your own attribution
+    notices within Derivative Works that You distribute, alongside
+    or as an addendum to the NOTICE text from the Work, provided
+    that such additional attribution notices cannot be construed
+    as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/plugin/inline/README.md

@@ -0,0 +1,56 @@
+# Inline for Hermes Agent
+
+Use Hermes from Inline work-chat DMs, chats, and reply threads. The plugin
+connects Hermes to Inline through a bundled Node.js sidecar; it does not install
+npm packages when the gateway starts.
+
+## Requirements
+
+- Hermes Agent 0.21.4 or newer.
+- Node.js 20 or newer, available on the gateway host.
+- An Inline bot token. [Create a bot](https://inline.chat/docs/creating-a-bot),
+  or use the guided setup below.
+
+## Install and configure
+
+Once this entry is available in the Hermes catalog:
+
+```sh
+hermes plugins install inline-platform
+hermes plugins enable inline-platform
+hermes gateway setup
+```
+
+Select **Inline** in gateway setup. It can guide you through bot creation or
+accept an existing token using Hermes's credential storage. Keep tokens out of
+chat messages and command-line arguments.
+
+Check configuration and plugin compatibility:
+
+```sh
+hermes inline status --json --check-compatibility
+hermes inline status --json --probe
+hermes gateway status
+```
+
+Start or restart the Hermes gateway through your usual service manager, then
+send the bot a DM in Inline. A successful status probe alone does not prove
+inbound message delivery; confirm that the bot replies.
+
+## Using the plugin
+
+- `/threads` configures reply-thread routing.
+- `/follow` and `/unfollow` control explicit chat following.
+- `/inline_sync` republishes Hermes commands and skills to Inline.
+- `/inline_version` reports the loaded plugin version and last catalog sync.
+
+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).
+
+The catalog pins an exact reviewed source commit. Update a catalog installation
+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.
+
+The plugin is distributed under the Apache-2.0 license; see [LICENSE](LICENSE).