One install — agents that remember, coordinate, and ask by default.

A question reaches my phone — and gets answered

Watch one loop: my laptop's agent claims a task, my phone sees it, the agent asks a question, I answer from the couch, and the agent carries on.

Why the phone is a real peer, not just a viewer: a laptop saving through git and a phone saving through GitHub both follow the same rule — only save if no one changed this first. Because those two checks behave identically, both devices share one to-do list and no central server ever has to referee between them.

Replayed from the real commit history

The couch demo above is illustrative — a clean, one-loop walkthrough. This one isn't. It's replayed from the actual agentsync board and context-keeper decisions recorded while the stack was used to build itself. Step through it; every event links to the commit or PR behind it.

A week of real use

Ordinary work, run on this stack. Every item links to a commit or PR you can open and check.

1. An audit → fix → retrain loop, driven from a phone.
   An agent audited a Balatron model's optimizer, found the learning rate was being reset every time a checkpoint reloaded, locked it at load time, and re-ran — the whole cycle steered from the couch.
   the audit (dec-058)·the LR-lock fix·dec-061 follow-up
2. Two agents building in parallel on one board.
   Two agents claimed disjoint lanes on a single shared board and built on their own branches. The board's compare-and-swap refused a colliding claim with its reason, and let non-overlapping work through — no central server refereeing.
   the two-person CAS test
3. A knowledge harvest: 132 distilled lessons → 9 org items.
   A week of session-level lessons was distilled and boiled down to 9 organization-level knowledge items — each one landed through its own reviewed pull request, not a bulk dump. The org knowledge store itself is a private repo, so unlike the other items on this list you can't open it; what you can read is the promotion machinery that gated it.
   cambium's promotion gates
4. A connector outage where the discipline held.
   When the remote connector's MCP handshake started failing, the local-first servers kept working. The fix hardened the handshake so a GitHub-side outage isolates to a logged warning instead of hanging the session.
   handshake hardening

In plain terms

Four tools, four everyday analogies.

The numbers

Real figures from the projects' own test reports — honest labels, limits included. These are a hand-copied snapshot, read on 8 July 2026, not a live feed; for numbers that refresh on their own, see the live dashboard.