Show HN: Mainplane – Agent in Go that lives on your old PC, drives your laptop
Hi HN, I'm Alexander. Yes, this is another agent harness. Here is why I built one anyway. I was engineer #2 at Browser Use, where I built our agent harness and the evals behind it, including BU Bench, which became a default benchmark for browser agents. I left in September to build Mainplane. The problem: local agents die with your laptop, and cloud agents can't reach your work. Many cloud platforms ask you to "select a repository", but my work is not that simple. I work across a deskt
Read original source
Source record
Recorded metrics
points · 3 votes
2026-10-27 12:45:23.150Z
cumulative since publication
Research analysis
Project record
Repository: mainplane-ai/mainplane. Source account: Hi HN, I'm Alexander. Yes, this is another agent harness. Here is why I built one anyway. I was engineer #2 at Browser Use, where I built our agent harness and the evals behind it, including BU Bench, which became a default benchmark for browser agents. I left in September to build Mainplane. The problem: local agents die with your laptop, and cloud agents can't reach your work. Many cloud platforms ask you to "select a repository", but my work is not that simple. I work across a deskt
Observed adoption & comparisons
Source votes: 3 votes (Oct 27, 2026 UTC; cumulative since publication); previous same-scope observation: 3 (Oct 27, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “Show HN: Cerea – yet another self-hosted LLM chat front end” (Show HN, Nov 5, 2026); “Show HN: Lantern Lattice – the call graph from your compiler, for coding agents” (Show HN, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.