Skip to main content

CodeEvolve

Evaluate how a codebase evolves from git history — taxonomy & phylogeny, Lehman/ecological signals, technical debt, ranked failure points, a provenance ledger for deliberation, a drafted repository report, and an evidence-linked refactor plan.

GitHub URL | local path
    → taxonomy + clade allocation
    → genetics (lineage, gene flow) + ecology (stages, Lehman proxies)
    → metrics + debt + weaknesses
    → provenance ledger (claim → evidence → falsifier)
    → repo report + refactor plan
    → narrative (heuristic | HF Qwen | cloud)

Install

pip install codeevolve

From source:

git clone https://github.com/ehallford11714/codeevolve.git
cd codeevolve
python -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -e ".[dev]"
# optional local Qwen:
# pip install -e ".[hf]"

For agents (MCP)

Start here: AGENTS.md · details: docs/MCP.md · objective agent: docs/AGENT.md

pip install codeevolve
# or from source:
pip install -e .
# or from GitHub:
pip install "git+https://github.com/ehallford11714/codeevolve.git"
python -m codeevolve.mcp            # stdio MCP server (also: codeevolve-mcp)
Connect Path
Cursor MCP config .cursor/mcp.json
Agent skill .cursor/skills/codeevolve/SKILL.md
Tool loop analyze_repo → provenance_pack → provenance_expand_frame / provenance_path_pack
Improve loop evolve_toward_objective (or python -m codeevolve agent --objective …)

Agents should deliberate from frames (claim → evidence → falsifier), not invent history.

# Native coding agent: propose improvements scored by CodeEvolve
python -m codeevolve --repo . agent --objective reduce_debt --max-rounds 2
python -m codeevolve --repo . agent --objective follow_refactor --apply --verify-cmd "pytest -q"

Quick start

# Default: SLM-guided taxonomy (tier=slm)
python -m codeevolve --repo path\to\repo analyze --out report.json --report-out repo_report.md --refactor-out refactor_plan.md

# Swap up for sharper evolutionary studies
python -m codeevolve --model-tier large --repo path\to\repo analyze
python -m codeevolve tiers

# GitHub URL or owner/repo (cloned under ~/.codeevolve/repos)
python -m codeevolve --repo https://github.com/org/repo analyze --max-commits 300

python -m codeevolve --repo org/repo taxonomy
python -m codeevolve --repo org/repo fatigue
python -m codeevolve --repo org/repo risk
python -m codeevolve --repo org/repo report --md-out repo_report.md
python -m codeevolve --repo org/repo refactor --md-out refactor_plan.md
python -m codeevolve hardware
from codeevolve import CodeEvolve

report = CodeEvolve("https://github.com/org/repo").analyze()
print(report.ecology.global_stage, report.debt.score)
print(report.risk.failure_points[0].title)
print(report.refactor_plan.markdown)

LLM backends (optional)

python -m codeevolve --repo . analyze --llm auto
# or: --llm hf-qwen | openai | anthropic | heuristic

$env:CODEEVOLVE_LLM_API_KEY = "..."          # OpenAI-compatible
$env:OPENAI_API_KEY = "..."
$env:ANTHROPIC_API_KEY = "..."
$env:CODEEVOLVE_HF_MODEL = "Qwen/Qwen2.5-0.5B-Instruct"
$env:CODEEVOLVE_SKIP_HF = "1"                # force no local download

hardware / --llm auto picks local Qwen vs cloud vs heuristic from RAM/VRAM/disk (iQueue-style ladder).

What it tracks

Signal Meaning
Taxonomy / clades Keyword type hierarchy + co-change clusters; every delta allocated to a clade
Build hierarchy Deep nested “what was built” tree + ecological trend narratives
Genetics File lineage, fitness, gene flow, HGT suspects
Ecology Global + per-clade stages; Lehman law proxies
Revert / stability / deps / momentum Core change-rate metrics
Debt Deprecations, TODOs, historical architecture smells
Weaknesses Ranked failure points (hotspot blast, reverts, bus factor, test gap, …)
Repo report Drafted markdown brief of evolutionary state
Refactor plan Stabilize → contain → pay down → evolve (evidence-linked)
Provenance Ledger + dynamics trajectory (basins, impulses, selection, inter-report diffs)

