Go to bed.
Wake up to a PR.
A schedule trigger fires at 03:00 on weekdays. An agent updates your dependencies, the test suite sends failures back to it, and a pull request opens only if there are new commits. You wake up to a PR, or to nothing if everything was already current.
- Update dependencies Claude Code · sonnet
- Run tests npm test · ↻ 1
- Count new commits git rev-list
- Open pull request only if > 0
What the pipeline does for you
Quiet when there’s nothing to do
The PR step has a Run only if condition on the commit count. Zero commits skips it and the run still succeeds.
Tests push back
A failing suite loops back to the update step with the output attached, up to twice, before anything is opened.
Never overlaps
Max concurrent runs is 1, so a slow night can’t collide with the next one.
Tells you in the morning
Send run succeeded and failed events to Slack, ntfy or Discord. The success message links the PR.
Four steps, once
- Import the Nightly maintenance pipeline JSON and set your local repository and test command.
- Triggers → Add trigger → Schedule, with the cron expression 0 3 * * 1-5.
- Add a notification channel filtered to this pipeline.
- Click Run once to test it without waiting for 03:00.
Jimothy has to be running (the tray is fine) and the computer awake when the schedule fires. Missed firings aren’t caught up.
Same engine, different jobs
For engineering
Issues → pull requests
Hand off a Linear, Jira or GitHub issue. Agents plan, build and review it, and you approve the PR.
See how it runs →GitHub → CommentSpecs from vague issues
A fuzzy issue gets a spec with acceptance criteria and open questions, posted back after you approve it.
See how it runs →Beyond engineering
Support reply drafts
New tickets are triaged and answered in your voice, within your policies. You approve before anything is sent.
See how it runs →Schedule → SlackWeekly product updates
Every Friday the week’s changes become a customer-facing “What’s new” post, ready to approve and publish.
See how it runs →Webhook → CRMInbound lead research
Each contact-form lead gets a cited research brief, a fit rating and a first reply before you’ve opened the email.
See how it runs →Build your own
Agent, shell and approval steps in a DAG, started by an issue, a schedule or a webhook. Or describe it and let Jimothy draft the pipeline.