bablobanov

Read-only Hermes status dashboard kept in one pinned Telegram message and edited in place on a schedule through the gateway's own Telegram adapter: gateway health, message freshness, last state.db backup, config drift, Claude, Codex, Grok and Kimi account limits, and the running Hermes version against the latest upstream release. HTML when the adapter takes it, plain text otherwise; no LLM calls, no tools or hooks; the screen text is English. Disclosure — Claude and Codex limits come from Hermes' own account-usage fetcher, called every tick (which, like /usage, may refresh OAuth tokens through Hermes' own auth code); at most once per limits_refresh_seconds (default 900 s) the Grok weekly pool is read from https://cli-chat-proxy.grok.com/v1/billing and /v1/settings with the xai-oauth token Hermes resolves, sending the header x-xai-token-auth xai-grok-cli that identifies the request as the Grok CLI (an undocumented xAI host Hermes itself does not use), and Kimi Code windows from the kimi-coding base URL /v1/usages with the kimi-coding key Hermes resolves and a User-Agent of claude-code/0.1.0 (undocumented provider surfaces); the plugin never reads the Telegram bot token itself and never writes vendor credential files; the latest Hermes release list is read from api.github.com without a token at most once a day; an operator-configured drift_command, if set, runs as a subprocess; the delivery record is written under HERMES_HOME/plugin-data/.