Shell-verified acceptance
The spec defines the exact commands that must pass. The agent does not decide for itself whether it is done.
See it in action
From goal to commits, unattended.
How it works
From spec to commit, unattended.
01
Describe your goal
Start with a vague goal. owloop spec reads your codebase, asks clarifying questions, and drafts a concrete spec.
02
Review the spec
Edit the generated spec: requirements, shell-verifiable acceptance criteria, exclusions, and stuck behavior.
03
Start the loop
owloop run opens a full-screen TUI with an animated owl, iteration counter, token budget, and real-time status.
04
Verify & commit
The agent runs the exact shell commands from your acceptance criteria. Only green means commit.
05
Review in the morning
Open the worktree diff and the HTML report. Merge when ready. Go back to sleep.
Features
Built for reliable overnight progress.
Fresh context per iteration
Each task starts clean. No accumulated context drift, no accidental side effects.
Worktree isolation
Everything happens in a disposable git worktree. Your main checkout is never touched until you choose to merge.
Deterministic completion
Completion is a grep-able <promise>DONE</promise>, not a model guess.
Fix-loop detection
Catches death spirals when the same files are edited repeatedly without progress.
Token budget cap
Set --max-tokens and --max-duration. The loop stops before your wallet does.
Morning report
3
specs completed
14
commits
0
failures
12.4k
tokens used
Compared to
Pick the right loop for the job.
| owloop | /goal |
|
|---|---|---|
| Completion check | grep <promise> |
Haiku judgment |
| Best for | Backlog of verifiable tasks | One focused task, user present |
| Spec format | Constraint-oriented | Free-form |
| Context | Fresh per iteration | Same session |
| Isolation | Worktree | None |
Put your backlog to work overnight.
Install owloop, write your first spec, and let Ollie handle the rest.