Files
hermes-agent/hermes_cli
teknium1 7a99c4d13c fix(send): the 'not configured' error lists the home and sources it consulted
The error now names the resolved home's `.env` (and whether the platform's
token key is defined there), `config.yaml` (block absent / `enabled: false` /
no token) and the environment variable(s) checked, so a Windows or profile
home user can fix the file this process actually read. When a gateway started
from the same home already has the platform connected, the message says its
token lives only in that process's environment and which key to add to `.env`.

Docstrings in `gateway/channel_directory.py` and `send_cmd._load_hermes_env`
stop naming `~/.hermes`; the pipe-script-output guide documents the message.
2026-09-18 10:11:14 -07:00
..
…
…
…
…
…
…
…