Start here

[AlexBTurchyn]

Progress Watch is a place where anything that runs without you (a crawl, a training run, a migration, a CI job, an AI agent) can report its progress, and you get a push notification when it finishes. It started as a pile of my own scripts
that I kept checking on by hand.

It works, and it is deliberately not 1.0. The server is tested against SQLite and PostgreSQL on every push, runs from one compose file, and I use it every day. What is not settled is its shape: the API, the CLI's flags and output,
what a task can carry. I would rather settle that with the people using it than guess on my own. Doing it before 1.0 means the breaking changes happen now, while there is little to break, and not later, after you depend on it. When it
reaches 1.0, compatibility becomes a promise.

Until then, a release can change things. If you self-host and need to stand still, pin an image tag instead of latest.

Where things go:

• Something broken: open an issue. The form asks what /up says, which answers most of what I would ask next.
• An idea, or something you wish it did: Ideas.
• A question about running it: Q&A.
• Something you track with it: Show and tell.

A few things are left out on purpose, so they are worth knowing before asking for them. There are no accounts and no login, because a space UUID is the credential. Progress lives in Redis and is never written to the database. Steps nest
one level deep.

The server is this repository. The CLI, the MCP server and the agent skill are in progress-watch/progresswatch-cli. Hosted: https://progress.watch