saucesteals/monitord

monitord is a small local program written in Go that runs recurring checks and remembers what it saw last time. It fills the gap between a plain cron job, which has no memory between runs, and a full job scheduling platform, which is more than most people need for a handful of watchers. Each individual check, called a monitor, is its own small Go program. A monitor might check whether a product page shows an item back in stock, whether a website is still responding, or whether an API's health check still passes. The daemon handles the parts that are tedious to build yourself: scheduling how often a monitor runs, saving its state in a local SQLite database so it survives restarts, running each deployed monitor as a long-lived background worker so things like open network connections can persist between checks, and sending alerts when something changes. Alerts can be sent to Discord as formatted messages, including things like an image and labeled fields such as price or size. There is also an integration called OpenClaw that can turn a monitor's alert into a task for an AI agent to act on, complete with a custom prompt describing what the agent should do when that alert fires. A command line tool covers the full lifecycle of a monitor: creating one from a template, testing it locally, deploying it to run continuously, inspecting its history and current state, and removing it. Because each monitor's saved state is a typed Go data structure rather than loose untyped data, the tool checks that a redeployed monitor's new code still matches the shape of data already saved, and it supports writing a migration function when that shape needs to change. The project also supports assigning monitors to run through imported proxy pools, keeping any proxy credentials out of the monitor's own source code. Installation is done with a shell script that builds the tool and can set it up as a background service on macOS or Linux.