Choose the work you want waiting for review

Ten focused starting points for recurring work. Pick the closest role to see three traceable workflows, what each one needs, what it returns, and where a person stays responsible.

What kind of work keeps returning?

Choose the closest role. Three audience packs are bundled; the other seven starting sets are assembled from the included picker templates. Every page says which is which.

Developer

Review-gate jobs return work for you to read before it reaches main.

Four repos, one of you, and an agent CLI you can only supervise one session at a time. This is the part that runs the other three while you sleep — on Claude Code, GitHub Copilot CLI or agy, whichever each repo calls for — and hands all of it back uncommitted.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

Three finished worktrees with uncommitted diffs, the review screen scrolling with an explanation card beside each hunk, and one agent at the top still blocked on an approval it asked for at 3am. — Illustration 08:40. Three agents finished, one is still waiting on a question it asked at 03:12, and nothing has been committed.

Day one: three agents, already written

Overnight backlog

Every night at 2am

By morning there is a finished, uncommitted diff in a worktree with an explanation beside every hunk.
Dependency sweep

Mondays at 6am

Every Monday, patch and minor upgrades applied and tested in a worktree, with the risky majors listed separately and untouched.
CI red triage

Every 2 hours

A red build on the default branch becomes a queue item naming the failing test, the exact command to reproduce it locally, and — when it is small — the fix itself, uncommitted.

Installed as the developer pack. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

macOS on Apple Silicon
claude (or copilot/agy) installed and authenticated
node on PATH
At least one git repo you are happy for an agent to branch from

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

Indie hacker / founder

The chores ran while you slept. Your morning starts at the decisions.

You are engineering, support, finance and marketing — every hat, one head. The chores are not hard, they are just endless, and they are the reason you shipped nothing this week. Overnight they get read, sorted and drafted, so your day begins at the decision instead of at the discovery.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

The morning view: a Needs-you strip with four drafts and one decision, each produced overnight and each one click away. — Illustration 08:00. Four drafts and one decision, all produced while you were asleep. Every one of them waiting on you.

The caveat, up front. Every non-code deliverable arrives as a draft you approve and send. For a company of one you are the only reviewer there is, and that is exactly who this is built for.

Day one: three agents, already written

Overnight backlog

Every night at 2am

By morning there is a finished, uncommitted diff in a worktree with an explanation beside every hunk.
Inbox triage

Every 30 minutes, business hours

The inbox read, sorted and the obvious replies drafted — and you pulled in only for what truly needs you.
Renewal reminder

Every morning at 8

No renewal, expiry or deadline arrives as a surprise, each one filed with its source attached.

One agent comes from the developer pack; the other two are ready-made prompts in the agent picker. All three are switched off until you turn them on. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

A mail account you are willing to connect over IMAP (read-only)
Somewhere to put the non-code project: a scratch folder, not a repo

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

Agency / contract shop

One machine, six client repos, and one place for run output and available command evidence.

Five stacks, five sets of credentials, and a client asking what happened this month. Answering that used to be non-billable archaeology — here the record is captured while the work happens, per client.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

The commands view filtered to one client project — the commands an agent ran this week with their exit codes and durations — beside that client's queue of finished, unpushed work. — Illustration One client, one week: run output and captured commands with exit codes, kept together for review.

The caveat, up front. Per repo, on your machine. The evidence is a filterable command log you can hand to a client and a markdown digest you own — and each Mac keeps its own, so two people's work never mixes.

Day one: three agents, already written

Overnight backlog

Every night at 2am

By morning there is a finished, uncommitted diff in a worktree with an explanation beside every hunk.
Dependency sweep

Mondays at 6am

Every Monday, patch and minor upgrades applied and tested in a worktree, with the risky majors listed separately and untouched.
Digest

Every evening at 6.30

One rollup per project of what actually happened — runs, queue items, decisions waiting — on your screen, not in a client-facing report.

Two come from the developer pack; the third is a ready-made prompt in the agent picker. Install them per client project. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

One project per client, each with its own working dir and env

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

DevOps / platform

The infra chores you keep deferring, done overnight — as a plan you approve, never an apply.

Drift, dependency bumps, certificate rotations, log noise. None of it is urgent, all of it is real, and it never becomes anyone's priority. This does the work and stops at the point where a human has to say yes.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

A terraform plan diff in the review screen, with the apply visibly blocked behind an approval gate marked denied because nobody decided. — Illustration The plan is ready to read. The apply is blocked, and it expired because nobody decided — which is the correct outcome, not a failure.

The caveat, up front. Chores, not monitoring. The work happens overnight and stops at a plan you approve — it pages nobody, and it fires nothing while your Mac is asleep.

Day one: three agents, already written

Dependency sweep

Mondays at 6am

Every Monday, patch and minor upgrades applied and tested in a worktree, with the risky majors listed separately and untouched.
Security audit

Sundays at 3am

The issues that pile up quietly — CVEs, exposed secrets, dependency advisories — reported against how your project actually uses the package rather than merely what is in the tree.
Renewal reminder

