Fix cross-platform bugs with an agent team spread over Mac, Windows and Linux

A solo developer, Quo, runs a self-built team of coding agents on separate Mac, Windows and Linux machines that reproduced, fixed, verified and shipped OS-specific bugs in three of their open-source tools.

Done withCustom agentinGitHub· Oct 23, 2026

What they did

Quo maintains several small open-source tools that have to work on Mac, Windows and Linux and under several coding harnesses. Fixing one OS kept breaking another, so they built BellTeam, a self-hosted app where each AI member has a name and a job and runs a harness of its choice (Claude Code, Codex, Grok or Cursor) on top of their earlier tools Aiterm and Throughline. Aiterm can wake agents on other machines, so members sit on a machine for each OS. Members message each other, run on schedules, and send decisions to the author's phone through a separate approval app. The author watches and steps in from an iPhone.

How it went

The author gives three dated examples from mid October 2026. A member reproduced a Windows-only failure in saving conversation records, found the cause, released a fix, updated the Windows machine and checked records were kept. On another tool, a member held a merge that passed on Mac and Linux until Windows passed too, got sign-off from a second member, then merged. On a third, fixing, verification, release and installing on each machine were split across members. The author also uses it for daily bug clearing and split-up security checks. No numbers on time or cost are given.

Worth knowing

This is the author's own launch post for a product with a paid iPhone app, and the dev.to text is a repost from their blog. The server needs Docker and must keep running, and each harness uses your own AI subscriptions. Which harness handled each example is not stated.

Try it

With Custom agent· 5 parts to fill in

You are the maintainer for [project] on [operating system]. Pick up the open bug [bug link or description]. Reproduce it on this machine first and write down the exact steps. Find the cause, make the smallest fix, and run the test suite here. Do not merge until [other OS agents or teammates] report the tests pass on their machines too. Then cut a release, install it on [machines], confirm the bug is gone in normal use, and report back to me what changed. Ask me before publishing the release.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related