Alan's Way Plugin

Good to know before installing

Once the gateway connects Telegram, a background thread checks every 60 seconds. When the bound Telegram DM has been quiet (2 h by default, doubling per unanswered check-in, 08:00-22:00 user time), it injects an internal user-role prompt into that chat (needs plugins.entries.alans-way.allow_gateway_injection, which setup sets), so the bot runs a turn on its own and may take one "safe, reversible" step; the user still approves tool calls in Telegram. Its pre_llm_call/post_llm_call hooks see every session's turns and store the bound chat's activity timestamps in plugin state; optional cross-bot export adds the separate storage disclosed below. On first load it reads $HERMES_HOME/companion/proactivity/proactivity.sqlite3 once, read-only. The plugin itself makes no network calls. The workspace-setup skill has the agent fetch this repo at the catalog pin into ~/alans-way-agents (or reuse a clean clone there) and hand a JSON setup plan to the human in Alan's Workspace. The app runs setup.sh through an external SSH process outside the gateway, checks the exact repoRef and desktopRef and rejects tracked checkout changes; the agent must never run setup or even --verify in its gateway termin

From the plugin's catalog listing.