Every morning at 8

Certificates, domains, licences and contracts that expire when nobody is looking, filed with the source attached.

One comes from the developer pack; the other two are ready-made prompts in the agent picker. Every one of them stops at a plan. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

You accept that AgentCron is not a monitor and never pages anyone
Your tooling is reachable from a shell on your Mac, or over an MCP server you run

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

Tech lead / senior IC

Every change arrives with its own explanation. You review the reasoning, not the diff.

You are the one who reads everything, and the volume of agent-written code has made that unsurvivable. This makes a change explain itself before it reaches you — and it does that on your machine, for your own review load.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

The review screen with an explanation card beside a hunk: what changed, why, what it means in plain English, and the one thing that would break. — Illustration One hunk, four sentences: the mechanism, the alternative it rejected, the idea underneath, and what to check. A hunk with no card shows as a gap.

The caveat, up front. Your own review load, on your own machine. Single-user by construction: no seats to buy, no team admin, and nothing of yours on anyone else's computer.

Day one: three agents, already written

Overnight backlog

Every night at 2am

By morning there is a finished, uncommitted diff in a worktree with an explanation beside every hunk — the reasoning arrives with the change, not after it.
CI red triage

Every 2 hours

A red build on the default branch becomes a queue item naming the failing test, the exact command to reproduce it locally, and — when it is small — the fix itself, uncommitted.
Digest

Every evening at 6.30

One end-of-day rollup of what your own agents did, what is waiting on you, and what stalled.

Two come from the developer pack; the third is a ready-made prompt in the agent picker. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

You are willing to run agents on your own machine, not the team’s

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

Content creator

Monday morning: the week planned, the drafts written, the posts queued. You publish.

The calendar going empty is what kills a channel, and it goes empty in the weeks you are busiest. This does the planning and the first drafts overnight, so you sit down to edit rather than to start.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

Monday morning in the queue: a week's content calendar with the reasoning beside each slot, two finished drafts underneath it, and the week's social posts lined up as items. — Illustration Monday 08:00. A week planned with the reasoning attached, two finished drafts, and the posts lined up — every one of them waiting on you to publish.

The caveat, up front. It plans and it writes — ideas, outlines, scripts, descriptions, the whole calendar. Rendering and publishing stay with you, which is why nothing goes out in your name that you have not read.

Day one: three agents, already written

Content planner

Mondays at 8am

A living content calendar driven by your goals and by what is actually working, with the reasoning beside each slot.
Draft writer

Weekday mornings, or on demand

A brief becomes a finished, on-voice first draft ready for your polish.
Social scheduler

Fridays at 10am

The week's posts lined up as ready-to-publish drafts on a clear calendar — queued, never posted.

All three are ready-made prompts in the agent picker, switched off until you turn them on. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

Somewhere for the content project to live: a folder or a repo the agent can read and write
Something for the planner to learn from — past pieces, a goals note, or your own numbers pasted in

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

Customer support lead

Every morning: the replies already written, and the three that genuinely need you.

Twenty to two hundred conversations a week and no helpdesk worth the name. An agent reads the queue before you do, writes the routine answers, and pulls you in only for the ones that actually need a person.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

The Needs-you strip: eleven drafted replies collapsed into one line, and one escalation expanded with the drafted answer beneath it. — Illustration Eleven routine replies written overnight, collapsed into one line. One escalation, open, with its draft underneath.

The caveat, up front. The replies arrive written and you send them, so your name is on nothing you have not read. At ten conversations a day that is most of the work gone — at a hundred, do the arithmetic on this page first.

Day one: three agents, already written

Support triage

Every 20 minutes, business hours

Raw incoming support turned into a clean, prioritised queue with the routine answers already drafted.
Reply drafter

Hourly through the day, or on demand

The hard replies triage flagged — the ones needing a careful answer — written out in full.
Churn watch

Weekday mornings at 8

Accounts drifting toward cancellation surfaced early, while there is still time to act.

All three are ready-made prompts in the agent picker, switched off until you turn them on. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

The support channel is an IMAP mailbox, or reachable over an MCP server you run

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

Analytics engineer

Your models ran overnight. Here's the diff that fixes the one that broke.

Your models live in a repo, run on a schedule, and break quietly when an upstream schema changes. A green run and a wrong number look identical from the outside — so the run has to leave evidence, not just an exit code.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

A queue item reading 'orders_daily fell 34% against yesterday', with the upstream column rename identified and a one-line model fix waiting uncommitted in the review screen. — Illustration orders_daily down 34% overnight, no deploy behind it. The renamed upstream column named, and the one-line fix waiting uncommitted.

The caveat, up front. It runs the command your repo already runs, with the credentials your repo already uses, held in a per-project variable on your Mac. No warehouse integration to configure, and nothing new to give access to.

Day one: three agents, already written

Nightly smoke

Every night at 3am

Last night's run of the command your repo already uses, with the evidence attached and a one-line verdict — so a green run and a wrong number stop looking the same.
Overnight backlog

Every night at 2am

