@hermespilot/link 0.6.0 → 0.6.2

package/README.md

@@ -41,13 +41,16 @@ hermeslink autostart on
 hermeslink autostart off
 hermeslink doctor
 hermeslink logs
+hermeslink logs -f
+hermeslink logs -n 100
+hermeslink logs flush
 ```
 
 `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.
 
 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.
 
-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:
+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/responses`, Link returns an actionable error and the user should run:
 
 ```bash
 hermes update
@@ -58,7 +61,7 @@ If Hermes Agent is configured through `~/.hermes/.env`, Link follows the same `A
 
 CLI output follows the current system language when it is Chinese or English. You can override it for a single command with `HERMESLINK_LANG=zh-CN` or `HERMESLINK_LANG=en`.
 
-Set `HERMESLINK_LOG_LEVEL=warn` to suppress `debug` and `info` logs in published builds; `warn` is the default. You can also persist it with `hermeslink config set log-level warn`.
+Set `HERMESLINK_LOG_LEVEL=warn` to suppress `debug` and `info` logs in published builds; `warn` is the default. You can also persist it with `hermeslink config set log-level warn`. A running daemon keeps the log write level it started with; run `hermeslink restart` after changing `log-level` if you need the write level to take effect immediately. `hermeslink logs` filters displayed lines by the current configured level by default, and `--level debug` can be used to inspect lower-level history.
 
 ## Runtime data
 
@@ -70,4 +73,6 @@ Hermes Link keeps its local identity and runtime state under:
 
 Uninstalling the npm package does not remove this directory, so the same Link ID can be reused after reinstalling.
 
-Service logs are written as rotated JSONL files under `~/.hermeslink/logs/hermeslink.log`. A paired App can read the same service log stream through `GET /api/v1/logs` using the normal Link access token.
+Service logs are written as rotated JSONL files under `~/.hermeslink/logs/hermeslink.log`. `hermeslink logs` prints the relevant paths, `hermeslink logs -n 100` prints recent lines, and `hermeslink logs -f` follows service and daemon logs without depending on a platform-specific `tail` command. Use `hermeslink logs --error -n 20`, `hermeslink logs --warn -n 50`, or `hermeslink logs --level debug` to choose the displayed severity. `hermeslink logs flush` clears active and rotated service/daemon logs; use `hermeslink logs flush --all` to include Gateway logs. A paired App can read the same service log stream through `GET /api/v1/logs` using the normal Link access token.
+
+Hermes Link also maintains a small Hermes skill under `~/.hermeslink/hermes-skills/hermes-link/SKILL.md`. On start, successful pairing, and Profile creation, Link registers `~/.hermeslink/hermes-skills` in each existing Hermes Profile's `skills.external_dirs`, so Hermes can understand what Hermes Link is and help diagnose HermesPilot mobile connection issues.