Skip to content

Releases: vimoxshah/clockwork

Clockwork v0.5.0

Choose a tag to compare

@github-actions github-actions released this 05 Sep 23:37
5a7f9a8

Clockwork v0.5.0

The day after launch, four public claims did not match the code. Each is now wired, tested, and proven against Claude Code CLI 2.1.261 through the production runner. Records: ADR-034 and ADR-035 in decisions/DECISIONS.md; matrix in spikes/reports/T007-engine-contract-matrix-2.1.261.md.

What changed

  • Approvals hold. A gated tool call pauses the run and waits for you, for the run's remaining wall-clock budget, then fails safe. Before 0.5.0 this never fired on a real engine.
  • Every engine runs inside the macOS Seatbelt sandbox (Claude, Codex, OpenCode, Hermes, and the BYOK agent's shell): writes only to the worktree, scratch and tool caches; credential paths unreadable. CW_SANDBOX=off is the only escape and is logged, journaled, and stamped on the report. Before 0.5.0 the profile existed but nothing applied it.
  • The policy floor sees every Bash call. A fail-closed PreToolUse hook refuses deny-list floor hits (force-push to a protected branch, package publishing) in every permission mode, ~60 ms per call. It also pins disableAllHooks: false, so a repo's own settings cannot switch it off.
  • Interrupted runs keep their worktree. A timeout or cancel mid-rebase preserves the working state; the report says what was kept and why.
  • BYOK credentials travel over the daemon⇄runner stdin channel, never the environment (a process's exec-time env is readable via sysctl by any same-user process).
  • Codex runs with its own sandbox off while Clockwork's is on (macOS will not nest two Seatbelts). Hermes's working directory is pinned to the worktree. Tool caches are redirected under ~/.clockwork/cache for npm, pnpm, yarn, pip, cargo, go, gem, bundle, uv, poetry, gradle, composer and nuget.

Known limits (documented in docs/security.md)

Repo-declared MCP servers that run shell are not matched by the Bash-only hook; the loopback permission bridge has no per-run bearer token yet; runs inherit HOME, so your own Claude Code allow rules and session hooks apply unattended; BYOK configs that read the key from an env var keep it in the daemon's exec-time env (keychain-backed configs are fully closed); network is allowed inside the profile for every engine.

Verify before installing

shasum -a 256 -c checksums-sha256.txt

Clockwork_aarch64.dmg is the same file as Clockwork_0.5.0_aarch64.dmg under a stable name (used by the landing page's "latest" link).

Install

  1. Download the DMG (Apple Silicon, macOS 14+), open it, drag Clockwork to Applications.
  2. Run the daemon from this tag: git clone https://github.com/vimoxshah/clockwork && cd clockwork && git checkout v0.5.0 && pnpm install && pnpm build && node packages/daemon/dist/main.js (Node 22+; needs one provider CLI: claude, codex, opencode or hermes).
  3. Pair the app with the daemon using ~/.clockwork/api-token.

Signature status

This build is unsigned (ad hoc). macOS will ask you to confirm the app under System Settings → Privacy & Security on first launch. Homebrew (brew tap vimoxshah/clockwork && brew install --cask clockwork) verifies the checksum for you.

Clockwork v0.4.0

Choose a tag to compare

@github-actions github-actions released this 03 Sep 05:09

Clockwork v0.4.0

Verify before installing

Checksums are published with this release. Verify the download:

shasum -a 256 -c checksums-sha256.txt

Install

  1. Download Clockwork_0.4.0_aarch64.dmg (Apple Silicon)
  2. Open the DMG and drag Clockwork to Applications
  3. Launch — pair with your local daemon using ~/.clockwork/api-token

Requirements

  • macOS 14+ · Apple Silicon · Node 22 + one provider CLI (claude/codex/opencode/hermes)

Signature status

See checksums-sha256.txt to verify integrity. If this build is unsigned,
macOS Gatekeeper will ask you to confirm the app in System Settings →
Privacy & Security on first launch.

Known limitations

Jobs execute when the machine is awake.

Clockwork v0.3.1

Choose a tag to compare

@github-actions github-actions released this 26 Aug 13:29

Clockwork v0.3.1

Install

  1. Download Clockwork_0.3.1_aarch64.dmg (Apple Silicon)
  2. Open the DMG and drag Clockwork to Applications
  3. Launch — pair with your local daemon using ~/.clockwork/api-token

Requirements

  • macOS 14+ · Apple Silicon · Node 22 + one provider CLI (claude/codex/opencode/hermes)

Signature status

See checksums-sha256.txt to verify integrity. If this build is unsigned,
macOS Gatekeeper will ask you to confirm the app in System Settings →
Privacy & Security on first launch.

Known limitations

Jobs execute when the machine is awake.

Clockwork v0.3.0

Choose a tag to compare

@github-actions github-actions released this 26 Aug 13:06

Clockwork v0.3.0

Install

  1. Download Clockwork_0.3.0_aarch64.dmg (Apple Silicon)
  2. Open the DMG and drag Clockwork to Applications
  3. Launch — pair with your local daemon using ~/.clockwork/api-token

Requirements

  • macOS 14+ · Apple Silicon · Node 22 + one provider CLI (claude/codex/opencode/hermes)

Signature status

See checksums-sha256.txt to verify integrity. If this build is unsigned,
macOS Gatekeeper will ask you to confirm the app in System Settings →
Privacy & Security on first launch.

Known limitations

Jobs execute when the machine is awake.

Clockwork v0.2.0

Choose a tag to compare

@github-actions github-actions released this 26 Aug 09:22

Clockwork v0.2.0

Install

  1. Download Clockwork_0.2.0_aarch64.dmg (Apple Silicon)
  2. Open the DMG and drag Clockwork to Applications
  3. Launch — pair with your local daemon using ~/.clockwork/api-token

Requirements

  • macOS 14+ · Apple Silicon · Node 22 + one provider CLI (claude/codex/opencode/hermes)

Signature status

See checksums-sha256.txt to verify integrity. If this build is unsigned,
macOS Gatekeeper will ask you to confirm the app in System Settings →
Privacy & Security on first launch.

Known limitations

Jobs execute when the machine is awake.

Clockwork v0.1.3

Choose a tag to compare

@github-actions github-actions released this 23 Aug 11:58

Clockwork v0.1.3

Install

  1. Download Clockwork_0.1.3_aarch64.dmg (Apple Silicon)
  2. Open the DMG and drag Clockwork to Applications
  3. Launch — pair with your local daemon using ~/.clockwork/api-token

Requirements

  • macOS 14+ · Apple Silicon · Node 22 + one provider CLI (claude/codex/opencode/hermes)

Signature status

See checksums-sha256.txt to verify integrity. If this build is unsigned,
macOS Gatekeeper will ask you to confirm the app in System Settings →
Privacy & Security on first launch.

Known limitations

Jobs execute when the machine is awake.

Clockwork v0.1.0

Choose a tag to compare

@vimoxshah vimoxshah released this 23 Aug 10:16

Clockwork v0.1.0 — first public beta

The calendar where your AI agents show up for work.

Highlights

  • Month-calendar scheduling for agent jobs (recurring, queue, missed-run policies)
  • Providers: Claude Code · Codex CLI · OpenCode · Hermes Agent — detected automatically
  • 13 built-in agent profiles (Dep Surgeon, Test Doctor, Security Auditor, …)
  • Human calendar overlay via read-only ICS subscription
  • Human-in-the-loop approvals, budget caps, sandboxed per-run worktrees
  • ⌘K command palette, instant inbox search, light/dark themes

Install

  1. Download Clockwork_0.1.0_aarch64.dmg below (Apple Silicon, macOS 14+)
  2. Verify: shasum -a 256 against checksums-sha256.txt
  3. Open the DMG → drag Clockwork to Applications → launch
  4. Pair with your local daemon using ~/.clockwork/api-token

Signature status

This build is unsigned (no Apple Developer certificate configured yet).
On first launch macOS will block it once — right-click the app → Open, or
use "Open Anyway" in System Settings → Privacy & Security. See docs/install.md.

Known limitations

  • Jobs run only while your Mac is awake (plug in for scheduled windows)
  • Recurring external calendar events show as a single base occurrence