By morning there is a finished, uncommitted model change in a worktree with an explanation beside every hunk.
Digest

Every evening at 6.30

One rollup of what ran, what moved and what is waiting on you — in your own numbers, not a BI tool.

Two come from the bundled packs — one QA, one developer — and the third is a ready-made prompt in the agent picker. Every agent arrives switched off, with a “Run once” button — nothing fires on its own.

What has to be true first

Models in a git repo with a runnable local command
Warehouse credentials you are willing to put in a per-project env var on your Mac

And the limits, in the same breath

macOS only. You bring, install and authenticate one of the supported agent CLIs shown above.
Schedules fire while your Mac is awake — AgentCron can hold it awake through a window you set (lid open) — and there is no daemon, no wake-from-sleep and no catch-up for a run that was missed.
AgentCron grants none of its own commit, push, send or pay paths by default. The launched CLI remains a real networked process, so separately configured CLI tools and project credentials keep their own risk.

The useful pattern is deliberately narrow

AgentCron is for work that repeats, can be described to a CLI agent, and should end in something a person reviews. A repository workflow can run in its own git worktree. A folder or service workflow needs the files, credentials and connection it names; AgentCron does not invent those integrations for you.

The prompt is not proof that a workflow succeeded. Check the returned files, command record and terminal output, then decide what happens next. Product visuals on this site remain labelled Illustration until the corresponding workflow has been captured from a real, synthetic test run.

Code, quality and technical operations

These roles get the strongest built-in fit because the work already lives in a repository.

Build and maintain
Developers and open-source maintainers can prepare bounded changes, dependency reviews and issue triage in a worktree. A tech lead can start from release notes, review preparation and planning output rather than a blank page.
Test and analyse
QA workflows run named checks and return failure evidence. Analytics engineering stays repository-based: validate models, refresh documentation and prepare reviewed data-quality findings, rather than promising access to an unconfigured warehouse.
Operate with a plan
DevOps workflows inspect repository-owned configuration and prepare checklists, dependency work and runbooks. They are scheduled chores, not an uptime monitor, pager or cloud runner.

Client, customer and publishing work

These starting points are useful when the required files or service connection already exist.

Founder and agency
Prepare weekly digests, client status drafts and project reviews from scoped folders. Keep each client in its own project and review the result before it leaves your Mac.
Customer support
Triage supplied conversations and draft replies against supplied documentation. AgentCron does not provide a helpdesk connector and it does not send the reply.
Content creator
Turn supplied research and existing material into outlines, scripts and a review calendar. Publication remains a human action; no social network or publishing account is bundled.

Before you schedule anything

Install and sign in to a supported CLI, choose a real project folder, and connect any external service the workflow explicitly needs. Run the task manually once with non-sensitive data before giving it a schedule. If your Mac is asleep, a scheduled run does not fire and missed runs are not replayed automatically.

See release status See pricing

Not released yet. It will need macOS 12.0 or later on Apple Silicon — and the download page says exactly what is still missing.

What kind of work keeps returning?

Review-gate jobs return work for you to read before it reaches main.

Day one: three agents, already written

Overnight backlog

Dependency sweep

CI red triage

What has to be true first

And the limits, in the same breath

Wake up to triaged issues, a reproduction video, and a changelog you only have to approve.

Day one: three agents, already written

Issue triage

Repro runner

Release notes

What has to be true first

And the limits, in the same breath

Every morning, last night's test run — as screenshots, not a wall of red text.

Day one: three agents, already written

Nightly smoke

Flaky hunter

PR evidence

What has to be true first

And the limits, in the same breath

The chores ran while you slept. Your morning starts at the decisions.

Day one: three agents, already written

Overnight backlog

Inbox triage

Renewal reminder

What has to be true first

And the limits, in the same breath

One machine, six client repos, and one place for run output and available command evidence.

Day one: three agents, already written

Overnight backlog

Dependency sweep

Digest

What has to be true first

And the limits, in the same breath

The infra chores you keep deferring, done overnight — as a plan you approve, never an apply.

Day one: three agents, already written

Dependency sweep

Security audit

Renewal reminder

What has to be true first

And the limits, in the same breath

Every change arrives with its own explanation. You review the reasoning, not the diff.

Day one: three agents, already written

Overnight backlog

CI red triage

Digest

What has to be true first

And the limits, in the same breath

Monday morning: the week planned, the drafts written, the posts queued. You publish.

Day one: three agents, already written

Content planner

Draft writer

Social scheduler

What has to be true first

And the limits, in the same breath

Every morning: the replies already written, and the three that genuinely need you.

Day one: three agents, already written

Support triage

Reply drafter

Churn watch

What has to be true first

And the limits, in the same breath

Your models ran overnight. Here's the diff that fixes the one that broke.

Day one: three agents, already written

Nightly smoke

Overnight backlog

Digest

What has to be true first

And the limits, in the same breath

The useful pattern is deliberately narrow

Code, quality and technical operations

Build and maintain

Test and analyse

Operate with a plan

Client, customer and publishing work

Founder and agency

Customer support

Content creator