An auto-adaptive
coding-agent harness.
agntro classifies each task and scales its pipeline depth to match — from a
single search → summarize for a research question, to a full
multi-model plan → code → review ladder for a complex feature.
Built on Elixir/BEAM for supervision, crash recovery, and concurrent agents. MCP-native codebase understanding. An HTTP/WebSocket backend so any frontend can drive it — desktop, CLI, or web.
the pipeline scales with the task
trivial
Research question / audit
A question about the codebase, not a change to it.
search graph → summarize · ~3 calls
simple
Small, localized change
A single edit with a drift check.
plan → code → drift review · ~10 calls
medium
Feature with a contract
Spec extraction anchors the work; a contract-verifier runs the tests.
spec → plan → test → code → contract-verify · ~25 calls
complex
Multi-component feature
A planning ladder with variations, delegated sub-tasks, and the full review panel.
spec → plan-ladder → delegate → test → code → full review · ~100 calls
{ adaptive }
Auto-adaptive routing
Every task is classified before any work begins. A research question
doesn't trigger a coding pipeline; a complex feature doesn't get a
single-pass plan.
{ mcp }
Codebase-grounded
Code understanding comes from the codebase-memory graph — structural
search, call paths, architecture — not from re-reading files every turn.
{ beam }
Built on Elixir/OTP
Supervision trees, crash recovery with checkpointed state, and
concurrent agent processes. The harness survives what kills a script.