Egej Vencelj Senior software engineer

Projects / My multi-agent coding setup

My multi-agent coding setup

I follow the latest industry concepts. Currently, I employ loop engineering principles: I design the loops my coding agents work in, not each prompt. A supervising agent runs them across my spare-time projects and stops for my decisions. In its first month, more than 170 of their pull requests were merged.

Fig. 1 Several tasks in flight at once. Each idea gets its own worktree, goes back to its agent until review and tests are clean, merges, and its worktree is removed. The supervisor watches every lane, and real decisions come back to me. The task names are made up.

I set it up to work on several projects at the same time and to take on fields I had not worked in before. I don't prompt the agents step by step. I design the loops they work in. My spare-time projects run on them, among them the OBS plugin, Floorcut, FairPair, my 3D-printed parts and my CV site.

The supervision loop. I talk to one supervising agent. It plans the work and gives each task its own coding agent in a clean git worktree, so tasks run side by side. It wakes on events, checks each agent, steers it or restarts a stuck one, then waits again.

The validation loop. Every change goes through an automated review, the tests and the fixes they ask for, again until it is clean. Only then does it become a pull request.

Me in the loop. Merges, deploys and real decisions stop and wait for me. Spending and merge rights are set by rules, not by an agent's judgement.

The rules I write. Small, clear changes skip the full pipeline. FairPair changes go to a running demo that I approve first, and nothing goes public without my word. Agents load my written playbooks, for my home server and for my CV's wording, when a task needs them.

Harnesses and the home server. The setup drives several agent harnesses, among them Claude Code, Codex, OpenCode and Pi. The harnesses can also run on language models I host myself. For coding I use hosted frontier models for now, because open-weight models are not there yet. The supervising agent runs in a container on my home server. Through Home Assistant's MCP server my agents can also operate and configure the house. One of them set up my 3D printer's integration, its dashboard and the print alerts.

I set up the open-source tooling, design the loops and their rules, and run my projects on it.

Result. In its first month, from 27 Sep 2026, more than 170 pull requests from it were merged. They went into four repositories: the OBS plugin, Floorcut, and FairPair's engine and web app. The OBS plugin went from its first scaffold to release 0.1.4 in about a week. Projects without a GitHub repository, such as my CV site, are merged locally and are not counted.