Skip to content

The agent that grows with you

chore(plugin-catalog): re-pin the hermes-windows-* entries to 5bad3fb

Yicheng-Marke1f356c10f01
diff --git a/plugin-catalog/hermes-dpapi-secrets.yaml b/plugin-catalog/hermes-dpapi-secrets.yaml
index 4622c88d9d1..b2b6a0492de 100644
--- a/plugin-catalog/hermes-dpapi-secrets.yaml
+++ b/plugin-catalog/hermes-dpapi-secrets.yaml
@@ -1,6 +1,6 @@
name: hermes-dpapi-secrets
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: dpapi-secrets
description: "Resolve Hermes environment variables at startup from a single secret file encrypted with the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.dpapi.map, an ENV_VAR -> store-name mapping (bare names or dpapi:// names) plus an optional file path (default <HERMES_HOME>/secrets.dpapi). The file is one DPAPI blob keyed by the current Windows user profile, so it is unreadable by another Windows account and worthless off the machine; it is written by the bundled CLI (python -m hermes_dpapi_secrets set NAME, value read from a prompt or stdin, never from argv) and only read at runtime. Mapped names that are missing or empty are skipped with a warning; a file that is not ours, a blob this user cannot decrypt, or a payload that is not a flat string map is reported as an error with nothing injected. Disclosure - this source decrypts a file for every Hermes process that enables it: resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. User-scope encryption only (the machine-wide flag is never used and is not exposed), and the at-rest protection is a bar for backups, cloud sync and dotfiles, not a boundary against code already running as the same user. Stdlib-only (ctypes): no Python dependencies, no subprocesses, no network calls, no self-update. Windows only. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — decrypts a DPAPI-encrypted secret file (default <HERMES_HOME>/secrets.dpapi) at startup for every Hermes process that enables it, and the resolved values become environment variables of Hermes and its child processes like `.env` entries; the encryption is per Windows user and protects backups, cloud sync and copied files, not against other code running as the same user. Local only: no network calls, no subprocesses."
maintainer: Yicheng-Mark
diff --git a/plugin-catalog/hermes-wincred.yaml b/plugin-catalog/hermes-wincred.yaml
index 56f99afa256..c3ee785cacb 100644
--- a/plugin-catalog/hermes-wincred.yaml
+++ b/plugin-catalog/hermes-wincred.yaml
@@ -1,6 +1,6 @@
name: hermes-wincred
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: wincred
description: "Resolve Hermes environment variables from the current user's Windows Credential Manager at startup, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.wincred.map, an ENV_VAR -> generic-credential-target mapping (bare names or wincred:// names); each value is read with CredReadW in the current user's vault and handed to the secret-source orchestrator, which applies it with the usual precedence, provenance and conflict rules. Values may be UTF-8 or UTF-16LE (cmdkey and the Credential UI write UTF-16); anything that does not decode to text, or that contains interior NULs, is skipped with a warning instead of being injected as a mangled key. Disclosure - this source reads your Windows Credential Manager: only the generic credentials named in the map, with no enumeration of the vault. Resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. The package is read-only and stdlib-only (ctypes): it never creates, updates or deletes credentials, writes no files, starts no subprocesses, makes no network calls and does not self-update. Windows only. Credential Manager is user-scoped, so this raises the at-rest bar for backups, cloud sync and dotfiles; it is not a boundary against code already running as the same user. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — when enabled, reads only the Windows Credential Manager generic credentials named in secrets.wincred.map (no vault enumeration) and injects them as environment variables of the Hermes process and its children, exactly like .env entries; read-only, stdlib ctypes, no subprocesses, no network, no file writes; user-scoped at-rest protection, not a boundary against code already running as the same user."
maintainer: Yicheng-Mark
diff --git a/plugin-catalog/hermes-windows-eventlog.yaml b/plugin-catalog/hermes-windows-eventlog.yaml
index 27b04bf51b7..7de77674ece 100644
--- a/plugin-catalog/hermes-windows-eventlog.yaml
+++ b/plugin-catalog/hermes-windows-eventlog.yaml
@@ -1,6 +1,6 @@
name: hermes-windows-eventlog
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: windows-eventlog
description: "Answer \"why did this process die\" on Windows: three read-only tools over the Windows Event Log. win_crash_events reads Application Error / Application Hang / Windows Error Reporting / .NET Runtime records for a time window, decodes the exception code (0xC0000005 -> ACCESS_VIOLATION and the other codes a debugger would name), reports the faulting module, its path and the fault offset, and groups repeated crashes by app and signature. Records are classified by provider as well as by event id, so unrelated providers that reuse ids 1000 and 1001 for informational events are not reported as crashes. win_shutdown_events reads the System log for Kernel-Power 41 unexpected restarts, bugchecks decoded to names (0x9F -> DRIVER_POWER_STATE_FAILURE, accepting the decimal form some providers emit), EventLog 6008 dirty shutdowns, 1074 operator-initiated restarts with the process and comment, and the 6005/6006/12/13 start and stop markers. win_eventlog_query is the general case: any channel, filtered by event ids, levels, an exact provider name or a payload substring, returning structured records instead of raw XML. Queries read newest-first and stop at the window start or at a 5000-record scan cap; a call returns at most 200 records and marks truncated payload text. Channel names, provider names and numeric filters are validated before anything is interpolated into the query. Disclosure - this plugin reads the local Windows event logs and hands what it finds to the model: application and faulting-module paths, exception codes and offsets, report ids, service names and provider message text, which routinely includes user and machine paths (C:\\Users\\<name>\\...). Treat tool output like any other local diagnostic dump when sharing it. It reads only the channels the current account may read - Security and some operational logs answer with an access-denied error rather than any attempt to obtain elevation - and it never writes to a log, clears one or configures a channel. Stdlib-only (ctypes wevtapi plus xml.etree): no Python dependencies, no child processes, no network calls, no file writes, no self-update. Windows only. Disclosure — reads the local Windows event logs and hands what it finds to the model: application and faulting-module paths, exception codes and offsets, report ids, service names and provider message text, which routinely include user and machine paths (C:\\Users\\<name>\\...); win_eventlog_query reads any channel the account running Hermes may read, so an unelevated account gets access-denied on Security and some operational logs while an elevated Hermes can return Security-log records (logon events with account names and source addresses). It never requests elevation, never writes to, clears or configures a log, and has no Python dependencies, child processes, network calls, file writes or self-update. Windows only."
maintainer: Yicheng-Mark
diff --git a/plugin-catalog/hermes-windows-ops.yaml b/plugin-catalog/hermes-windows-ops.yaml
index 032eaf09c5a..bc0dcac9ec7 100644
--- a/plugin-catalog/hermes-windows-ops.yaml
+++ b/plugin-catalog/hermes-windows-ops.yaml
@@ -1,6 +1,6 @@
name: hermes-windows-ops
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: windows-ops
description: >-
Windows and WSL triage skills for Hermes: processes that survive a quit
diff --git a/plugin-catalog/hermes-windows-ports.yaml b/plugin-catalog/hermes-windows-ports.yaml
index 1a5b35a5209..6b2f9eb7824 100644
--- a/plugin-catalog/hermes-windows-ports.yaml
+++ b/plugin-catalog/hermes-windows-ports.yaml
@@ -1,6 +1,6 @@
name: hermes-windows-ports
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: windows-ports
description: >-
Answer "who holds this port" on Windows. win_port_owners reads the TCP and UDP owner
diff --git a/plugin-catalog/hermes-windows-process.yaml b/plugin-catalog/hermes-windows-process.yaml
index 8352b80f58c..a54813f70cf 100644
--- a/plugin-catalog/hermes-windows-process.yaml
+++ b/plugin-catalog/hermes-windows-process.yaml
@@ -1,6 +1,6 @@
name: hermes-windows-process
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: windows-process
description: >-
Answer "what is still running, and who started it" on Windows: win_process_table reads the
diff --git a/plugin-catalog/hermes-wsl-terminal.yaml b/plugin-catalog/hermes-wsl-terminal.yaml
index b51387b4e8b..c0894548ba3 100644
--- a/plugin-catalog/hermes-wsl-terminal.yaml
+++ b/plugin-catalog/hermes-wsl-terminal.yaml
@@ -1,6 +1,6 @@
name: hermes-wsl-terminal
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: wsl-terminal
description: >-
Run Hermes' terminal tools inside an existing WSL distro on Windows: one bash -c per
diff --git a/plugin-catalog/hermes-wslc-sandbox.yaml b/plugin-catalog/hermes-wslc-sandbox.yaml
index 6c4aedf51bb..1774b8f01c8 100644
--- a/plugin-catalog/hermes-wslc-sandbox.yaml
+++ b/plugin-catalog/hermes-wslc-sandbox.yaml
@@ -1,6 +1,6 @@
name: hermes-wslc-sandbox
repo: https://github.com/Yicheng-Mark/hermes-windows-plugins
-sha: b26b92760b2bfc36a91c280af96b0171c4d00267
+sha: 5bad3fb2baf04ce6befecfefce6d14f4c9c98934
subdir: wslc-sandbox
version: "0.1.0"
description: "Run Hermes' terminal, file and execute_code tools in a Linux container on Microsoft's WSL Containers (wslc) runtime, so Windows users who run WSL Containers get a sandbox without Docker Desktop. Disclosure — the plugin spawns the wslc CLI (one short-lived process per command, plus one long-lived container per environment) and every call runs inside that container; containers have outbound network access unless docker_network is false; persistent sandboxes are left stopped on disk until removed; host environment variables enter the container only when named in docker_forward_env, and only paths listed in docker_volumes are bind-mounted. wslc rejects --cap-drop, --security-opt, --pids-limit, --init and --storage-opt, so this sandbox is not capability-dropped the way the Docker backend's is, container_disk is reported but not enforced, and dangerous-command approval deliberately stays enabled for this backend. The plugin reads no credentials, stores none, and makes no network calls of its own."