Repoprep

Convert any GitHub repo or local project into an AI-ready context file in one click.

Stop pasting files into Claude, ChatGPT, or Gemini one by one. repoprep turns an entire GitHub or GitLab repository — public or private — or any local project folder, into a single, clean, AI-ready context file. Browse to any repo, click the icon, select the files you need, and copy a structured context straight into your AI tool of choice. ## WHAT'S NEW IN 1.3.0 - **Full transparency on what got skipped.** A new disclosure panel shows exactly which files were left out and why — flagged as sensitive (keys, credentials, tokens), binary/media, or inside an ignored directory — so you're never left guessing what didn't make it into your context. - **Safer secret detection.** Credentials sitting in folders like `.ssh/`, `.aws/`, or `.kube/` are now correctly flagged as sensitive, even when the filename itself doesn't scream "secret" (think `.aws/credentials` or `.kube/config`). - **Interactive file tree.** Browse your repo or local folder as a real collapsible tree, with folder-level select/deselect, instead of one long flat list. - **Fixed drag-and-drop.** Dropping a folder now actually recurses into its contents (it silently didn't before) — while still skipping `node_modules` and other noise before descending, so it stays fast. - **Clearer downloads.** Exported files are now named `repoprep_<project-name>.txt`, sanitized so odd characters in a repo or folder name can't produce a broken filename. - **Pro sync improvements.** License verification now checks in with your account automatically, so your Pro status stays in sync across devices without manual re-verification. ## HOW IT WORKS - **On GitHub or GitLab:** click the repoprep icon on any repo page. It opens in its own window — separate from the toolbar popup — so you can switch to another app to grab a license key or copy code, and it stays right where you left it. It reads the file tree, lets you filter and select files, and builds your context file instantly. Add a personal access token in settings to unlock private repos too. - **Local files:** drop in a folder or ZIP — works exactly the same way, entirely offline. - **Automatically strips secrets and noise:** `.env` files, API keys, SSH keys, cloud credentials, `node_modules`, lock files, build outputs, binaries, and other clutter that just wastes context space — so you don't accidentally paste a credential into an AI chat. ## 100% LOCAL, ALWAYS Local files are processed entirely in your browser — nothing is uploaded anywhere. GitHub/GitLab repos are fetched directly from their own public APIs, the same way your browser already talks to those sites. If you add a personal access token for private repos, it's stored only on your device and never leaves it. ## FREE PLAN 50 files, 4 MB per session — plenty for components, bug reports, or quick questions. Private repo support included. ## PRO — $6 ONE-TIME - 250 files, 20 MB per session - Token counter — see exactly how large your context is before pasting - Model compatibility check — know if your context fits Claude, GPT, Gemini, and more - Syncs your Pro status across all your devices (personal access tokens stay local to each device, by design) No subscription. Pay once, use forever. ## OPEN SOURCE The core parsing and context-building engine is open source: github.com/Kishoren1/repoprep-app ## WEBSITE [repoprep.com](https://www.repoprep.com) — the free web app version, for whenever you want to process a local project without installing anything, or need repoprep on a browser other than Chrome. ## USE IT FROM YOUR AGENT, TOO Prefer working from an AI coding agent instead of the browser? [repoprep-mcp](https://www.npmjs.com/package/repoprep-mcp) brings the same repo-to-context engine to any MCP-compatible tool (Claude Code, Cursor, and others), so your agent can pull a clean, secret-stripped context straight from a repo without leaving the terminal. *(Double-check that description against the actual package README before publishing — I couldn't fetch npmjs.com directly to verify the exact feature set, so this is a reasonable inference from the name and your existing ecosystem, not a confirmed description.)* Questions or feedback? repoprepcare@gmail.com