Evolver

Why it's ranked here

This is a credible orchestration layer for teams that want repeatable agent improvement without surrendering every change to automation. Offline operation, human review, recorded outcomes, rollback-aware Git integration, and multiple runtime hooks form a practical workflow. The obfuscated core and announced licensing shift weaken transparency and long-term adoption confidence.

What's good

The boundary is unusually clear: Evolver generates guidance but does not automatically patch source. Review mode preserves human control, while continuous mode supports unattended cycles. Git provides rollback and change-scope safeguards. Local operation needs no hub connection, and runtime hooks cover Cursor, Claude Code, Codex, Kiro, opencode, and OpenClaw.

Tradeoffs

Every run requires a Git repository. Codex integration lacks raw session transcripts, so Evolver falls back to workspace memory and its own outcome history. The documented Node requirement conflicts with the package metadata, which demands a newer runtime. Most importantly, the main evolution implementation is obfuscated, and future releases are planned to become source-available.

How to use it well

Use Evolver when an agent already produces useful logs and you want controlled, repeatable guidance for later attempts. Start with single runs and human review, then adopt continuous operation after inspecting recorded outcomes. It suits Git-based agent projects and runtime-hook workflows. It does not replace a coding agent, apply patches, or provide full Codex request routing without the separate proxy setup.

Observed

License

GPL-3.0-or-later for the published package; the README says future releases will transition to source-available terms.

Primary language

CommonJS JavaScript running on Node.js.

Packaging

Published as the @evomap/evolver npm package with a global evolver executable.

Runtime requirement

package.json requires Node.js >=22.12, while the README states Node.js >=18.

Interfaces

Provides a CLI, agent-runtime hooks, a proxy mailbox API, and model-provider-compatible HTTP routing.

Platform integrations

Documents hooks or native integration for Cursor, Claude Code, Codex, Kiro, opencode, and OpenClaw.

Testing surface

The npm test script runs JavaScript test files with Node’s built-in test runner.

Source structure

The central evolution source supplied in the repository text is obfuscated, while configuration, update, locking, proxy, and transaction modules are readable.