Watch any process

Some things run for hours with nobody watching: a nightly crawl, a training run, a migration, a CI pipeline, an agent working through a long task. Progress Watch gives them one place to report to, and gives you one place to look — plus a notification when they finish.

One request, no library

Reporting is an HTTP request. There is no SDK to install and nothing to import, because wrapping a single PUT would add nothing.

There is a command line tool as well, and wrapping a command is the whole integration — it creates the task, streams the output through untouched, and closes the task with the exit code:

Counts, not percentages: the screen shows 1200 / 50000 pages, which tells you something that 2.4% does not. The total may change as a job discovers more work — send the new number and the bar recalculates. Full CLI and curl examples are one click away.

Agents report their own work

An AI agent breaks a job into steps and then works for a long time with nothing to show for it. Connect one over MCP and it gets tools for creating a task and reporting against it: one task for the job, one child task per step, updated as it goes. There is an agent skill for the same thing without MCP.

The agent decides when tracking is worth it and how often to report. The tool descriptions tell it what a task is for, not a schedule to follow.

No accounts

A space is a container for tasks, and its UUID is the credential. Whoever has the link can read and write it; sharing is giving someone the link. There is nothing to sign up for, nothing to log into, and no password to lose — which also means the link is the only way back to a space, so it is worth keeping like an API token.

Progress is not stored

Current state lives in memory and expires on its own. A crawler reporting every second for three months does not grow a database, and there is nothing to clean up afterwards. The trade is deliberate: there is no history and no charts, only what is happening now.

What it will not do

• Send commands back. It is a departures board, not an orchestrator. A process reports; nothing reports to it.
• Keep a log. One line, the latest, per task. Log storage is a solved problem and this is not it.
• Nest more than one level. A task may have steps; a step may not.

Run it yourself

The server is open source and self-hosting is one container plus a Redis — see the Docker snippet. The hosted service exists so you do not have to, not because the software is crippled without it.