What is an agent harness?
Why production agents need memory scope, token accounting, tool policy, and evals.
guides · practical context
Short, engineering-first notes on agent memory boundaries, MCP tool safety, and ERPNext context — plus honest side-by-sides against OpenClaw, Hermes Agent, and QM.
Start here
Why production agents need memory scope, token accounting, tool policy, and evals.
How MCP servers become safer when routed through policy, result caps, and ledgers.
Why ERP agents need DocTypes, fields, workflows, roles, and permissions in context.
How tenant, workspace, user, and session boundaries prevent useful memory from becoming risky.
Comparisons
Written to be useful rather than flattering — each one names what the other project does better before making Muster's case.
387.8k stars and a plugin economy against a receipted, observed edit trail. Both MIT, both self-hosted.
Seven execution backends and 40+ tools against scoped memory boundaries and eval-gated learning.
The nearest neighbour: grant-based sharing and durable sandboxes against deterministic receipts.
The measurement behind the claim: 0 of 5 self-reported edits versus an 86ms observed diff.