Clawpatch

Why it's ranked here

Clawpatch is compelling when repeatability matters more than a one-shot agent conversation. Deterministic mapping, persistent records, bounded parallel work, explicit repair attempts, and separate publication steps create an auditable workflow. Its value depends on an external coding harness, but that boundary also keeps model transport and authentication outside the tool.

What's good

The default mapper needs no model call and recognizes feature boundaries across many common language ecosystems. Reviews and revalidation request read-only provider execution. Repairs require a specific finding, reject dirty worktrees by default, record changed files and command results, and leave committing or pushing to a separate action.

Tradeoffs

Clawpatch requires Node.js 22 or newer plus an installed, authenticated coding-agent harness. Provider isolation differs, so write-capable agents still demand care with untrusted repositories. Validation only runs commands the project exposes or configuration supplies. Persistent project-local records improve resumability but add state that teams must manage alongside their source workflow.

How to use it well

Use it for maintained Git repositories where findings need triage, repairs need validation, and interrupted work must resume cleanly. Start with deterministic mapping, review a small bounded set, inspect evidence, then repair one finding at a time. It does not supply models, authentication, general CI hosting, or automatic merging.

Observed

License

MIT

Primary language

TypeScript

Packaging

ESM npm package installable globally with npm or pnpm

Interface

Command-line application with machine-readable JSON output support

Runtime requirement

Node.js 22 or newer

Provider model

Uses installed coding-agent harnesses and does not call model APIs directly

State model

Stores configuration, feature records, findings, patches, reports, runs, and locks in project-local state