Coppice — Codebase Governance for Cursor

Vibe-coded repos drift: a second UI library, a second HTTP client, a second login, unused files, and known-bad package versions quietly accumulate. Agents do not remember the last session. Teams needed a contract that lives in the repo—not another cloud scanner and not a second implementation of the same feature.

We shipped Coppice as a Cursor gardener with a local-first scan model: • Architecture contract: one folder layout, one design pattern per job, one library per job • Duplicate features: extend the existing module; do not create a sibling • Orphan hygiene: unused files, exports, and packages get pruned instead of accumulating • Security: CVEs at the exact lockfile version, and secrets in the repo—fix by bumping the winner or removing an orphan, never by adding a second library • Local scan (free, no API key): full JS/TS coverage plus a first-pass Python read, on folder open and lockfile change • Agent Scan (on-demand, Cursor SDK): Python, Laravel, Go, Rails and others; billed to your Cursor plan; same finding JSON; never invents CVEs • Free plan: gardener in the editor, one linked GitHub repo and the latest scan • Premium: GitHub-linked history, billed on GitHub Marketplace—unlimited repos, explore board, ticket/PR overlay, local vs Agent Scan overlay • Scans never run in the cloud

Coppice keeps prompting honest without adding a second stack: • The next agent sees COPPICE.md and a Cursor rule before it writes • One architecture, no duplicate work, no dead code, no known-bad package versions • Free gardener in the editor; Premium GitHub history billed on GitHub, not a Coppice card • Agent Scan stays on your Cursor plan • Live product at coppice.tekreign.com