# Hermes Windows Tasks: Hermes Agent plugin > 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… Canonical: https://hermeswatcher.com/plugins/hermes-windows-tasks Tier: Community Official page (Nous Research): https://hermes-agent.nousresearch.com/docs/plugins/hermes-windows-tasks Last updated in catalog: 2026-10-29 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. ## Good to know before installing 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\; treat the output like a Task Scheduler window opened on their machine. From the plugin's catalog listing. ## How to install 1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on. ```bash hermes plugins install hermes-windows-tasks ``` 2. Said no? Turn it on later: ```bash hermes plugins enable hermes-windows-tasks ``` 3. Restart Hermes so it loads the plugin. Some plugins also need a sign-in or settings: see the official page. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/plugins ## Facts - Category: Memory & notes, Automation & multi-agent - Maintained by: Yicheng-Mark (Community) - Needs: No API keys declared - Adds tools: `win_scheduled_tasks`, `win_scheduled_task_detail` - Requires Hermes: `>=0.21.4` - Version: 0.1.0 - In the catalog since: 2026-10-29 ## Links - [Full setup and settings (official page)](https://hermes-agent.nousresearch.com/docs/plugins/hermes-windows-tasks) - [Source code](https://github.com/Yicheng-Mark/hermes-windows-plugins/tree/main/windows-tasks) - [All plugins](https://hermeswatcher.com/plugins.md) --- HermesWatcher is an independent guide. It is not affiliated with or endorsed by Nous Research. The [official Hermes Agent documentation](https://hermes-agent.nousresearch.com/docs) and [repository](https://github.com/NousResearch/hermes-agent) from Nous Research are the authority; each page here lists the official sources it was written from. If this site and the official docs disagree, trust the official docs. Index for agents: https://hermeswatcher.com/llms.txt