Documentation
README
Delegate scoped issues to SWE-AF
You are the main harness. SWE-AF is the sub-harness: it implements one fully-scoped issue per call on an isolated branch, using cheap models, and hands the branch back. You keep planning, merging, review, and CI.
When to delegate (and when not to)
Delegate an issue only when ALL of these hold:
- The change is fully specified: you can name the files, the behavior, and the acceptance criteria without the sub-harness needing to plan anything.
- It is independent of your other in-flight edits (no shared files with another delegation or with your own uncommitted work).
- The repo is reachable by the SWE-AF node (same machine or shared volume) and has at least one commit.
This is the opening of the README. Read the full README on GitHub.