Gene-based self-evolution loop for a coding agent repo

What they did

They installed the Evolver CLI globally from npm and ran it inside an existing git repository, letting the engine treat the repo as the substrate for agent self-evolution. Instead of hand-editing prompts and skill docs, they let Evolver encode experience as Genes and Capsules under the GEP protocol, so each change became an auditable evolution asset rather than a one-off tweak. They then inspected the resulting evolution trail to see which genes activated and how the agent's behavior shifted across iterations, using the repo's own history as the feedback signal. The workflow stayed local: install, run in the repo, review what the engine proposed and recorded, and keep the artifacts under version control alongside the code they affect.

How it went

Produced a reviewable trail of evolution assets instead of scattered prompt edits, with changes traceable back to specific genes. Polish level depends heavily on how much repo context the engine is given; the loop is usable but the quality of proposed genes varies, and results are best treated as drafts for human review rather than automatic merges.

Worth knowing

Evolver is moving from fully open source to source-available for future releases, so pin a version you can still use under its original terms. It needs Node.js 18+ and a git repo with meaningful history to learn from. Gene quality is uneven and should be reviewed before adoption; there is no guarantee the engine's proposals fit your domain without curation.

Wiring

Install Node.js 18+ and run npm install -g @evomap/evolver. Change into the target git repository so Evolver can read its history and files as context. Run evolver from the repo root; the engine reads repo state, proposes genes and capsules under the GEP protocol, and records an audit trail. Keep generated artifacts in version control next to the code they affect, and gate any application of proposed changes behind human review of the diff.

Try it yourself

Install Evolver globally with npm install -g @evomap/evolver, then run evolver inside this repository. Review the genes and capsules it proposes, summarize which ones map to real recurring problems in this codebase, and flag any that look like noise or overfitting to a single commit. Do not merge or apply any proposed change without showing me the diff and rationale first.