Documentation
Install & prerequisites
cut3 needs `gh` (authenticated) and a running T3 Code service. Install the service with `t3 service install`, sign in to GitHub with `gh auth login`, then run the interactive setup.
npx cut3 initInteractive setupHow it works
cut3 is a short-lived cron job: on each tick it reconciles the work that should be happening against the threads T3 Code already has, and dispatches a prompt for anything new. cut3 decides WHEN; T3 decides WHERE and HOW the agent runs. In v1 the source of work is GitHub issues — for each open issue carrying the configured label it dispatches a thread on a deterministic branch (`cut3/issue-42`), and T3 cuts a worktree from it for your OpenCode agent. The same loop can later drive other cues (CI, a daily summary) by pointing it at a different source.
Command reference
cut3 initConfigure repo, project, label, model, intervalcut3 runReconcile once: start threads for new eligible issuescut3 run --dry-runShow what would happen; start nothingcut3 statusShow live cut3 threads and the concurrency budgetcut3 cron installRegister the scheduled `cut3 run`cut3 cron statusShow whether the schedule is installedcut3 cron removeUnregister the scheduleConfiguration
Config lives at `~/.config/cut3/config.json` (`%APPDATA%\cut3\config.json` on Windows). It holds your repo, the eligibility label, the resolved T3 project id, the model selection, concurrency and interval. No secrets are stored — bearer tokens are minted fresh on every run and never persisted.