Every scheduled AI job, on one page.

~2,300

lines of zero-dependency Python (stdlib only)

120

automated unittest test functions

83

commits from 09 Jun to 02 Jul 2026

£0

marginal infra cost vs the retired paid VPS agent

/ the challenge /

Once the jobs moved to a schedule, they became invisible.

A headless run fires under Windows Task Scheduler, writes to an overwritten log, and exits — with no single place to see whether it ran, succeeded, or hung, and no safe way to pause or reschedule it. A decommissioned paid VPS agent left recurring work needing a durable local home, on top of a stack of Windows-specific traps.

Register a recurring job with a single command, landing a scheduled task

Collectors poll Windows tasks, local agents and the VPS and render each as a card

At its time the task runs headless with per-job context, a timeout and run history

The operator watches sparklines and logs and can run/pause/reschedule any job

The watchdog probes the server hourly and restarts it if the port is down

Bringing remote VPS crons from read-only to fully controllable — run, pause, resume, reschedule and rename over SSH from the same dashboard — with the schedule string strictly whitelisted, single-quoted remotely, and unit-tested against shell-injection payloads, all without changing a single server route.

/ tech stack /

Built to be owned.