Download
macOS on Apple Silicon. Bring your own agent CLI — Claude Code, GitHub Copilot CLI or agy. AgentCron can see which ones you have, but it cannot install or sign you in to one.
The app runs every day on the machine it was built on. It is not signed yet, so downloading it today would get you a warning dialog rather than an app — that is being fixed before release, and it is not a step worth asking you to work around. There is no list to join and nothing here collects an address: the changelog announces the build and the buy button first, and it has a feed, so the announcement can come to you. This page changes the same day.
What you need before it is any use
- macOS 12.0 or later on Apple Silicon.
- An agent CLI you already use and have already signed in to —
codex,claude,copilot,agy,shell. This app detects one; it cannot install or authenticate one for you. nodeon your PATH. The control CLI that agents talk back through is a Node script.- A folder you are happy for an agent to work in. For code work, a git repo.
How you get the next version
By coming back here and downloading it. The in-app updater is written but not usable yet: it is not signed with a real key and there is no public release for it to fetch, so it refuses to run rather than checking anything — which is why the app makes no network call on your behalf today. When it does become usable, the automatic check is opt-in and off by default.
The first ten minutes
In this order. The last step is the one that tells you whether the rest is worth setting up.
Let it look around
On first launch it checks which agent CLIs are on your machine — Claude Code, GitHub Copilot CLI, agy — and whether Node is where it expects. Fix anything it flags now; most later problems trace back to this screen.
Add a project
Point it at one repo. Not your most important one.
Create one agent from a template
Pick a template, read the prompt it filled in, and change anything that does not match how your repo actually works. The prompt is the product; it is worth the two minutes.
Press Run once
New agents are created switched off on purpose, and the button next to them says Run once to see what it does. Watch this one. Read the command log while it works.
Only then give it a schedule
Turn it on after you have watched it do the thing at least once. Nothing in a ready-made pack fires on its own.
What Gatekeeper will say, and what it means
Until a build has been through Apple's checks, macOS refuses to open it and shows either cannot be opened because the developer cannot be verified or is damaged and can't be opened. Nothing is damaged — that second message is what macOS says about an app whose signature it cannot make sense of.
What you would actually be accepting:
- Apple has not scanned the build for malware.
- Nothing cryptographically ties the download to a named developer account, so if the file were swapped in transit or on the host, macOS could not tell you.
- You are relying on your own judgement instead of Apple's. That is a real basis for a decision, but it is a different one, and it is worth making deliberately.
If that trade is not one you want to make, the right answer is to wait for the signed release, and that is a sensible call rather than a cautious one.
The two messages need different things, and only one of them has an override. Cannot be opened because the developer cannot be verified means the signature is valid but unattributed, and macOS will let you through: Right-click → Open, or Privacy & Security → Open Anyway. It asks once and leaves the check in place for the next thing you download, so use it when you can.
Is damaged and can't be opened means macOS could not validate the signature at all, and there is no override for it — Right-click → Open and Open Anyway both re-run the verification that is already failing. The only thing that opens a build in that state is removing the quarantine flag: xattr -dr com.apple.quarantine /Applications/AgentCron.app. That permanently disables the check on that one file, which is a real decision rather than a formality. Read which message you actually got before running it.
How you will know the download is genuine
You are being asked to run an unfamiliar developer's app next to your repos and credentials, so the burden of proof sits here, not with you. This is the standard every public release is held to, written down before the first one exists so you can hold the releases to it:
- A Developer ID signature on every public build, submitted through Apple's checks, so macOS itself verifies who made it and that it was not altered after signing.
- The signing identity (Team ID) printed on this page, so continuity is checkable — if a build ever arrives signed by someone new, you can catch it in ten seconds, and you should.
- A SHA-256 published beside each download link, so what you fetched can be compared against what was released, with one Terminal command.
- Any change to the signing identity, and any new network destination, announced in the changelog before it ships — not discovered by users afterwards. The privacy page lists every network destination the app has today and shows how to verify the list yourself.
None of this is decoration. Mac users have watched quietly transferred apps start shipping analytics under the old icon; the defence against that is a paper trail you can check, and this page is where it will live.
Two things that will happen
Both are certain enough that they belong here rather than in a support thread.
A schedule will be missed
The scheduler runs inside the app on your Mac. If the machine is asleep at 3am, the 3am run does not happen, and there is no catch-up when it wakes. Keeping the app open and the Mac awake is the fix — and Settings has a keep-awake window that holds the Mac awake through the hours you name, with the lid open; closing it still sleeps the Mac. What stays architectural: no daemon, no wake-from-sleep, no catch-up.
Disk will disappear
Worktrees, screenshots, command output and run history add up faster than you expect — the machine this was built on carries over a hundred worktrees. There is a storage view that shows where it went and a cleanup that previews before it deletes anything. Look at it in week one rather than in month two.
Straight answers, before you download
Why is this not on the Mac App Store?
Because it could not be itself there. App Store apps run inside the App Sandbox, and this app's entire job is the kind of thing the sandbox exists to prevent: spawning the agent CLIs you installed, in real terminal sessions, against any folder you point it at, with your own credentials in the environment. Distribution is a direct download instead, which is exactly why the integrity section above exists — outside the App Store, the checking falls to a signature and a hash, and both are owed to you.
Does it run on an Intel Mac?
No. Apple Silicon only — the only builds that have ever existed are arm64, and nothing on this page should be read as promising an Intel build. If you are on an Intel Mac, the kindest thing this page can do is not sell to you.
Do I need all three agent CLIs?
One is enough. Claude Code, GitHub Copilot CLI and agy are each first-class, chosen per agent, so the app is useful with whichever single subscription you already carry. First launch detects what is installed; what it cannot do is install one or sign you in — that stays between you and your CLI vendor.
Can I try it without paying anything?
That is the design, the moment there is a build here: the free tier is one project with every safety mechanism in the product — no account, no card, no trial clock — and paying is only for outgrowing it. Today there is no build to hand over, which is the only thing this page is waiting on.
What does it leave on my machine, and how do I get rid of it?
Its state lives in one local data directory on your Mac — runs, queues, logs, settings — and mail passwords go into the macOS Keychain rather than into any file. Nothing syncs anywhere. Removing AgentCron is deleting the app, that directory and the Keychain entry, plus whatever worktrees agents created inside your own repos — and those are listed in the storage view, with a cleanup that previews exactly what it would free before deleting anything.
If something is wrong
There is a health check built in that reports what it found — CLIs, Node, the agent channel, disk — and exports the whole thing to a file. Attaching that file to a bug report is the difference between a same-day answer and a week of back-and-forth, because otherwise every bug is happening on a machine nobody else can see.
Where to send it is the honest gap on this page: the support address arrives with the first release. Keep the export in the meantime — it is what any first bug report is going to need.