A new major release,handled before you read the changelog.
A Web watch card checks a releases page on a schedule. When it changes, the diff goes to the connected agent as a prompt. The agent works in its own worktree — prepared with your .env and npm ci before its first prompt — upgrades, fixes the breaking changes and tells you on Telegram.
The watch fires and the agent upgrades on its own branch. Allow the install when it asks.
A Web watch sees a new major release and wakes the agent, which upgrades in its own worktree, fixes what broke and reports on Telegram.
Watches any page
Releases, changelogs, docs — the Web watch card fetches the page, diffs it and sends the change to the connected agents.
Its own branch
The upgrade happens in the agent’s own git worktree; your checkout stays as it was until you merge.
Prepared like yours
Listed files are copied in, not symlinked, and the setup command finishes before the agent starts.
A report where you are
Migration notes land in a note card; the short version reaches your Telegram bot.
From release to report
Nobody has to remember to check.
More ways to ship with agents
Every scenario runs on the cards you already saw — pick the next one.
Let an agent keep your dependencies current
On its own branch, with your OK for every install.
macOS and Linux are coming later.
The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.