COPPICE

DOCUMENTATION

How Coppice works

Coppice is a gardener for vibe-coded repos. You keep prompting in Cursor. Coppice is the memory: one architecture, no duplicate work, no dead code, no known-bad package versions.

Install the extension

Install Coppice in Cursor or VS Code. Nothing else is required to start — the local scan is free and needs no API key.

Coppice: Scan WorkspaceFree. Auto on folder open and lockfile change.
Coppice: Agent ScanPython and other languages. Your Cursor plan.
Coppice: Set Cursor API KeySecret Storage. Never in the repo.
Coppice: Sign in to CoppiceOpens /connect in the browser.
Coppice: Fix assigned tasksClaims a site job; runs a local agent.
Coppice: Open SiteLanding, or workspace if signed in.

Install the extension opens Cursor. The listing is on Open VSX. If you do not have the editor, download Cursor first.

Create an account

Sign up with email and password, or continue with GitHub. Either way you land on the workspace. An account is only needed for GitHub-linked history — the gardener in the editor works without one.

Connect GitHub

Open Connections and connect GitHub onto the same account. GitHub is an integration, not a second login. Connecting lets Coppice list your repositories so you can link one. Linking does not clone anything, and Coppice never scans from the server.

Upload history

On Connections or /connect from the extension, mint a token. The extension stores it in Secret Storage and can POST scan results for a linked GitHub remote.

Explore board

Board turns findings into a list you can work through: Found, On my list, Being fixed, Waiting for you, Done. Create a request, hand a fix to Cursor, then read and accept it here. The website never runs the agent.

What Coppice will not do

  • Add a second UI kit or HTTP library when a winner already exists
  • Treat Next app/api as a feature folder
  • Ask for a Cursor API key on this site
  • Replace Django with FastAPI or NextAuth