← Blog·Automation··2 min read

The end of “remind me”

The best work happens while nobody is watching. Cron and webhooks turn Nova from something you ask into something that shows up.

Most of what an operations team does is not clever. Half of it recurs: the daily summary, the dependency check, the report that goes out at eight. The other half reacts: an alert fires, a pull request opens, a lead fills in a form. Both halves used to need a person at a keyboard.

On a schedule

Declare cron jobs in config, or spin them up from chat. “Every weekday at seven, summarise what shipped and post it here” is a sentence, and then it is a job. Nova runs it, logs it, and reports back in the channel.

A job created in chat is a first-class job. It sits next to the config-declared ones with its schedule, last run, next run and status, and you manage it from the same channel you created it in. Nobody opens a dashboard to find out whether the Monday report is still scheduled. You ask.

On every signal

Point a webhook at Nova and an event becomes a full agentic run. GitHub, Linear, or anything generic. Every inbound hook is HMAC-verified and rate-limited per hook before an agent so much as reads it.

“It reads the alert, pulls the logs, opens the PR, and tells us what it did before anyone’s awake.”
Marcus Hale, VP Engineering, Vestwell

What a run can do

A scheduled or triggered run is a full session, so it has the full toolset: shell, files, web search, a real browser and, on the Business tier, Google Workspace. It can open a pull request, deploy itself with a zero-downtime drain, run a health check, and tell you what it changed.

Every step lands in the append-only activity log. So the morning report is not a summary of what Nova thinks it did. It is a list of what it did, with inputs, outputs and how long each step took.

Deploys that do not drop the ball

A job killed mid-run is worse than no job. Nova’s deploys are drain-safe: in-flight turns finish before any restart, with a hard-kill backstop so a stuck run cannot hold the system hostage. A self-restart preserves in-flight work. The 7am report goes out at 7am even if Nova shipped a new version of itself at 6:58.

The point of automation was never to save ten seconds of typing. It is to make the work happen whether or not anyone remembered it. “Remind me” was a workaround. This is the fix.

Contact

Tell us what Nova should run.