Skip to content

v1.6.0 — Buddy System: one Opus Boss, many providers

Latest
Latest

Choose a tag to compare

View all tags
@asiridalugoda asiridalugoda released this 18 Oct 01:38
v1.6.0
e97d241
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The loop's maker/checker split now spans model providers. Say "autonomous-loop buddy system" and one Opus session — the Boss — runs each round across Codex, Grok, Sonnet and Haiku, so many lanes build at once and no lane is reviewed by the provider that built it.

The seats

  • Boss (Opus) — rulings, briefs, local merges, gates, git, the PR. Nothing a seat claims counts until the Boss re-runs the gates on the integrated head.
  • Astra (Codex) — lanes with disjoint files, contracts, risks and a test plan per round.
  • Two build sides in parallel — Sonnet leads with a Haiku swarm on exact-change satellites, and Sol orchestrating Luna builders in standalone clones on lanes whose contracts are settled.
  • Grok reviews lanes and runs the security round; Sol is the merge reviewer when Codex built nothing; Luna re-reviews Claude-built fixes.

Degrade, don't wait. A provider probe picks FULL, NO-CODEX, NO-GROK or CLAUDE-ONLY every round and whenever a seat hits its limit. Seats move to the available column without waiting for a reset — a provider limit is never a pause or a strike.

One stacked PR per round. Each push round ends in a PR based on the previous round's branch, so building never waits for a merge. The stack merges at the end, only on your word.

Flags (they compose): --mode <full|no-codex|no-grok|claude-only> pins a ceiling — claude-only never probes and sends no code to another provider · --local pushes nothing · --rounds <n> bounds a scheduled run · --plan <path> builds an existing plan · relay sends off-machine gates to a relay worker. Active flags are recorded on BOARD.md, so a resumed run never widens provider access or push authority on its own.

Project settings stay in your repo. A setup wizard writes a ## Buddy System profile into docs/loop/LOOP.md — commit identity, gate, copy ratchet, security-critical areas, push authority. The skill carries no project data.

Cautions. In any mode but CLAUDE-ONLY, code is read by xAI and OpenAI models. The Codex build side runs with full access inside standalone clones (cloud credentials stripped); pin --mode no-codex where that isn't acceptable. Grok and Codex CLIs are optional — without them the build runs on Claude seats only.

Runbook: references/buddy-system.md · seat scripts and briefs: buddy-system/ · PR #6.

Assets 2
Loading