localharness vs the coding-agent field

make a small local model do senior-dev work on hardware you already own — coding first, multi-role agents next
localharnessaiderOpenHandsSWE-agentClaude Code
runs on owned hardwareyes · GX10yes · Ollamayes · 100+ providersyes · model-agnosticno · cloud only
per-token cost$0 (owned)free localfree localfree local$ / subscription
edit methodsurgical edit + grepSEARCH/REPLACE difffile edit + full shellACI windowed + lintsurgical edit
test-feedback loopyes · project testsyes · lint+test healyes · in sandboxyes · run_testsyes
tuned for weak modelsyes · core focuspartialgeneralACI guardrailsn/a (frontier)
context engineeringverified window · dynamic in/out split · compaction · bail-guardrepo-map · sets ctxsandbox · condenserwindowed viewslarge frontier ctx
weak-model railsforced-commit · circling fast-fail · best-of-N · planningedit-format coercionACI guardrails
openin-houseApacheMITMIT (research)closed
role scopecoding → multi-rolecoding (pair)coding + browser/QAcoding (SWE-bench)coding + general
Where localharness fits. Everyone else needs one of three things we don't: a strong/cloud model (Claude Code), a human in the loop (aider is a pair-programmer), or a heavyweight general agent (OpenHands). SWE-agent is the research ancestor that proved models need their own interface. localharness targets the corner none of them aim at on purpose — senior-dev output from a small model you already own, with the rails and context engineering built for weak models. Coding is the proving ground; the destination is a multi-role agent harness running your own models as proper agents.
localharness is the youngest and narrowest of the five — this compares design intent and fit, not maturity. The others are battle-tested; we're purpose-built for one underserved corner. Peer capabilities per their public docs (aider.chat, OpenHands, SWE-agent / Princeton), June 2026.