All plugins

hermes-windows-tasks

Answer "what does this machine run on its own, and did it work" on Windows: win_scheduled_tasks lists the Task Scheduler's tasks with their state (Ready, Running, Disabled), the account each runs as, its first action's command line, its triggers in words (at logon, daily, weekly, at a time, on event), its last and next run with the machine's offset, its missed runs, and what its last result code means - 0x80070002 is a program that is no longer there, 0x800710E0 a task that needed a desktop it did not have, 0x40010004 one that was stopped, 0x80040154 a COM class that is not registered. win_scheduled_task_detail takes one task and gives its triggers with start boundaries and repetition, its actions with arguments and working directory, its principal and the settings that decide whether it runs on battery or when late; a task with no triggers but MaintenanceSettings runs during automatic maintenance and the notes say so rather than leaving an empty list. Use it for why a logon task keeps failing, for finding what an uninstalled program left behind at logon, for telling a disabled task from a broken one, and for reading a task's command line before trusting it. Read-only: nothing is created, started, changed or deleted. Reads through the ScheduledTasks cmdlets rather than the store on disk, because the TaskCache registry tree and C:\Windows\System32\Tasks both answer access denied without elevation, and rather than schtasks /Query /FO CSV, which is localized and interleaves error lines for tasks whose definitions are gone. The plugin declares no Python dependencies; there is no network call and no file write. Windows only. Disclosure - the tools report task paths, command lines, working directories, account names and SIDs to the model, and those reveal what the person has installed, what starts at their logon, and the paths under C:\Users\<name>; treat the output like a Task Scheduler window opened on their machine.

Yicheng-MarkToolsv0.1.0Updated 12 days ago

About

Answer "what does this machine run on its own, and did it work" on Windows: win_scheduled_tasks lists the Task Scheduler's tasks with their state (Ready, Running, Disabled), the account each runs as, its first action's command line, its triggers in words (at logon, daily, weekly, at a time, on event), its last and next run with the machine's offset, its missed runs, and what its last result code means - 0x80070002 is a program that is no longer there, 0x800710E0 a task that needed a desktop it did not have, 0x40010004 one that was stopped, 0x80040154 a COM class that is not registered. win_scheduled_task_detail takes one task and gives its triggers with start boundaries and repetition, its actions with arguments and working directory, its principal and the settings that decide whether it runs on battery or when late; a task with no triggers but MaintenanceSettings runs during automatic maintenance and the notes say so rather than leaving an empty list. Use it for why a logon task keeps failing, for finding what an uninstalled program left behind at logon, for telling a disabled task from a broken one, and for reading a task's command line before trusting it. Read-only: nothing is created, started, changed or deleted. Reads through the ScheduledTasks cmdlets rather than the store on disk, because the TaskCache registry tree and C:\Windows\System32\Tasks both answer access denied without elevation, and rather than schtasks /Query /FO CSV, which is localized and interleaves error lines for tasks whose definitions are gone. The plugin declares no Python dependencies; there is no network call and no file write. Windows only. Disclosure - the tools report task paths, command lines, working directories, account names and SIDs to the model, and those reveal what the person has installed, what starts at their logon, and the paths under C:\Users\<name>; treat the output like a Task Scheduler window opened on their machine.

hermes-windows-tasks

Answer "what does this machine run on its own, and did it work" on Windows, from inside
Hermes.

win_scheduled_tasks({"query": "wps"})
win_scheduled_tasks({"failed_only": True, "include_microsoft": True})
win_scheduled_tasks({"state": "disabled"})
win_scheduled_task_detail({"name": "\\Microsoft\\Windows\\Defrag\\ScheduledDefrag"})

Windows starts a great deal of what it does, and what installed software wants it to do,
through Task Scheduler: at logon, at boot, every hour, or during automatic maintenance. When
one of those starts failing, the only place that says so is the "Last Run Result" column of
Task Scheduler, as a number. These two tools read that column and translate it.

What the tools report

| Field | Where it comes from |
|---|---|
| state | Ready, Running, Disabled, Queued |
| run_as, run_level | The task's principal (a user, a SID such as S-1-5-18, or a group) |
| action | The first action's command line |
| triggers | The trigger classes in words: at logon, daily, weekly, at a time, on event |
| last_run, next_run | ISO 8601 timestamps with the machine's offset |
| last_result | The code, in hex, with what it means: 0x80070002 is a program that is no longer there, 0x800710E0 a task that needs a desktop it did not have, 0x40010004 one that was stopped |
| missed_runs | Runs the scheduler skipped, typically because the machine was off |

