Your agent, on a schedule.
cut3 is a tiny cron that hands T3 Code its cue. Point it at labelled GitHub issues, a flaky CI run, or a morning summary — T3 spins up a worktree and your OpenCode agent gets to work.
$
Read the docs →npx cut3 initPut it to work on
- GitHub issues
- Label an issue `agent:ready` and cut3 starts a thread on branch `cut3/issue-42`. This is the recipe that ships today.
- Babysit CI
- Poll for failing runs and hand the agent the latest one to investigate.
- Morning summary
- A daily cue that summarises a todo list, recent commits, or an inbox.
Why it stays small
- Reconciliation, not a daemon. A short-lived `cut3 run` on a native cron. No resident process, no queue.
- T3 does the heavy lifting. Threads, worktrees, branches and agent sessions are all T3 Code — cut3 just decides when.
- Stateless by design. A deterministic join key (the git branch, for issues) is the source of truth. No database, no stored tokens.