I built Clockwork because I was paying for Claude capacity that sat idle about 18 hours a day, while I re-typed the same repo chores every week by hand.
The idea is simple: if an agent can do the work, give it a workday. A slot on the calendar, a budget, permission rules, and a report when it's done.
Trusting something to run while I'm asleep meant the boring parts had to be real: • Runs execute inside a macOS Seatbelt sandbox, in a per-run git worktree. Writes are confined to that worktree. • The run environment is an allowlist, so SSH_AUTH_SOCK and your provider tokens never reach the agent process. • Risky steps pause and ask instead of failing silently or ploughing on. • Hard budget caps in dollars, turn limits and wall-clock timeouts, enforced by the supervisor rather than the model's good intentions. • You can check all of that rather than believe it - the sandbox, the credential deny list and the env allowlist are Apache-2.0 in the repo, and the tests write a fake secret into `~/.ssh` and `~/.aws`, then run `cat` inside a real sandbox and assert it fails. The rest of the app is source-available under a proprietary licence, so please don't call it open source; I'd rather be precise than flattering.
Honest limits, up front: • Runs need your Mac awake. It holds off idle sleep during booked windows when plugged in, and tells you loudly when a miss happened instead of hiding it. • It isn't notarised yet — an Apple certificate is $99/year and this is an early build - so you clear the quarantine flag by hand. The install docs say exactly why. • Apple silicon only, for now. It's free. There's no paid tier you can buy today. I'd genuinely like to hear what you'd want before trusting an agent with more of your week.
PH 用户
Are there / will there be webhooks too? Sometimes I want something scheduled every time there is a new release for example.
PH 用户
'give an agent a workday' idea is actually a great framing. makes autonomous coding feel much more practical than just letting agents run endlessly.
PH 用户
Congrats on your PH launch! Love the OSS spirit!
I am running a lot of agents and unfortunately I have to babysit them and I often go to bed late because I want to just make sure I get one more task going before I go to bed. Clockwork seems to fill this gap for me so I will definitely try it!
I am curious how Clockwork handles a recurring slot when the previous run is still waiting for approval: skip it, queue it, or start another isolated worktree?
PH 用户
the wall-clock timeout is the part I'd want to understand better. if an agent is mid-commit or mid-rebase when its slot runs out, does the supervisor let it finish the git operation before killing it, or does it cut the process wherever it happens to be and leave the worktree in a half-done state for the next run to deal with
PH 用户
interesting product! do u have any plans for when u'll open access to the paid plans?
I built Clockwork because I was paying for Claude capacity that sat idle about 18 hours a day, while I re-typed the same repo chores every week by hand.
The idea is simple: if an agent can do the work, give it a workday. A slot on the calendar, a budget, permission rules, and a report when it's done.
Trusting something to run while I'm asleep meant the boring parts had to be
real:
• Runs execute inside a macOS Seatbelt sandbox, in a per-run git worktree. Writes are confined to that worktree.
• The run environment is an allowlist, so SSH_AUTH_SOCK and your provider tokens never reach the agent process.
• Risky steps pause and ask instead of failing silently or ploughing on.
• Hard budget caps in dollars, turn limits and wall-clock timeouts, enforced by the supervisor rather than the model's good intentions.
• You can check all of that rather than believe it - the sandbox, the credential
deny list and the env allowlist are Apache-2.0 in the repo, and the tests write a fake secret into `~/.ssh` and `~/.aws`, then run `cat` inside a real sandbox and assert it fails. The rest of the app is source-available under a proprietary licence, so please don't call it open source; I'd rather be precise than flattering.
Honest limits, up front:
• Runs need your Mac awake. It holds off idle sleep during booked windows when
plugged in, and tells you loudly when a miss happened instead of hiding it.
• It isn't notarised yet — an Apple certificate is $99/year and this is an
early build - so you clear the quarantine flag by hand. The install docs say exactly why.
• Apple silicon only, for now. It's free. There's no paid tier you can buy today. I'd genuinely like to hear what you'd want before trusting an agent with more of your week.
I am running a lot of agents and unfortunately I have to babysit them and I often go to bed late because I want to just make sure I get one more task going before I go to bed. Clockwork seems to fill this gap for me so I will definitely try it!
I am curious how Clockwork handles a recurring slot when the previous run is still waiting for approval: skip it, queue it, or start another isolated worktree?