Repo Prompt helps AI models understand your codebase without wasting tokens on irrelevant code. Context Builder analyzes your project and selects the files and functions needed for your task, building dense context that fits in model limits. It works with your existing AI subscriptions (Claude MAX, ChatGPT Plus, Gemini) — no extra API costs. The MCP server turns Repo Prompt into a backend for Claude Code, Cursor, and Codex, giving them context analysis and discovery they can't do on their own.
Repo Prompt is like a superskeleton for creating better prompts within specific repos or projects.
It'll help you produce refined prompts so that when you hand off to your coding agent of choice, it'll get the done more efficiently and intentionally.
Repo Prompt looks awesome! Super excited about the potential for boosting developer productivity. How does it handle repos with a lot of historical branches?
This really bypass the try and refine loop for prompting. Any future support for local LLMs like Ollama?
Finally found one token saving for my cursor usage! I wonder if it only takes effect when the codebase is large enough?
Context assembly is quietly becoming infrastructure for AI coding. Tools that formalize it instead of hand-waving over repo search feel inevitable.
The Context Builder approach sounds practical for larger codebases—isolating relevant code before passing to reasoning models makes a lot of sense. I'm curious how it handles multilingual codebases where comments and variable names mix languages. Does the discovery agent factor in those language patterns when building context?
As a solo dev, context switching is the biggest pain. The mental overhead of manually curating files for Claude/Cursor is exhausting. 💀
The MCP integration specifically catches my eye (I'm currently experimenting with Claude Code workflows).
Quick question: Does the Context Builder handle large, unstructured "spaghetti" codebases well (to help refactor), or does it rely on existing clean architecture to find the right files?
Been using Repo Prompt daily for months. My workflow: GPT 5.2 High or Pro for planning, Opus 4.5 for implementation, then GPT 5.2 High for review. RepoPrompt keeps the same codebase context across all three, so each model builds on what the last one did.
The MCP integration with Claude Code is where it really clicks. Context building, implementation, review - all orchestrated end-to-end without manual handoffs.
Also want to highlight the Discord community. I'm active there, helping other users get set up, but I'm also learning a ton from how others use it. It's one of the most responsive dev communities I've been part of. @eric_provencher ships features faster than we can request them.
Graphical user interfaces are a magical way to interact with coding agents and Repo Prompt is a great example of the larger trend. Cool app and great team.
Congrats on the launch! I like how Repo Prompt focuses on context quality instead of just prompt wording, that’s usually where things break with coding agents.
I've been using Repo Prompt for about a year now and it's become my go-to tool for AI-assisted development.
My setup: I use Claude Code with Opus 4.5 as my main coding agent, but I also bring in GPT-5.2, especially during architecture and planning. Repo Prompt is the context layer that lets these models collaborate - I can curate exactly what each one sees and keep everything in sync. Instead of being stuck with one model's strengths, I get the best of both.
Just shipped my latest iOS app using this workflow exclusively.
Beyond the tool itself, the community is incredibly valuable. The Discord is active, Eric is constantly listening to feedback, and he ships high-quality updates at a speed I haven't seen from other dev tools. Can't recommend this enough.
If I'm already using Cursor or Claude Code with their built‑in repo search, what’s the concrete advantage of your Context Builder—fewer tokens, better accuracy, or faster completion—and by how much in typical tasks? What concrete advantages are there over Claude Code plan mode?
I've been using Repo Prompt for over a year now, and it's become an essential part of my daily development workflow.
As a founder building multiple B2B SaaS products, the ability to quickly assemble the right context for AI assistance has been a game-changer. Whether I'm working on backend Rails projects or integrating AI features, Repo Prompt saves me countless hours every week.
Here's a kept secret: pairing Repo Prompt with GPT-5 Pro (with full context) is incredibly powerful for architectural planning. The combination of precise context selection and advanced reasoning lets you think through complex system designs before writing a single line of code.
Highly recommended for any serious developer working with AI tools. This isn't just a productivity boost—it's become foundational to how I build software.
This is my workflow
I rarely comment here but this one's worth it.
I usually have 5-10 RepoPrompt windows open at any given time; one per project I'm context-switching between. It's become essential to how I work with AI coding tools.
The CLI/MCP Server is the killer feature for me. I've built autonomous multi-model review loops and context export workflows on top of it. The CLI lets agents coordinate reviews without me babysitting.
If you're building AI coding workflows, these features turn RepoPrompt from a great GUI into actual infrastructure you can automate against. Congrats on the launch Eric!
I’ve been actively using Repo Prompt for almost a year now, and it’s made it much easier to give LLMs the right context from a codebase without overloading them. Being able to select only the files that matter and generate a clean prompt saves time and tokens. It fits nicely into an ai assisted coding workflow and feels practical rather than gimmicky.
One of the best additions to my dev workflow. It is a great tool to rapidly improve the precision of your development with coding agents - saving you time and money. One of the best features of this app is the rapid development lifecycle and how close Eric is to the community of users, and he's both opinionated and openminded... Join the discord, and help guide the tool's development.
Repo Prompt lets you build precise context from your codebase so reasoning models actually understand what you’re working on.
I’ve been building it for over a year now. With MCP and CLI support, it fits into any agent workflow — Claude Code, Codex, Cursor, whatever you use.
The /rp-build command automates the whole loop: it researches your codebase, builds a plan, and hands off to your agent with the right context already loaded.
Repo Prompt is like a superskeleton for creating better prompts within specific repos or projects.
It'll help you produce refined prompts so that when you hand off to your coding agent of choice, it'll get the done more efficiently and intentionally.
Enjoy!