What does a “score” actually look like?
What does a “score” actually look like?
Every criterion — derived from your own traces, not invented by us — gets a pass/fail with a
confidence. Those roll into one verdict on the whole run: a critical failure sinks it. Below a
threshold of human labels, a judge is marked
unvalidated rather than trusted, so you always
know which verdicts to believe.Is my data uploaded anywhere?
Is my data uploaded anywhere?
No. Traces stay on your machine; Helix reads them locally. When it judges, it reasons on your own
coding agent’s model, so we hold no provider key and add no inference bill. The shipped package
has no analytics. The hosted Platform is opt-in, through the separate
mutagent CLI.What's the difference between the two forms?
What's the difference between the two forms?
The Plugin installs into the coding agent you already use. The
Standalone binary is proprietary and is its own coding agent.
Both run the same loop.
Do I need traces to start?
Do I need traces to start?
How do I remove it?
How do I remove it?
Plugin: delete the skill directories under
.claude/ and remove the Helix section from your
CLAUDE.md. Standalone: curl -fsSL https://install.mutagent.io/helix | bash -s -- uninstall.Which lifecycle skills ship, and are they published?
Which lifecycle skills ship, and are they published?
Helix bundles the full loop — the orchestrator plus AgentSpec, Builder, Evaluator, Diagnostics,
and Optimize — installed through the
mutagent CLI. Two skills also publish on
npm and run on their own: @mutagent/evaluator
and @mutagent/diagnostics.