argus-hermes-bridge 0.1.0 → 0.1.1

package/README.md

@@ -6,10 +6,12 @@ Windows, and hosts without a systemd user manager are outside this beta path.
 
 ## Start here
 
-Open Argus → **Set up Argus** → **Copy setup prompt**. Send that prompt to
-Hermes. The prompt includes the pinned npm command. Hermes can do the host setup and
-return a three-line connection block for the phone. Install Tailscale on your
-iPhone and sign in to the same tailnet as your Hermes host.
+Open Argus → **Set up Argus** → **Copy prompt**. Send that short message to
+Hermes. It links to [llm.txt](https://unpkg.com/argus-hermes-bridge@0.1.1/llm.txt),
+the full instructions with the pinned npm command. **View prompt** shows the
+same instructions inside Argus. Hermes can do the host setup and return a
+three-line connection block for the phone. Install Tailscale on your iPhone
+and sign in to the same tailnet as your Hermes host.
 
 The companion package has no npm dependencies or install hooks. Downloading it
 does not start a service; `setup` explicitly installs the bridge. It copies only
@@ -21,11 +23,11 @@ It does not need the private Argus repository.
 On the Hermes host, using its normal user account and Node.js 22 or newer:
 
 ```sh
-npx --yes argus-hermes-bridge@0.1.0 setup
+npx --yes argus-hermes-bridge@0.1.1 setup
 ```
 
 The package is [argus-hermes-bridge on npm](https://www.npmjs.com/package/argus-hermes-bridge).
-Use `npx --yes argus-hermes-bridge@0.1.0` followed by any command below.
+Use `npx --yes argus-hermes-bridge@0.1.1` followed by any command below.
 A supplied tarball also works with `npx --yes --package /path/to/package.tgz argus-bridge setup`.
 
 `setup` finds the actual Tailscale hostname, checks runtime imports, installs a
@@ -49,7 +51,7 @@ custom installation, set these **paths** before the setup command:
 ARGUS_HERMES_HOME=/path/to/hermes-config \
 ARGUS_HERMES_SOURCE=/path/to/hermes-agent \
 ARGUS_HERMES_PYTHON=/path/to/venv/bin/python3 \
-npx --yes argus-hermes-bridge@0.1.0 setup
+npx --yes argus-hermes-bridge@0.1.1 setup
 ```
 
 These selections persist in the service definition and `~/.config/argus/bridge.json`.

package/{HermesSetupPrompt.txt → llm.txt}

@@ -1,14 +1,14 @@
 I downloaded the Argus iPhone beta from TestFlight. Please connect it to my existing Hermes on this Mac or Linux/VPS host. Do the setup for me and keep the steps I need to do myself short.
 
 Use the published Argus bridge package from npm with this exact command on the host where Hermes runs:
-npx --yes argus-hermes-bridge@0.1.0 setup
+npx --yes argus-hermes-bridge@0.1.1 setup
 The command includes the installer. You do not need to ask me for a separate download or private repository access. Use exactly this package name and version. If npm cannot retrieve it, report the actual error.
 
 1. Inspect this host and locate the existing working Hermes installation, its Python runtime and config home. The beta supports macOS with a logged-in desktop user, or Linux with a working systemd user service manager. If Hermes runs in a container, Windows, or a restricted environment without these capabilities, explain the blocker before making changes. Use the same user account as Hermes; do not run the installer as root or reinstall Hermes.
 2. Check Node.js 22+ and Tailscale. Help me install missing prerequisites using their official instructions. I need Tailscale on my iPhone and the Hermes host, signed into the same tailnet. Let me complete sign-in, HTTPS enablement, or administrator prompts myself. Preserve existing Tailscale routes. Use private Tailscale Serve, never public Funnel or an open internet port.
 3. Inspect the package README from npm, then run the exact pinned setup command above. If a bridge already runs on this host, inspect its service before updating it and preserve existing device access. Finish active phone requests before a service restart. Pass ARGUS_HERMES_HOME, ARGUS_HERMES_SOURCE or ARGUS_HERMES_PYTHON only if auto-discovery needs the paths from this installation. Do not copy provider keys or passwords into chat, the phone, or the package. Keep the default strict phone approvals. Do not enable monitoring, automatic tool approvals, vault writes, or change my model/provider settings for setup.
-4. Resolve setup errors, then run npx --yes argus-hermes-bridge@0.1.0 doctor. On Linux, check user-service lingering and help me enable it if needed so the bridge survives logout/reboot. On a Mac the user must stay logged in and the host must stay awake; explain any macOS file-access prompt. Do not claim a successful HTTPS check proves inference or tool approvals.
-5. Issue the pairing code last, using npx --yes argus-hermes-bridge@0.1.0 pair if the setup code is close to expiry. Return its exact three-line block in one copyable code block:
+4. Resolve setup errors, then run npx --yes argus-hermes-bridge@0.1.1 doctor. On Linux, check user-service lingering and help me enable it if needed so the bridge survives logout/reboot. On a Mac the user must stay logged in and the host must stay awake; explain any macOS file-access prompt. Do not claim a successful HTTPS check proves inference or tool approvals.
+5. Issue the pairing code last, using npx --yes argus-hermes-bridge@0.1.1 pair if the setup code is close to expiry. Return its exact three-line block in one copyable code block:
 ARGUS-PAIR/1
 https://<actual-host>.<actual-tailnet>.ts.net:8443
 <actual 12-character pairing code>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "argus-hermes-bridge",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Private Tailscale connection between the Argus iPhone beta and your existing Hermes",
   "type": "module",
   "license": "UNLICENSED",
@@ -17,7 +17,7 @@
   "files": [
     "scripts",
     "prototypes",
-    "HermesSetupPrompt.txt",
+    "llm.txt",
     "README.md"
   ]
 }