Documentation

Coppice keeps one architecture in vibe-coded repos. You prompt in Cursor. Coppice writes the contract for the next session. This site is history, not a second IDE.

1. Install the extension

Open the Coppice repo. Sideload the VS Code extension in Cursor (Run and Debug → Launch Coppice Extension, or install the VSIX). Command palette:

• Coppice: Scan Workspace — free, local JS/TS + first-pass Python. No API key.
• Coppice: Agent Scan (Python and other languages) — asks for a Cursor API key in the editor. Never asked on this website.
• Coppice: Sign in to Coppice / Open Site

After a scan, Coppice writes COPPICE.md and .cursor/rules/coppice.mdc.

2. Authorize GitHub

On coppice.tekreign.com click Authorize GitHub. GitHub asks for identity and repo list. You return to /dashboard. Link the repo you already work in. Coppice does not clone GitHub as the product.

OAuth callback (production): https://coppice.tekreign.com/api/auth/github/login/callback/

3. Upload history (optional)

After GitHub login, open /connect (or the extension sign-in command). Mint a token. The extension stores it in Secret Storage and can POST scan results for a linked GitHub remote.

4. Advanced review

On the dashboard, open Explore more. That is not a second scanner. Coppice overlays findings you already uploaded from Cursor onto open GitHub pull requests and issues, and shows Local scan vs Agent Scan side by side. It does not clone the repo or invent CVEs.

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

Privacy · Terms · Third-party services · Support