Why Miton
Models keep improving. A better harness compounds every improvement.
Miton is the next level of harness: built to extract better work, lower waste and more trustworthy agency from every model connected to it.
01 / Ground-up architecture
A project system cannot be an afterthought inside an editor fork.
Miton is its own Tauri and React application, not a fork of VS Code or a wrapper around another agent harness.
Why it matters: Miton can route intent into the right workspace while keeping Chat, Goals and project knowledge coherent.
02 / Model intelligence
The best model is a decision, not a brand allegiance.
Miton scores eligible models for each task while respecting provider availability, user routing posture and model capabilities.
Why it matters: Cheap work can stay cheap; difficult work can earn stronger reasoning; the boundary remains visible and controllable.
03 / Token economics
The waste around a model matters as much as its published price.
Miton condenses context, preserves cache-friendly prefixes, records spend and supports limits so frontier tokens are used deliberately.
Why it matters: Less repeated context, warmer caches and deliberate routing make cost a product outcome rather than a billing footnote.
04 / Local models
Private execution deserves a first-class harness and an honest limit.
Local providers participate in the same capability checks and routing controls as hosted providers without pretending every model suits every task.
Why it matters: Local models are neither ignored nor asked to bluff through work better suited to an allowed hosted model.
05 / Safety before agency
A capable agent needs more brakes, not fewer visible decisions.
Miton combines permission policy, injection checks, secret isolation, audit events and recoverable project actions.
Why it matters: Permissions, injection checks, secrets and egress can be inspected where trust is actually granted.
06 / Project cohesion
The work should survive the surface used to produce it.
Chat, Canvas, Writer, Automation and Code operate on the active project and share project goals, knowledge and conversation context.
Why it matters: A design decision can become a runbook, workflow and code change without turning into four unrelated chats.
The model is a component. Miton is the system that makes it useful.
See the system in real desktop evidence, then inspect how implemented beta behaviour differs from the beta release gate and the v1 programme.