win_scheduled_task_detail adds what a listing has no room for: every trigger with its start
boundary, repetition and schedule, every action with arguments and working directory, the
principal, and the settings that decide whether a task runs on battery or when late. A task
with no triggers and MaintenanceSettings runs during automatic maintenance, and the notes
say so instead of leaving an empty list to be misread.

Read-only, and why it goes through PowerShell

Nothing is created, started, changed or deleted: the tools query, and the schemas say so.

The task store on disk is not readable without administrator rights. On Windows 11 (build
26300) both HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree and
%SystemRoot%\System32\Tasks answer [WinError 5] Access is denied to a normal user, so a
tool that walked them would work only for an elevated agent. The ScheduledTasks cmdlets run
unelevated, and ConvertTo-Json gives field names and values that do not change with the
display language.

schtasks /Query /FO CSV is the usual alternative and it is the wrong one: its header and
state words are localized, and for a registration whose definition file is gone it prints an
ERROR: Task cannot be loaded line in the middle of the rows, which is what makes naive
readers of it fail (hermes-agent issue #142140 is exactly that failure in hermes gateway ensure). These tools ask the cmdlets instead.

Cost

One PowerShell call for the listing (about 1.4 s for 195 tasks on this machine) and a
second one only when a single definition is asked for. There is no cache: scheduled tasks
change when software is installed, and a stale answer here is worse than a slow one.

Platform

Windows only. There are no Python dependencies, no network calls and no file writes.

README from the reviewed commit 9778252; it updates when the author re-pins.

More by Yicheng-Mark

15 plugins by Yicheng-Mark in the catalog.

Yicheng-Markhermes-dpapi-secretsResolve 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.CommunitytoolsYicheng-Markhermes-wincredResolve 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.CommunitytoolsYicheng-Markhermes-windows-appsAnswer "what is installed on this Windows machine": the software inventory behind Apps & Features, swept straight from the four Uninstall registry keys (the machine's 64-bit and 32-bit views plus the user's), so a program is found even when the Settings page hides it - a per-user install that never shows on the machine page came from the user view on the writing machine. Each row carries version, publisher, size in MB, install date and which view it lives in; the same DisplayName in two views is a 32/64-bit dual install, marked instead of listed twice. Entries the publisher asked to hide (runtime packages, update rollups) are filtered out unless asked for. Details one program with every field its publisher wrote and a reading of the uninstall command (MSI product code, setup executable, appx, script) so the next step is known before anything is run; the install folder is checked against disk. Use it for "what did that installer actually register", for inventory before a cleanup, and for "which of the two installs does uninstalling remove". Read-only: registry keys are enumerated and uninstall strings are reported, never run; no network, no file writes, no elevation. The sweep is pure registry - 102 entries in seven milliseconds on the writing machine, the whole table in ten, no PowerShell, no WMI. The plugin declares no Python dependencies. Windows only. Disclosure - the tools report program names, versions, publishers, sizes, install folders and uninstall commands, and what is hidden from Apps & Features, to the model; treat the output like the machine's own Apps & Features page.CommunitytoolsYicheng-Markhermes-windows-devicesAnswer "which device on this Windows machine is unhappy, and what does it need" on Windows: win_device_table lists every present PnP device with its class (System, Net, HIDClass, Display), its status, its manufacturer, its stable device id, and its problem code in words - 28 is one with no driver installed, 10 one that cannot start, 43 one Windows stopped after it reported a failure, 22 one the person switched off on purpose and is not broken - filtering by name or id substring, by class, or to the devices that need attention; devices no longer plugged in are history, left out unless asked for. win_device_detail takes one device by id or name substring and adds the driver behind it from the signed-driver table - name, version, date, provider, signer, INF file, signed or not - or the absence of one, which for code 28 is the same fact said twice; a disabled device gets a note saying it is on purpose, not an alarm. Use it for the Device Manager yellow-mark question without opening Device Manager, for finding what an uninstalled program left behind, and for what changed after an update. Read-only: nothing is enabled, disabled, updated or reinstalled. Both answers come from CIM (Win32_PnPEntity and Win32_PnPSignedDriver, joined by device id), whose property names, enum values and ids do not change with the display language; the human-facing device names localize and are carried through as data, never parsed. The plugin declares no Python dependencies; there is no network call and no file write. Windows only. Disclosure — the tools report device names, manufacturers, device ids and driver versions to the model, and those reveal the machine's hardware inventory and what is plugged into it; treat the output like a Device Manager window opened on their machine.Communitytools
All 15 by Yicheng-Mark

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section