Documentation
Cyberine's developer documentation — install, dispatch, judge, ship.
Cyberine dispatches one task to many agents, judges the results, and ships the winner.
Where things are
- Usage — the recipe book, generated from the repo-root
USAGE.md. Every shipped feature has a run recipe there, plus the full environment-variable table. - Task manifest spec — the normative shared task-manifest format
cyberine and the
nf-tasksskill both read and write. - Providers — one page per provider with its live-probed API contract (migrating in T669).
- Design notes — the decision records behind the architecture (migrating in T669).
The shape of a run
A Task fans out to every registered Agent in parallel. Each key-loop worker runs a
tool-calling loop against an OpenAI-compatible endpoint; each CLI worker spawns a headless coding
agent inside a host sandbox. A Judge then decides. DiffJudge is the one that gates on
machine-checkable evidence: it applies every candidate diff in a throwaway git worktree and
keeps the one that both applies and typechecks.