Your agents are everywhere. Their work is nowhere.
You have powerful AI agents. But the work they do lives in terminal scrollback, cron tables, CI logs and chat threads — invisible, unrepeatable, unaccountable.
Stop babysitting terminals and cron scripts. Book agent work on a real calendar — Clockwork runs it in an isolated sandbox at the hour you chose and files a report you can actually read.
Free during beta · No API key · Uses your Claude Code / Codex / OpenCode / Hermes login
You have powerful AI agents. But the work they do lives in terminal scrollback, cron tables, CI logs and chat threads — invisible, unrepeatable, unaccountable.
Clockwork overlays your meetings with scheduled agent work, so you always know what ran while you were heads-down — and what needs you now.
Right now recurring agent chores live in crontabs, shell scripts, CI pipelines, and sticky notes. Clockwork gives that work a home on your calendar — with budgets, approvals, isolation, and searchable history built in.




Choose an agent profile, a repo, a budget, and a time. One-off or recurring.
Your own CLI engine executes unattended inside an OS-sandboxed git worktree.
A human-readable report lands in your inbox — branch, diffstat, cost, transcript.
Make it weekly. Search your run history. Trust grows with evidence.
Month grid, recurrence, missed-run policies, per-repo mutex — scheduling is first-class, not an afterthought.
Claude Code today, Codex / OpenCode / Hermes when you want. Switch per task without rebuilding anything.
Risky actions pause the run and ask you. Unanswered asks fail safe — never silently approved.
Every run gets its own worktree and Seatbelt sandbox. Writes locked to scope. SSH keys unreadable.
Full-text search across your retained reports and transcripts. Your agent's track record becomes auditable.
⌘K palette, global shortcuts, instant inbox search. Built by terminal people, for terminal people.
Every profile ships with mission, constraints, safety rails, output contract, and success criteria — so "update my deps" doesn't turn into "rewrite my repo".
Groups upgrades, reads breaking changes, runs tests, opens PRs. Never force-pushes.
Triage flaky suites, quarantine noise, propose minimal fixes.
Finds where docs and code disagree, drafts precise corrections.
Morning digest: stale branches, failing CI, security advisories.
macOS Seatbelt profiles per run. File writes restricted to the run's worktree.
Sanitized environment. SSH agents and credential helpers unreadable from inside a run.
USD soft caps, turn limits, wall-clock timeouts — enforced by the supervisor, not the model's good intentions.
Every approval, denial, and state change recorded. Nothing happens off the record.
🔍 Don't take our word for it. The Seatbelt profile, the credential
deny list and the run-environment allowlist are
published under Apache-2.0
with the tests that prove them — the suite writes a fake secret into ~/.ssh and ~/.aws,
then runs a real cat inside a real sandbox and asserts it fails. Read it, run it on your own Mac, and
see what it does not prove. Clockwork itself stays proprietary; the security boundary is open.
⏾ The honest constraint: jobs run when your machine is awake. Clockwork keeps a plugged-in laptop awake through booked windows and tells you loudly when sleep caused a miss. For true overnight runs, use an always-on machine. We'd rather tell you now than disappoint you at 2am.

Download Clockwork for Mac, connect once, book your first chore tonight.
Download Clockwork for MacApple silicon · macOS 14+ · 3.4 MB · SHA-256 checksum
brew tap vimoxshah/clockwork brew trust vimoxshah/clockwork brew install --cask clockwork xattr -dr com.apple.quarantine /Applications/Clockwork.app
brew trust is required because Homebrew refuses casks from third-party taps by
default — you are explicitly saying you trust this one.
Homebrew verifies the SHA-256 before installing, then you clear the quarantine flag
yourself — Homebrew 6 removed the --no-quarantine option, so there is no
way to skip it. You are still clearing quarantine on a binary whose hash was checked for
you, which is why this beats a raw download.
# 1. verify what you downloaded shasum -a 256 ~/Downloads/Clockwork_0.4.0_aarch64.dmg # 2. open the DMG, drag Clockwork to Applications, then: xattr -dr com.apple.quarantine /Applications/Clockwork.app # 3. launch it open -a Clockwork
Step 1 should print the hash shown in checksums-sha256.txt. If it does not match, do not install it — tell us instead. Step 2 removes the quarantine flag macOS adds to downloaded files; you are telling your Mac you trust this specific app. Only run it on a file whose checksum you just verified.
Bring your own API keys — Clockwork never marks up provider charges. Whatever Clockwork costs later, it will never be a markup on your provider usage — those stay separate bills.
Free during beta
Approvals and budget caps are never paywalled — they are the brakes on unattended code.
Not yet priced
These are the pieces teams ask for. They are built, but not for sale — I would rather find out what is worth paying for than guess at a number. Beta users keep their history either way.
Talk to us
Clockwork is proprietary software — previously FSL-1.1, now under the LICENSE in the repository. No payment is collected on this site yet.
Clockwork is an early build and I read every message. Tell me what broke, what you expected, or what would make it worth paying for.
Email mevmoksh.shah179@gmail.com · or open an issue on the Homebrew tap