The agent that grows with you
Python aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexhermeshermes-agentllmnous-researchopenai
plugin-catalog: update both Alan's Way plugin pins and disclosures
capthvnsen6d77cc14faa9
diff --git a/plugin-catalog/alans-way-computer.yaml b/plugin-catalog/alans-way-computer.yamlindex 5458b3bcb72..b25d59c39c1 100644--- a/plugin-catalog/alans-way-computer.yaml+++ b/plugin-catalog/alans-way-computer.yaml@@ -1,6 +1,6 @@name: alans-way-computerrepo: https://github.com/capthvnsen/alans-way-agents-sha: 0a61eb66894a00bf2e8a8091359ffb9bcf196a70+sha: ebcac96f41f3af1ab4a1ebf70ba72eb35efc6c60subdir: alans-way-computerversion: "0.21.6"title: "Alan's Way Plugin: Computer Use"@@ -9,17 +9,18 @@ maintainer: capthvnsentier: communitycategory: toolsrequires_hermes: ">=0.21.5"-docs_url: https://github.com/capthvnsen/alans-way-agents/tree/0a61eb66894a00bf2e8a8091359ffb9bcf196a70/alans-way-computer+docs_url: https://github.com/capthvnsen/alans-way-agents/tree/ebcac96f41f3af1ab4a1ebf70ba72eb35efc6c60/alans-way-computerreadme: trueplatforms: [linux, macos]known_issues:- - "Needs a Hermes build with the pluggable computer-use API (merged to main after 0.21.5). On older Hermes the plugin installs and does nothing. Install alans-way first and run its workspace setup, which writes the workspace_browser block this provider reuses."- - "Hermes asks for approval on every computer_use action type until it is granted. For an unattended Telegram bot, grant them once with Always in Telegram, or add cua:<action>:background entries to command_allowlist (see the README). Takes effect after a gateway restart."- - "Runs only in the plugin host: it cannot load under plugins.isolation: host, because the provider hands Hermes a live router session."- - "Typing without a target field works only on the VM's own desktop, where it types at the focused window (still approval-gated). On the user's computer the app never takes focus, so the agent uses set_value on a field instead."- - "The VM desktop path needs xdotool, a screenshot tool (scrot, maim or ImageMagick import), the AT-SPI bus and python3-gi on the VM. Without them those calls fail and the agent reports it; setup.sh warns about what is missing."- - "A default som capture may fetch the window screenshot even when it is omitted from the model after the 35% coverage check. Use mode vision to request it explicitly, or mode ax for an element-only capture. When a screenshot is omitted, coordinate= and element bounds are screen pixels."- - "Mac and Windows action replies update the held element list without shifting surviving numbers. On Linux, capture again before acting by number after a tree change; cut replies do not prove an unseen control is gone. A timeout or hung app can leave the action's outcome uncertain: capture before retrying."+- "Needs a Hermes build with the pluggable computer-use API (merged to main after 0.21.5). On older Hermes the plugin installs and does nothing. Install alans-way first and run its workspace setup, which writes the workspace_browser block this provider reuses."+- "Hermes asks for approval on every computer_use action type until it is granted. For an unattended Telegram bot, grant them once with Always in Telegram, or add cua:<action>:background entries to command_allowlist (see the README). Takes effect after a gateway restart."+- "Runs only in the plugin host: it cannot load under plugins.isolation: host, because the provider hands Hermes a live router session."+- "Typing without a target field works only on the VM's own desktop, where it types at the focused window (still approval-gated). On the user's computer the app never takes focus, so the agent uses set_value on a field instead."+- "The VM desktop path needs xdotool, a screenshot tool (scrot, maim or ImageMagick import), the AT-SPI bus and python3-gi on the VM. Without them those calls fail and the agent reports it; setup.sh warns about what is missing."+- "A default som capture may fetch the window screenshot even when it is omitted from the model after the 35% coverage check. Use mode vision to request it explicitly, or mode ax for an element-only capture. When a screenshot is omitted, coordinate= and element bounds are screen pixels."+- "Mac and Windows action replies update the held element list without shifting surviving numbers. On Linux, capture again before acting by number after a tree change; cut replies do not prove an unseen control is gone. A timeout or hung app can leave the action's outcome uncertain: capture before retrying."+- The provider implementation is unchanged by this re-pin. It is pinned alongside alans-way because it uses the configured workspace router; this catalog update does not independently establish remote end-to-end compatibility.capabilities:provides_tools: []provides_hooks: []diff --git a/plugin-catalog/alans-way.yaml b/plugin-catalog/alans-way.yamlindex a58f58d6b2e..ef084c4187e 100644--- a/plugin-catalog/alans-way.yaml+++ b/plugin-catalog/alans-way.yaml@@ -1,40 +1,40 @@name: alans-wayrepo: https://github.com/capthvnsen/alans-way-agents-sha: 0a61eb66894a00bf2e8a8091359ffb9bcf196a70+sha: ebcac96f41f3af1ab4a1ebf70ba72eb35efc6c60subdir: alans-wayversion: "0.21.6"title: "Alan's Way Plugin"-description: "Idle check-ins from the primary bot of a Hermes gateway on a Linux machine or a macOS guest VM: when the bound Telegram chat has been quiet for two hours, during 08:00-22:00 in the user's timezone, the bot checks in once (does one safe step and reports it, suggests one, or asks one question), backing off when unanswered. The model tool can only make check-ins quieter; more often, resume and wider hours are operator-only via /proactivity or the CLI. After install, the workspace-setup skill walks the agent through setting up Alan's Workspace (a separate desktop app for the user's computer: macOS or Windows) and Tailscale; desktop input goes only through Hermes's approval-gated computer_use tool. Disclosure — 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 only the bound chat's timestamps in plugin state. 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 run setup.sh, which does the following. (1) Installs long-running services (Alan's Tools: a managed Chrome/Chromium on a loopback-only debugging port, the first free port from 9223 up, plus a browser broker and an optional availability watcher): systemd units hermes-alans-way-chromium, -browser and mac-watch with loginctl enable-linger where systemd is running; supervisord programs alans-way-chromium, alans-way-browser and alans-way-mac-watch, written to a conf.d file, where it is not (VM images and containers); a KeepAlive LaunchAgent on a macOS guest; logon Scheduled Tasks on Windows. When no X display is running it also installs and runs Xvfb on :99 (unit hermes-alans-way-xvfb or program alans-way-xvfb, -nolisten tcp). (2) Installs packages when they are missing, only as root or with passwordless sudo, through apt, dnf or yum: Google Chrome stable (the current .deb downloaded from dl.google.com on amd64 apt hosts, which also adds Google's apt repository, so the host keeps taking Chrome updates from Google), else the distro chromium package, else Playwright 1.49.1 Chromium through npx (root only); and xvfb. It only warns, and installs nothing, for xdotool, scrot, at-spi2-core and python3-gi, which the VM desktop path needs. (3) Appends the user's computer's public key to ~/.ssh/authorized_keys (administrators_authorized_keys on a Windows admin account) with a from= restriction to the Tailscale ranges 100.64.0.0/10 and fd7a:115c:a1e0::/48, rewriting an existing unrestricted line for the same key; pins its host key in known_hosts and adds a ControlMaster block to ~/.ssh/config for Tailscale hosts only (with a tailscale nc ProxyCommand when Tailscale runs in userspace-networking mode). (4) Adds a TimeoutStartSec=180 drop-in to the hermes-gateway unit. Hermes refuses plugin file changes while a gateway is running, so setup drain-stops that profile's gateway (SIGUSR1 under supervisord, else systemctl stop or hermes gateway stop), replays the refused plugin install or update, and starts it again. With --restart it restarts the gateway only if setup changed something the gateway loads (or an earlier restart never happened), detached about ten seconds after printing its summary: by SIGUSR1 drain under supervisord, else a transient systemd-run timer or hermes gateway restart. (5) For the main profile and every profile with its own Telegram bot, writes a managed mcp_servers.workspace_browser block (removing other entries that run this router, with a backup; a re-run keeps the computer address and OS it already holds, and --mac-ssh none- removes them), turns off the built-in browser toolset for Telegram and cron (--keep-browser leaves it on), turns computer_use on for Telegram and cron, and sets computer_use.backend to alans-way-computer when it installed or found that provider (under the skill's --skip-plugin flow it only warns and prints the config command). It reads each profile's TELEGRAM_BOT_TOKEN only to derive the numeric bot id. It warns, and changes nothing, when a copy of the workspace-operations skill in a profile's skills directory shadows the plugin's. The workspace router reaches the user's computer over SSH on their tailnet; on the user's computer it calls the local API of Alan's Workspace on 127.0.0.1 with that app's bearer token. The skill's moved-VM checklist has the agent read the app's preferences.json on the user's computer over the same SSH path and tell the human where the VNC password lives without pasting it. The Alan's Workspace setup page has the human run the alans-way connect script from its main branch on their own computer, and the agent may install Tailscale with its official install script. The manual --allow-desktop-actions setup flag, which the skill offers but never adds itself, adds cua:*:background entries to command_allowlist. On a Hermes without the computer-use provider API, including 0.21.5, it also exposes workspace_computer_action, which drives the user's desktop, Terminal included, with no approval. The repo also holds bootstrap-orgo.sh and migrate.sh, which the plugin, setup.sh and the skills never run: a user runs them by hand to provision a fresh supervisord Linux computer (it fetches the Hermes and Tailscale installers over HTTPS, pipes setup.sh from this repo's main branch into bash unless --repo-ref is given, installs openssh-server if absent, writes supervisord programs, and POSTs the Tailscale login URL with a shared secret to a --callback URL when one is given) or to copy ~/.hermes, including .env, auth.json and state.db, to another host over SSH (it also looks up each profile's bot username at api.telegram.org with that profile's bot token). Since 0.21.0, every enabled profile also gets a default-on Telegram texting voice: an additional pre_llm_call hook reads that profile's voice mode and adds a tone note to Telegram turns, and transform_llm_output can remove a known leading assistant opener from the final Telegram reply. Messages containing backticks, quotes, indentation or silence markers are left unchanged by that polish. /tone texting|default|status and hermes tone store the mode under voice in Hermes plugin state; setup.sh --tone applies it to each configured profile. It layers over the user's persona without writing SOUL.md or agent.system_prompt. Check-ins now name one concrete open thread. /proactivity now requests one immediately from the bound chat even when paused or outside active hours, without changing the settings or unanswered-check-in count. Morning briefs are off by default: /proactivity brief on (or the operator CLI) enables one daily internal user-role prompt near active_start, with 0-20 minutes of jitter, at most two hours late and skipped after recent user activity. It asks the model to consult calendar and email read-only if those tools exist. The existing proactivity tool may disable the brief but cannot enable it; settings.morning_brief and last_brief_date are stored in the existing idle plugin state. The workspace router adds a commit object to the existing browser open/action tools for purchases, bookings, sends, posts, submissions, deletions and account changes. It checks control names, selectors, refs, action-looking URLs, batches, scripts, keys and dialogs against page state; missing page knowledge needs a snapshot or explicit commit. Shared commit-name patterns allow benign Buy it again, Book a demo and Subscribe & Save labels without excusing other commit-bearing words. It asks through MCP elicitation (60-second default wait, configurable with HERMES_ROUTER_APPROVAL_MS), refuses unavailable, declined, timed-out or stale approvals, drops agent-supplied approval receipts and adds a single-use receipt bound to the approved tab and epoch. An approved commit is never replayed after a lost connection or host change. It appends commit decisions to commit-decisions.jsonl beside the mac-watch state file, creating the log with mode 0600: timestamp, bot id, page origin, decision and any supplied kind, summary, amount, currency and counterparty, or the detected target. Page/control/challenge and pending-approval state is held in memory. The same two skills now prefer Hermes web_search/web_extract for plain lookups and the user's computer for interactive search, hand CAPTCHAs to the human, poll at most every 30 seconds for up to 30 minutes, and switch sources after two challenges in ten minutes. The router stops remembering challenge pages for failover and reports changed tab ids in result metadata. The operations skill covers the app's automatic takeover after its grace period; CAPTCHA and recording holds and Take-back cooldowns still keep the bot out. It also asks the agent to save durable facts and preferences to memory, never live tab state. The setup skill pins the companion app source to a82f5010248455600acfe275010e3e725355a2a8 and adds a long-chat reference: report effective compression and summary routing read-only, then only with explicit consent for each profile enable compression.proactive_prune_tokens at 48000, with 8000-character eligibility and 4096-token minimum reclaim, using the profile-scoped config CLI and keeping custom values, micro_compact and summary routing. This writes the approved profile's config.yaml and records prior values outside the repo for undo; setup.sh does not run it. A weekly time-saved report is a user-created Hermes cron recipe, not an installed job. setup.sh --verify now checks the running service manager, display, SSH ProxyCommand and managed browser's loopback /json/version endpoint, and reports noVNC reachability from its actual bind address. Manual supervisord restart guidance drains with USR1 first. The repo also adds scripts/voice_eval.py, user-run only: it sends fixed fictional scenarios and replies to Anthropic models through the SDK or claude -p for scoring and optionally writes a JSON result; the plugin, setup and skills never run it. Since 0.21.5, the plugin registers two more bundled skills, web-errands and integrations, with no new tools, hooks, commands or required environment variables. web-errands is guidance for shopping, booking, applications, filings, cancellations and claims in the workspace browser: every purchase, booking, send, submission and deletion still goes through the commit approval gate described above, CAPTCHA, sign-in and card-entry walls go back to the human, and card numbers are never stored. It has the agent record each application's company, role, date and posting URL in Hermes memory. For a price, restock or status watch the user asks for, it has the agent create a Hermes cron job with Hermes's cronjob_manage tool (or ask the operator), polling no more often than every 10 minutes and stopping after three consecutive failures; cron runs cannot answer approvals, so a watch that reaches its target stages the result for the user. The integrations skill has the agent check that an account is connected, with a small read, before promising a task that needs it, and reuses Hermes's Google Workspace, Himalaya, Home Assistant, Honcho and X routes first. The Google route uses Hermes's own setup, whose fixed scope list includes write access; the skill says so and stops if the user declines. Only after the user agrees in chat does it guide an install: a Hermes catalog plugin (Home Assistant or Honcho), a separately reviewed Himalaya v1.2.0 binary, rclone v1.75.2 (the release zip from downloads.rclone.org, checked against that release's SHA256SUMS before extraction) or Taskwarrior 3.5.0 (a source build of upstream commit 3419d5ba1e6a780fbbb0a8d68d8fd31e675c1bf8 cloned from GitHub, after checking the CMake and Rust versions and asking before changing any toolchain), the last two into versioned directories under ~/.local/share/alans-tools/. Secrets are entered by the human in a private terminal outside the agent session, never in Telegram; where a recipe needs a secret in the agent's terminal (a mail credential, RCLONE_CONFIG_PASS), it explains the grant and adds only that variable to the profile's terminal.env_passthrough. The recipes keep rclone.conf (mode 0600) and Taskwarrior's taskrc and data under the profile's HERMES_HOME/integrations. Scheduled reads are read-only cron jobs with a profile-local failure-count file, and pausing goes through the owner conversation or an explicitly authorized hermes cron pause. API writes (send, post, delete, share) need fresh explicit approval in the live conversation, and a declined, timed-out or unavailable browser commit is never completed through another tool. Mastodon is not bundled: its recipe is human-run documentation in this repo (docs/integrations/mastodon.md) that the plugin and skills never run. None of this runs at plugin load or from setup.sh. Telegram replies, check-ins and briefs share one status-first style: concrete status, evidence or caveat, plain limits, and no tool names, file paths, scripts or job and session IDs in user-facing text unless asked. Prices, availability and policies must come from a page read this turn or be labeled unconfirmed. Multi-step browser work runs in short chunks of about two actions with at most one plain progress update per chunk, a new mid-task message is acknowledged and folded in, and Hermes's clarify buttons may be used for decisions the user owns, never for approvals; a whole checkout batch still sits under one commit. For a message of 200 characters or fewer that is wholly a recap request, greeting, thanks or acknowledgment, the voice hook appends a three-sentence limit; the check reads only the current message, with no model call, history or network. The check-in menu now ends with asking about a decision the user owns. The operations skill adds tab hygiene: the agent closes finished tabs it owns with the existing close tool, never another bot's or the user's and never one with a pending handback or recording hold. The router adds requestingBotId to tab-list replies and forwards a reply over 4 MiB unchanged, without that decoration, writing a content-free line to stderr. The skill also tells the agent to report installed versions by running hermes --version, reading the plugin's install metadata, running local git describe and rev-parse on the Alan's Tools checkout, and calling the app's existing status tool. setup.sh --bind now also makes the bound DM Hermes's Telegram home by running hermes -p PROFILE config set for TELEGRAM_HOME_CHANNEL and TELEGRAM_HOME_CHANNEL_THREAD_ID (30-second limit each; on failure it warns to send /sethome); it loads on gateway restart. setup.sh --verify exits 0 for a complete local audit, 1 for failed required checks and 2 for a partial install (warnings, or skipped browser or services). The setup skill's checkout step now initializes ~/alans-way-agents if absent and fetches the pin (depth 1) from the repo's GitHub origin, or reuses a clean clone there after two read-only local git helpers (5-second limit) confirm one recorded and effective origin URL naming this repo; for file and direct Git installs it uses the installer-recorded revision, and it never falls back to a tag when that record is invalid. Its computer-use API probe separates an absent API from a failed or timed-out probe and ends the probe's process group or tree on timeout. The setup skill also offers, each only after an explicit answer, with readback and a remembered-choice marker in the profile's config: display.busy_input_mode (steer or interrupt, for every platform in that profile; asked once, only when the effective mode is interrupt and no choice is recorded) and one grouped Telegram question covering platforms.telegram.typing_indicator, display.platforms.telegram.interim_assistant_messages, tool_progress, notifications, long_running_notifications and busy_steer_ack_enabled, platforms.telegram.reactions, display.memory_notifications (hides the Memory updated and Self-improvement review notices on every platform in that profile), cron.wrap_response (profile-wide: removes scheduled-message headers, job IDs and footers for all delivery targets) and, as a separate city-confirmed question, timezone. Markers written through the same CLI are skills.config.workspace-setup.busy_input_choice and telegram_feel_choice; a legacy busy_steer_ack_choice marker is only read, never written. Silence and non-interactive runs write nothing, and neither setup script writes any of these keys. When the VNC viewer binds loopback only, the skill can, with explicit consent, have the human run a temporary SSH forward to the computer's loopback (local port 16080, ends after 30 minutes) and verify it with curl from that computer. For a manual or file install it explains the Hermes scanner result and, only after explicit consent to the exact reviewed revision, may retry hermes plugins install with --ref SHA --enable --force; --force confirms a caution verdict and cannot override a dangerous one. Hermes's unmodified scanner reports SAFE for this plugin: 0 HIGH, 2 MEDIUM (python_subprocess: the two git helpers in skills/workspace-setup/SKILL.md) and 3 LOW (hardcoded_ip_port: the loopback forward examples in the same file)."+description: "Idle check-ins from the primary bot of a Hermes gateway on a Linux machine or a macOS guest VM: when the bound Telegram chat has been quiet for two hours, during 08:00-22:00 in the user's timezone, the bot checks in once (does one safe step and reports it, suggests one, or asks one question), backing off when unanswered. The model tool can only make check-ins quieter; more often, resume and wider hours are operator-only via /proactivity or the CLI. After install, the workspace-setup skill walks the agent through setting up Alan's Workspace (a separate desktop app for the user's computer: macOS or Windows) and Tailscale; desktop input goes only through Hermes's approval-gated computer_use tool. Disclosure — 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 only the bound chat's timestamps in plugin state. 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 run setup.sh, which does the following. (1) Installs long-running services (Alan's Tools: a managed Chrome/Chromium on a loopback-only debugging port, the first free port from 9223 up, plus a browser broker and an optional availability watcher): systemd units hermes-alans-way-chromium, -browser and mac-watch with loginctl enable-linger where systemd is running; supervisord programs alans-way-chromium, alans-way-browser and alans-way-mac-watch, written to a conf.d file, where it is not (VM images and containers); a KeepAlive LaunchAgent on a macOS guest; logon Scheduled Tasks on Windows. When no X display is running it also installs and runs Xvfb on :99 (unit hermes-alans-way-xvfb or program alans-way-xvfb, -nolisten tcp). (2) Installs packages when they are missing, only as root or with passwordless sudo, through apt, dnf or yum: Google Chrome stable (the current .deb downloaded from dl.google.com on amd64 apt hosts, which also adds Google's apt repository, so the host keeps taking Chrome updates from Google), else the distro chromium package, else Playwright 1.49.1 Chromium through npx (root only); and xvfb. It only warns, and installs nothing, for xdotool, scrot, at-spi2-core and python3-gi, which the VM desktop path needs. (3) Appends the user's computer's public key to ~/.ssh/authorized_keys (administrators_authorized_keys on a Windows admin account) with a from= restriction to the Tailscale ranges 100.64.0.0/10 and fd7a:115c:a1e0::/48, rewriting an existing unrestricted line for the same key; pins its host key in known_hosts and adds a ControlMaster block to ~/.ssh/config for Tailscale hosts only (with a tailscale nc ProxyCommand when Tailscale runs in userspace-networking mode). (4) Adds a TimeoutStartSec=180 drop-in to the hermes-gateway unit. Hermes refuses plugin file changes while a gateway is running, so setup drain-stops that profile's gateway (SIGUSR1 under supervisord, else systemctl stop or hermes gateway stop), replays the refused plugin install or update, and starts it again. With --restart it restarts the gateway only if setup changed something the gateway loads (or an earlier restart never happened), detached about ten seconds after printing its summary: by SIGUSR1 drain under supervisord, else a transient systemd-run timer or hermes gateway restart. (5) For the main profile and every profile with its own Telegram bot, writes a managed mcp_servers.workspace_browser block (removing other entries that run this router, with a backup; a re-run keeps the computer address and OS it already holds, and --mac-ssh none removes them), turns off the built-in browser toolset for Telegram and cron (--keep-browser leaves it on), turns computer_use on for Telegram and cron, and sets computer_use.backend to alans-way-computer when it installed or found that provider (under the skill's --skip-plugin flow it only warns and prints the config command). It reads each profile's TELEGRAM_BOT_TOKEN only to derive the numeric bot id. It warns, and changes nothing, when a copy of the workspace-operations skill in a profile's skills directory shadows the plugin's. The workspace router reaches the user's computer over SSH on their tailnet; on the user's computer it calls the local API of Alan's Workspace on 127.0.0.1 with that app's bearer token. The skill's moved-VM checklist has the agent read the app's preferences.json on the user's computer over the same SSH path and tell the human where the VNC password lives without pasting it. The Alan's Workspace setup page has the human run the alans-way connect script from its main branch on their own computer, and the agent may install Tailscale with its official install script. The manual --allow-desktop-actions setup flag, which the skill offers but never adds itself, adds cua:*:background entries to command_allowlist. On a Hermes without the computer-use provider API, including 0.21.5, it also exposes workspace_computer_action, which drives the user's desktop, Terminal included, with no approval. The repo also holds bootstrap-orgo.sh and migrate.sh, which the plugin, setup.sh and the skills never run: a user runs them by hand to provision a fresh supervisord Linux computer (it fetches the Hermes and Tailscale installers over HTTPS, pipes setup.sh from this repo's main branch into bash unless --repo-ref is given, installs openssh-server if absent, writes supervisord programs, and POSTs the Tailscale login URL with a shared secret to a --callback URL when one is given) or to copy ~/.hermes, including .env, auth.json and state.db, to another host over SSH (it also looks up each profile's bot username at api.telegram.org with that profile's bot token). Since 0.21.0, every enabled profile also gets a default-on Telegram texting voice: an additional pre_llm_call hook reads that profile's voice mode and adds a tone note to Telegram turns, and transform_llm_output can remove a known leading assistant opener from the final Telegram reply. Messages containing backticks, quotes, indentation or silence markers are left unchanged by that polish. /tone texting|default|status and hermes tone store the mode under voice in Hermes plugin state; setup.sh --tone applies it to each configured profile. It layers over the user's persona without writing SOUL.md or agent.system_prompt. Check-ins now name one concrete open thread. /proactivity now requests one immediately from the bound chat even when paused or outside active hours, without changing the settings or unanswered-check-in count. Morning briefs are off by default: /proactivity brief on (or the operator CLI) enables one daily internal user-role prompt near active_start, with 0-20 minutes of jitter, at most two hours late and skipped after recent user activity. It asks the model to consult calendar and email read-only if those tools exist. The existing proactivity tool may disable the brief but cannot enable it; settings.morning_brief and last_brief_date are stored in the existing idle plugin state. The workspace router adds a commit object to the existing browser open/action tools for purchases, bookings, sends, posts, submissions, deletions and account changes. It checks control names, selectors, refs, action-looking URLs, batches, scripts, keys and dialogs against page state; missing page knowledge needs a snapshot or explicit commit. Shared commit-name patterns allow benign Buy it again, Book a demo and Subscribe & Save labels without excusing other commit-bearing words. It asks through MCP elicitation (60-second default wait, configurable with HERMES_ROUTER_APPROVAL_MS), refuses unavailable, declined, timed-out or stale approvals, drops agent-supplied approval receipts and adds a single-use receipt bound to the approved tab and epoch. An approved commit is never replayed after a lost connection or host change. It appends commit decisions to commit-decisions.jsonl beside the mac-watch state file, creating the log with mode 0600: timestamp, bot id, page origin, decision and any supplied kind, summary, amount, currency and counterparty, or the detected target. Page/control/challenge and pending-approval state is held in memory. The same two skills now prefer Hermes web_search/web_extract for plain lookups and the user's computer for interactive search, hand CAPTCHAs to the human, poll at most every 30 seconds for up to 30 minutes, and switch sources after two challenges in ten minutes. The router stops remembering challenge pages for failover and reports changed tab ids in result metadata. The operations skill covers the app's automatic takeover after its grace period; CAPTCHA and recording holds and Take-back cooldowns still keep the bot out. It also asks the agent to save durable facts and preferences to memory, never live tab state. The setup skill pins the companion app source to a82f5010248455600acfe275010e3e725355a2a8 and adds a long-chat reference: report effective compression and summary routing read-only, then only with explicit consent for each profile enable compression.proactive_prune_tokens at 48000, with 8000-character eligibility and 4096-token minimum reclaim, using the profile-scoped config CLI and keeping custom values, micro_compact and summary routing. This writes the approved profile's config.yaml and records prior values outside the repo for undo; setup.sh does not run it. A weekly time-saved report is a user-created Hermes cron recipe, not an installed job. setup.sh --verify now checks the running service manager, display, SSH ProxyCommand and managed browser's loopback /json/version endpoint, and reports noVNC reachability from its actual bind address. Manual supervisord restart guidance drains with USR1 first. The repo also adds scripts/voice_eval.py, user-run only: it sends fixed fictional scenarios and replies to Anthropic models through the SDK or claude -p for scoring and optionally writes a JSON result; the plugin, setup and skills never run it. Since 0.21.5, the plugin registers two more bundled skills, web-errands and integrations, with no new tools, hooks, commands or required environment variables. web-errands is guidance for shopping, booking, applications, filings, cancellations and claims in the workspace browser: every purchase, booking, send, submission and deletion still goes through the commit approval gate described above, CAPTCHA, sign-in and card-entry walls go back to the human, and card numbers are never stored. It has the agent record each application's company, role, date and posting URL in Hermes memory. For a price, restock or status watch the user asks for, it has the agent create a Hermes cron job with Hermes's cronjob_manage tool (or ask the operator), polling no more often than every 10 minutes and stopping after three consecutive failures; cron runs cannot answer approvals, so a watch that reaches its target stages the result for the user. The integrations skill has the agent check that an account is connected, with a small read, before promising a task that needs it, and reuses Hermes's Google Workspace, Himalaya, Home Assistant, Honcho and X routes first. The Google route uses Hermes's own setup, whose fixed scope list includes write access; the skill says so and stops if the user declines. Only after the user agrees in chat does it guide an install: a Hermes catalog plugin (Home Assistant or Honcho), a separately reviewed Himalaya v1.2.0 binary, rclone v1.75.2 (the release zip from downloads.rclone.org, checked against that release's SHA256SUMS before extraction) or Taskwarrior 3.5.0 (a source build of upstream commit 3419d5ba1e6a780fbbb0a8d68d8fd31e675c1bf8 cloned from GitHub, after checking the CMake and Rust versions and asking before changing any toolchain), the last two into versioned directories under ~/.local/share/alans-tools/. Secrets are entered by the human in a private terminal outside the agent session, never in Telegram; where a recipe needs a secret in the agent's terminal (a mail credential, RCLONE_CONFIG_PASS), it explains the grant and adds only that variable to the profile's terminal.env_passthrough. The recipes keep rclone.conf (mode 0600) and Taskwarrior's taskrc and data under the profile's HERMES_HOME/integrations. Scheduled reads are read-only cron jobs with a profile-local failure-count file, and pausing goes through the owner conversation or an explicitly authorized hermes cron pause. API writes (send, post, delete, share) need fresh explicit approval in the live conversation, and a declined, timed-out or unavailable browser commit is never completed through another tool. Mastodon is not bundled: its recipe is human-run documentation in this repo (docs/integrations/mastodon.md) that the plugin and skills never run. None of this runs at plugin load or from setup.sh. Telegram replies, check-ins and briefs share one status-first style: concrete status, evidence or caveat, plain limits, and no tool names, file paths, scripts or job and session IDs in user-facing text unless asked. Prices, availability and policies must come from a page read this turn or be labeled unconfirmed. Multi-step browser work runs in short chunks of about two actions with at most one plain progress update per chunk, a new mid-task message is acknowledged and folded in, and Hermes's clarify buttons may be used for decisions the user owns, never for approvals; a whole checkout batch still sits under one commit. For a message of 200 characters or fewer that is wholly a recap request, greeting, thanks or acknowledgment, the voice hook appends a three-sentence limit; the check reads only the current message, with no model call, history or network. The check-in menu now ends with asking about a decision the user owns. The operations skill adds tab hygiene: the agent closes finished tabs it owns with the existing close tool, never another bot's or the user's and never one with a pending handback or recording hold. The router adds requestingBotId to tab-list replies and forwards a reply over 4 MiB unchanged, without that decoration, writing a content-free line to stderr. The skill also tells the agent to report installed versions by running hermes --version, reading the plugin's install metadata, running local git describe and rev-parse on the Alan's Tools checkout, and calling the app's existing status tool. setup.sh --bind now also makes the bound DM Hermes's Telegram home by running hermes -p PROFILE config set for TELEGRAM_HOME_CHANNEL and TELEGRAM_HOME_CHANNEL_THREAD_ID (30-second limit each; on failure it warns to send /sethome); it loads on gateway restart. setup.sh --verify exits 0 for a complete local audit, 1 for failed required checks and 2 for a partial install (warnings, or skipped browser or services). The setup skill's checkout step now initializes ~/alans-way-agents if absent and fetches the pin (depth 1) from the repo's GitHub origin, or reuses a clean clone there after two read-only local git helpers (5-second limit) confirm one recorded and effective origin URL naming this repo; for file and direct Git installs it uses the installer-recorded revision, and it never falls back to a tag when that record is invalid. Its computer-use API probe separates an absent API from a failed or timed-out probe and ends the probe's process group or tree on timeout. The setup skill also offers, each only after an explicit answer, with readback and a remembered-choice marker in the profile's config: display.busy_input_mode (steer or interrupt, for every platform in that profile; asked once, only when the effective mode is interrupt and no choice is recorded) and one grouped Telegram question covering platforms.telegram.typing_indicator, display.platforms.telegram.interim_assistant_messages, tool_progress, notifications, long_running_notifications and busy_steer_ack_enabled, platforms.telegram.reactions, display.memory_notifications (hides the Memory updated and Self-improvement review notices on every platform in that profile), cron.wrap_response (profile-wide: removes scheduled-message headers, job IDs and footers for all delivery targets) and, as a separate city-confirmed question, timezone. Markers written through the same CLI are skills.config.workspace-setup.busy_input_choice and telegram_feel_choice; a legacy busy_steer_ack_choice marker is only read, never written. Silence and non-interactive runs write nothing, and neither setup script writes any of these keys. When the VNC viewer binds loopback only, the skill can, with explicit consent, have the human run a temporary SSH forward to the computer's loopback (local port 16080, ends after 30 minutes) and verify it with curl from that computer. For a manual or file install it explains the Hermes scanner result and, only after explicit consent to the exact reviewed revision, may retry hermes plugins install with --ref SHA --enable --force; --force confirms a caution verdict and cannot override a dangerous one. Hermes's unmodified scanner reports SAFE for this plugin: 0 HIGH, 2 MEDIUM (python_subprocess: the two git helpers in skills/workspace-setup/SKILL.md) and 3 LOW (hardcoded_ip_port: the loopback forward examples in the same file). This pin also extends the existing texting-note and minimal final-opener polish to public session source tags desktop, tui and bot_room, alongside Telegram; CLI, cron, webhook and API-server sources keep their default voice. Routine work is instructed to stay quiet while preserving essential questions, approvals, failures and honest completion. Fixed Hermes progress/error/approval messages are unchanged. Scripted tool conversations prove hook delivery; consistent real-model quiet behavior is unverified. Router changes bind approvals to exact observed page targets, reject missing/malformed action success receipts, bound recovery and owned-child shutdown, and project agent-facing replies without exposing internal approval proof. No new tools, hook names, middleware, required secrets or network destinations are introduced."maintainer: capthvnsentier: communitycategory: automationrequires_hermes: ">=0.21.5"-docs_url: https://github.com/capthvnsen/alans-way-agents/tree/0a61eb66894a00bf2e8a8091359ffb9bcf196a70/alans-way+docs_url: https://github.com/capthvnsen/alans-way-agents/tree/ebcac96f41f3af1ab4a1ebf70ba72eb35efc6c60/alans-wayreadme: trueplatforms: [linux, macos]known_issues:- - "Install this on the machine that runs Hermes (a Linux host or a macOS guest VM), not on the user's primary computer. Windows guests are new and untested on real hardware. If the plugin is already installed from the catalog, setup leaves it as it is, so this pin stays."- - "Setup turns off Hermes's stock browser toolset for Telegram and cron so the agent uses the workspace browser (pass --keep-browser to leave it on). It never turns off computer_use: on Hermes with the computer-use provider API, desktop input goes through the gated computer_use tool and its alans-way-computer provider."- - "Check-ins need plugins.entries.alans-way.allow_gateway_injection: true and a bound Telegram DM (setup does both). A background thread checks every 60 seconds once the gateway connects Telegram."- - "Setup may install Chrome, Chromium, Playwright's Chromium or Xvfb with root or passwordless sudo, and may drain-stop and start the profile's gateway to apply a plugin change Hermes refuses while it runs. Pass --skip-services to skip the services and their packages."- - "The computer's SSH key is only accepted from the tailnet (from= restriction). An existing unrestricted line for the same key is rewritten with it."- - "A copy of the workspace-operations skill under a profile's skills directory shadows the plugin's and never gets its updates. Setup only warns; move anything worth keeping out of it, then delete it."- - "The Telegram texting voice is on by default in every enabled profile. /tone default turns off its note and final-reply polish; check-ins and morning briefs keep their own short style. Fixed Hermes approval/error/progress messages, direct sends and cron reports are outside these hooks; interim messages get the tone note but no polish, and streaming may show raw chunks before the final edit."- - "Morning briefs are opt-in (/proactivity brief on), use the existing bound DM and gateway-injection permission, and may read calendar/email through tools already available to the model. /proactivity now is user-only from that chat and bypasses pause/hours for one requested check-in."- - "Telegram browser Approve buttons need Hermes v0.21.6 or newer including commit 239740a19e (first in date tag v2026.6.19), despite the generic >=0.21.5 install floor. Without MCP form elicitation support commits fail with approval_unavailable; unattended cron declines them. The gate protects against agent mistakes and malicious pages, not a deliberately hostile bot with same-user terminal/file access."- - "The router appends approval details and detected targets to commit-decisions.jsonl beside mac-watch state, shared by routers using that path; no retention or rotation is implemented. Keep this local log private. CAPTCHA handback, recording holds and Take-back cooldowns still block takeover. If the router reports human_has_control before a commit approval, wait or claim the tab through the normal app control flow first."- - "Long-chat pruning is an agent-guided, separately consented config option per profile, not a setup.sh default. It preserves customized values and summary routing, rewrites sent history and can break the prompt-cache prefix; undo affects future pruning and cannot restore tool bodies already pruned from active context."- - "web-errands and integrations are agent guidance, not setup steps. Any Himalaya, rclone, Taskwarrior, Home Assistant or Honcho install happens only after the user agrees in chat, never from setup.sh or plugin load. Taskwarrior is built from source (CMake >=3.24, Rust >=1.91.1 and several GiB of temporary space). The Google Workspace route requests Hermes's fixed scope list, which includes write access."- - "Guided setup can change a profile's busy-input, Telegram display, notification, reaction, memory-notice, cron-wrapping and timezone settings, but only after explicit answers. Busy mode, memory-notice hiding, cron.wrap_response and timezone reach beyond Telegram within that profile. Silence and non-interactive runs write nothing; neither setup script writes these keys."- - "setup.sh --bind also sets TELEGRAM_HOME_CHANNEL for the bound profile through hermes config set and clears TELEGRAM_HOME_CHANNEL_THREAD_ID; it loads on gateway restart. If that fails, send /sethome in the primary DM."- - "Desktop control needs a Hermes with tools.computer_use.backend.ComputerUseProvider (commit 63f5e0ea45726c5d8d7d207d140613997730aab3 or newer); a version string alone does not prove it. setup.sh --verify exits 2, not 0, for a partial install."+- "Install this on the machine that runs Hermes (a Linux host or a macOS guest VM), not on the user's primary computer. Windows guests are new and untested on real hardware. If the plugin is already installed from the catalog, setup leaves it as it is, so this pin stays."+- "Setup turns off Hermes's stock browser toolset for Telegram and cron so the agent uses the workspace browser (pass --keep-browser to leave it on). It never turns off computer_use: on Hermes with the computer-use provider API, desktop input goes through the gated computer_use tool and its alans-way-computer provider."+- "Check-ins need plugins.entries.alans-way.allow_gateway_injection: true and a bound Telegram DM (setup does both). A background thread checks every 60 seconds once the gateway connects Telegram."+- "Setup may install Chrome, Chromium, Playwright's Chromium or Xvfb with root or passwordless sudo, and may drain-stop and start the profile's gateway to apply a plugin change Hermes refuses while it runs. Pass --skip-services to skip the services and their packages."+- "The computer's SSH key is only accepted from the tailnet (from= restriction). An existing unrestricted line for the same key is rewritten with it."+- "A copy of the workspace-operations skill under a profile's skills directory shadows the plugin's and never gets its updates. Setup only warns; move anything worth keeping out of it, then delete it."+- "The texting voice is default-on for Telegram, desktop, TUI and bot_room source tags. /tone default disables its note and final-opener polish per profile. CLI, cron, webhook and API-server sources retain the default voice. Fixed Hermes progress/error/approval messages are outside these hooks; streaming can show raw chunks before a final edit. Quiet real-model task behavior has not passed end-to-end evaluation."+- "Morning briefs are opt-in (/proactivity brief on), use the existing bound DM and gateway-injection permission, and may read calendar/email through tools already available to the model. /proactivity now is user-only from that chat and bypasses pause/hours for one requested check-in."+- "Telegram browser Approve buttons need Hermes v0.21.6 or newer including commit 239740a19e (first in date tag v2026.6.19), despite the generic >=0.21.5 install floor. Without MCP form elicitation support commits fail with approval_unavailable; unattended cron declines them. The gate protects against agent mistakes and malicious pages, not a deliberately hostile bot with same-user terminal/file access."+- "The router appends approval details and detected targets to commit-decisions.jsonl beside mac-watch state, shared by routers using that path; no retention or rotation is implemented. Keep this local log private. CAPTCHA handback, recording holds and Take-back cooldowns still block takeover. If the router reports human_has_control before a commit approval, wait or claim the tab through the normal app control flow first."+- "Long-chat pruning is an agent-guided, separately consented config option per profile, not a setup.sh default. It preserves customized values and summary routing, rewrites sent history and can break the prompt-cache prefix; undo affects future pruning and cannot restore tool bodies already pruned from active context."+- "web-errands and integrations are agent guidance, not setup steps. Any Himalaya, rclone, Taskwarrior, Home Assistant or Honcho install happens only after the user agrees in chat, never from setup.sh or plugin load. Taskwarrior is built from source (CMake >=3.24, Rust >=1.91.1 and several GiB of temporary space). The Google Workspace route requests Hermes's fixed scope list, which includes write access."+- "Guided setup can change a profile's busy-input, Telegram display, notification, reaction, memory-notice, cron-wrapping and timezone settings, but only after explicit answers. Busy mode, memory-notice hiding, cron.wrap_response and timezone reach beyond Telegram within that profile. Silence and non-interactive runs write nothing; neither setup script writes these keys."+- "setup.sh --bind also sets TELEGRAM_HOME_CHANNEL for the bound profile through hermes config set and clears TELEGRAM_HOME_CHANNEL_THREAD_ID; it loads on gateway restart. If that fails, send /sethome in the primary DM."+- "Desktop control needs a Hermes with tools.computer_use.backend.ComputerUseProvider (commit 63f5e0ea45726c5d8d7d207d140613997730aab3 or newer); a version string alone does not prove it. setup.sh --verify exits 2, not 0, for a partial install."+- This pin needs the paired workspace/remote browser host with approval-binding-v1 support for approved browser actions. Older hosts fail closed when that proof is unavailable; update and verify the paired workspace before rollout.capabilities:provides_tools:- - proactivity+ - proactivityprovides_hooks:- - pre_llm_call- - post_llm_call- - transform_llm_output+ - pre_llm_call+ - post_llm_call+ - transform_llm_outputprovides_middleware: []requires_env: []