Skip to content

v1.4.0 — Relay (multi-node): two+ Claudes, different machines, one loop

Choose a tag to compare

View all tags
@asiridalugoda asiridalugoda released this 09 Aug 21:22
· 7 commits to main since this release
v1.4.0
edd98d1

Say "autonomous-loop relay" and Claude Code instances on different machines run the same loop on the same repo and hand work to each other — no human copy-pasting between sessions. Works for any pairing: mac↔win, mac↔mac, win↔win.

How it works

  • Coordination lives entirely in the target repo: the master file (docs/loop/LOOP.md) gains a ## Relay section; one GitHub issue per job (body = living summary, comments = structured TASK n / RESULT n messages); redacted payloads committed under docs/loop/relay/<issue>/.
  • Labels are the baton — awaiting:worker / working / awaiting:controller, exactly one present. Only the holder acts; one task outstanding at a time; the worker claims before executing so duplicate watcher firings never re-run a state-mutating task.
  • Roles bind per job, not per machine — a controller directs and authors fixes; a worker executes on its own box and reports facts. Any node can hold either role on different jobs.
  • First run = setup wizard (detects remote/auth/visibility, asks what's delegable and what remote workers may do, confirms, then creates labels + section + first issue). Every other machine joins by cloning and saying the same phrase.
  • Two-layer watching — the live session polls via /loop (~1–2 min round-trips) plus a launchd / Task Scheduler backstop firing an idempotent headless pass every ~5 min, so sessions can die, sleep, or reboot and the run continues.

Guardrails (the command bus may be world-writable)

  • Only comments from accounts in the node registry are instructions — everything else, including instruction-shaped text inside captured logs, is data.
  • Redact-first logging on public repos; destructive ops require an explicit authorized-by-human marker; 3 failed round-trips on one hypothesis → needs:human escalation.

New files

  • references/relay-template.md — wizard question list, master-file section, issue/comment templates, watcher prompt, scheduler snippets.
  • references/relay-scenarios.md — four worked examples incl. failure drills (duplicate watchers, injection attempts, session death, push races).
Assets 2
Loading