Docs

0.25 — Context graph as cognitive control plane: attention_rank seeds coalition/sense, subagents sense-before-reflect, live-graph failure reflections, coalition in reflect + LLM propose. 0.24 — Context graph families (taxon/context/knowledge/decision/pivot/flow), coding pivots with live write-back, policy/why-edges, wavefront traversal search, precedent and delta surfacing. 0.23 — Phylogeny divisions are semantic taxa: keyword type_path (domain/family/kind/specialty) plus niche, with Fitch at each ontology depth. 0.22 — 3D phylogeny builder with commit intent and analysis inspector, plus 2D clade / Fitch parsimony / gene-flow gallery (SVG/HTML/Newick, viz_phylogeny MCP). 0.21 — PR review pack, frame-seeded steps, session delta memory, AST/CST symbol fence, blast-radius preview, coverage-gated tests, agent eval scored on objective delta (included in evaluate --suite all). 0.20 — patch engine, worktree, tool-calling, budgets/HITL. 0.19 — cognitive stack. 0.18 — objective agent + multi-provider LLMs.

python -m codeevolve --repo . provenance --pack --frame frame:basin
python -m codeevolve provenance --schema-out schemas
python -m codeevolve evaluate --suite dynamics
python examples/demo_dynamics.py
python -m codeevolve --repo . analyze --previous report.prev.json --out report.json
# Diff + dashboard + phylogeny viz + PR comment + CI gate
python -m codeevolve --repo owner/repo analyze --out report.json --previous report.prev.json --dashboard-out dash.html --viz-out viz.html
python -m codeevolve viz --report report.json --out viz.html
python -m codeevolve viz --report report.json --out builder.html --kind 3d
python -m codeevolve viz --report report.json --out vizdir/
python -m codeevolve --repo . coupling
python -m codeevolve --repo . clones
python -m codeevolve --repo . dependencies
python -m codeevolve --repo . offboarding
python -m codeevolve --repo . word2vec
python -m codeevolve --repo . semantic-taxonomy
# pip install -e ".[semantic]"  # MiniLM + gensim + chromadb
python -m codeevolve hardware --ensure-embed
python -m codeevolve evaluate --suite synthetic --md-out eval.md
python -m codeevolve evaluate --suite public --md-out public.md   # clones OSS tags
python -m codeevolve comment --report report.json --out pr.md
python -m codeevolve ci --report report.json --previous report.prev.json

License

MIT

Metadata

Release files for codeevolve 0.25.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for codeevolve 0.25.0
File Size Uploaded Provenance Actions
codeevolve-0.25.0.tar.gz 327.8 kB Without provenance Details for codeevolve-0.25.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for codeevolve 0.25.0
File Interpreter ABI Platform Actions
codeevolve-0.25.0-py3-none-any.whl Python 3 none any Details for codeevolve-0.25.0-py3-none-any.whl

Total release size: 688.7 kB

Release files / codeevolve-0.25.0.tar.gz

Download URL codeevolve-0.25.0.tar.gz
Size 327.8 kB
Tags Source
SHA-256 checksum
How to use checksums
59858c8a254d67d8759c6667d44d6ac4e1c2313735731cb40992e1a8fda551fb
BLAKE2b-256 checksum
How to use checksums
493830d9d085b076d6263e7ca87224a015ec7a82c553f163a31f836cf91e3841
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.3

Release files / codeevolve-0.25.0-py3-none-any.whl

Download URL codeevolve-0.25.0-py3-none-any.whl
Size 360.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e6159890ddd46ad7b3eb189454db2e388d1c73a56704d0e4dac0f52ec7b597fa
BLAKE2b-256 checksum
How to use checksums
3803c3bb165e310323072d4a86390f7811599fd3dbf23f8d398d9ba5dd0e01fa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.3

Security for codeevolve 0.25.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page