CritiqueCode Is Now Open Source
The author agent, controller-owned review loop, verified repair machinery, and repository intelligence are now public under MIT.
CritiqueCode is open source under MIT. The public repository contains the interactive author agent, local terminal and browser sessions, change-capsule and evidence code, repository intelligence, and the controller-owned review and verified-repair loop.
The code is at github.com/repath500/critique-code. The npm package stays @critiquedotsh/harness, and the binary stays critique-code. Existing installs do not need to change.
Why open the harness
A verification product should be inspectable. If an agent says its author cannot quietly grade its own work, developers should be able to read the boundary: where author output stops, where evidence begins, how findings are promoted, and when a repair is allowed to apply.
That boundary is the point of CritiqueCode. The author writes into your working tree and can request checks with your approval. Its transcript and self-reported checks are not promoted to evidence. A separate controller captures the change, runs review, records uncertainty, and verifies repairs before completion can be accepted.
What is in the repository
- Interactive author agent and command surface
- Local TTY and browser sessions
- Change capsules, preflight, evidence, review, and repair controllers
- Repository intelligence and capability discovery
- Public protocol schemas and package build
- Critique Inference remains a hosted model route
- Local provider keys remain supported
- The Critique CLI sidecar remains a separate product and package
Install it or build it
Install
npm install --global @critiquedotsh/harness
cd /path/to/your/project
critique-code login
critique-codeRun it inside the repository you want CritiqueCode to edit.
Build from source
git clone https://github.com/repath500/critique-code.git
cd critique-code
pnpm install
pnpm buildNode.js 20.19+ and pnpm 10 are required.
The first public release is intentionally the local author harness, not the private Critique platform monorepo. That gives contributors a clean repository with one product boundary and no hosted control-plane code mixed into the review kernel.