@hermespilot/link 0.1.8 → 0.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/chunk-TMCXOV6J.js +17419 -0
- package/dist/chunk-TMCXOV6J.js.map +1 -0
- package/dist/cli/index.js +363 -28
- package/dist/cli/index.js.map +1 -1
- package/dist/http/app.d.ts +342 -0
- package/dist/http/app.js +1 -1
- package/package.json +1 -1
- package/dist/chunk-L2NM2XMX.js +0 -3099
- package/dist/chunk-L2NM2XMX.js.map +0 -1
package/README.md
CHANGED
|
@@ -31,7 +31,7 @@ hermeslink logs
|
|
|
31
31
|
|
|
32
32
|
`hermeslink pair` requires HermesPilot Server and Relay to be available. The terminal side does not ask for a HermesPilot account; the App must be logged in before it scans or claims a pairing session.
|
|
33
33
|
|
|
34
|
-
After
|
|
34
|
+
After the first successful QR claim, `hermeslink pair` starts Hermes Link in the background and enables boot autostart. Pairing additional devices does not rewrite boot autostart settings; use `hermeslink autostart on` or `hermeslink autostart off` to manage that setting explicitly. Boot autostart does not configure launchd/systemd restart policies; if the user stops Hermes Link, the operating system should not automatically relaunch it until the next login/boot autostart cycle.
|
|
35
35
|
|
|
36
36
|
When the App sends a message, Hermes Link prepares `~/.hermes/config.yaml` for the Hermes API Server and attempts to start Hermes Gateway with `hermes gateway run --replace` if the API Server is not already reachable. If Hermes Agent is missing or too old to provide `/v1/runs`, Link returns an actionable error and the user should run:
|
|
37
37
|
|