Introduction
Styre is an open-source harness for the software lifecycle. You hand it a structured ticket from Linear or Jira; it drives that ticket through design, implementation, verification and review on a real branch in your repo, and exits when a pull request is open. You merge it.
What it does not do
Section titled “What it does not do”Styre never merges. The operator merges every pull request personally, and Styre will not push
to your default branch. Continuous integration is reported — styre run takes one best-effort
snapshot of check status when the PR opens — but it is not a gate the run waits on.
The loop
Section titled “The loop”A run advances through five phases — design, implement, verify, review, PR — journaling each step before it executes. If a step has already succeeded, a replay returns the recorded result rather than running it again, which is what gives you crash-resume for free.
styre run ENG-482Verdicts at each stage come from ground truth — build output, the test and acceptance-criteria gates, and an independent reviewer step — never from an agent reporting on its own work.
Requirements
Section titled “Requirements”| Requirement | Detail |
|---|---|
| Issue tracker | Linear or Jira |
| Code host | GitHub only |
| Model provider | Claude or Codex, under your own API key |
| Platform | macOS or Linux |