Project releases
MetaHarness 0.4.4 documents 115 merged PRs in one catch up release
MetaHarness mints a custom agent harness for any repository. Release 0.4.4 is the first release entry since 0.1.3 and covers roughly two months of shipped work, with every claim traceable to a pull request number.
GitHub activity: · Published:
What MetaHarness is
Generic coding agents know nothing about your repository. MetaHarness reads the actual file layout and generates a harness for it: a repo aware CLI, agents, skills, a local MCP server, project scoped memory and release verification.
The output is an npm publishable package with your name on it and your own npx command.
What changed in 0.4.4
The GitHub releases page had fallen behind npm. This entry documents everything between 0.1.3 and 0.4.4 — about 115 merged pull requests — organised by theme rather than chronology, with PR numbers attached.
The largest theme is Darwin Mode, the evolutionary engine that improves the harness itself, including a defensive variant applied to security response.
Get started
Node.js. Generate a harness from a template:
npx metaharness my-bot --template vertical:coding --host claude-code
cd my-bot && npx . --helpExpected result: a generated harness directory whose own CLI prints its command list.
If you would rather be asked questions than pass flags:
npx metaharness --wizardYou can also score a repository before generating anything:
npx metaharness score <repo>Host support differs. Claude Code gets MCP plus hooks plus three scope settings; Codex gets MCP through its TOML config and no hooks; pi.dev has no MCP by design. Check the host table before assuming a surface exists.
Use it today
Practical case: a bounded repository audit. Generate a harness for the repo, delete the agents and tools you do not want, and hand the result to a reviewer who gets the same repo tuned agent you have.
Acceptance test: run the generated CLI's help command in a clean checkout. If it lists commands that reference your repository's actual structure, the generation step understood the repo.
Push it further
Experimental commentary. Darwin Mode is a harness that edits itself against an evaluation. That is genuinely powerful and genuinely risky; the gate matters more than the mutation.
Falsifiable test: run an evolution cycle with the promotion gate disabled and again with it enabled. If the gate never rejects anything, it is decoration.