Windows No-Admin Service Watchdog

    1

    A local HTTP service on a Windows machine you cannot administer dies, hangs, or gets restarted by a script that killed the wrong python.exe.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Windows No-Admin Service Watchdog

    Example session with this skill installed

    Our Python job server on this locked-down Windows laptop keeps dying overnight and I don't have admin rights. Set up something that restarts it safely and tells me why it died.

    • Read your context and instructions
    • Compiled the windows no-admin service

    Summary

    Registered a per-user scheduled task that checks the server every 2 minutes, restarts it only when it is truly gone, and records crash evidence.

    What was done

    • pwsh -File scripts/Test-Watchdog.ps1: 27 checks passed.
    • One manual check with the real values: healthy (the server answered /healthz in 40 ms, one matching process, port 8765 listening).
    • Register-WatchdogTask.ps1 -TaskName jobserver-watchdog -IntervalMinutes 2: task created as the current user, limited token, at logon and every 2 minutes, one instance at a time.

    Overnight result

    • 03:12 check: health failed 3 times, no matching process, port free -> recover.
    • 03:12 restart evidence: exit code -1073741819 (0xC0000005, access violation), Application-log event 1000 for python.exe, stderr tail shows the native extension that faulted (tokens redacted).
    • 03:14 check: healthy. No further restarts; cap of 3 per 30 minutes untouched.
    • A slow 02:40 request that timed out was recorded as unresponsive_no_restart and left alone; the server finished its job.

    Status file: %LOCALAPPDATA%\jobserver\watchdog\status.json. To pause: create a file named PAUSE in the state folder.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A local HTTP service on a Windows machine you cannot administer dies, hangs, or gets restarted by a script that killed the wrong python.exe. This watchdog runs as the current user from a per-user scheduled task and makes the decisions that keep a service alive without making things worse.

    Decision table (pure, exported, tested): PAUSE file wins; 2xx health is healthy; failures under the threshold retry; a matching server process or a listening port means unresponsive_no_restart (a slow server that owns work is never killed on an HTTP timeout); restarts at the cap in the window means restart_rate_limited; otherwise recover. Exit 0 or 1 so a monitor can page.

    Identity: a server is yours only if its executable path matches and every required command-line fragment appears at a token boundary; -m myservice does not match -m myservice2. Orphan worker detection by parent PID, creation time and a worker marker.

    Evidence on restart: exit code decimal and hex (NTSTATUS), Application-log crash events 1000/1005 for the executable, redacted stderr tail. Everything on disk passes a redactor for bearer tokens, token=, password:, api_key= and sk- keys. status.json is swapped in atomically with a .previous copy; events are one JSON object per line.

    Scripts: Watchdog.psm1 (module), Watchdog.ps1 (one check per run), Register-WatchdogTask.ps1 (per-user task every N minutes and at logon, limited token, one instance, 5-minute limit, -Remove), Test-Watchdog.ps1 (27 offline checks). reference/decisions.md explains each rule and the failure behind it. PowerShell 7, nothing to install.

    Supervises only current-user processes. Does not kill unresponsive servers that still hold the port. Requires PowerShell 7.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 19 days ago

    Requires

    PowerShell 7
    Windows
    Task Scheduler
    Service with an HTTP health endpoint

    Permissions

    Write Files
    Terminal / Shell
    Read Files
    Network Access

    Shell to run the PowerShell scripts and register the per-user scheduled task; read/write files for the status, state and event files under a folder you choose. Network access is limited to the local health URL you configure. No environment variables.

    Listed19 days ago

    What's inside

    Frequently Asked Questions

    No administrator privileges are required. The skill is designed to run within user-space, utilizing per-user Scheduled Tasks and standard PowerShell 7 commands to manage services you own.

    Unlike basic scripts that just search for a process name, this skill verifies exact executable paths and command-line arguments. This prevents 'friendly fire' where the watchdog might accidentally kill other instances of Python or Node.js running on the same machine.

    You receive the complete PowerShell 7 source code for the watchdog engine, an offline test suite for environment validation, a configuration template, and detailed deployment documentation.

    The skill includes a built-in rate limiter that caps restart attempts within a specific time window and a 'PAUSE' file mechanism that allows you to temporarily disable the watchdog for manual maintenance without deleting the task.

    It is compatible with any AI agent capable of executing PowerShell commands or managing files, such as AutoGPT or Open Interpreter. It can also function as a standalone utility triggered by the Windows Task Scheduler.

    If a service is listening but unresponsive, the watchdog logs the event and halts auto-restarts to prevent data corruption. This ensures a human or agent can investigate the logs—which include exit codes and stderr tails—before taking action.

    New in Workflow Automation