RepoPrompt CE

A free, open-source native macOS app and agent orchestrator for context engineering.

RepoPrompt CE helps coding agents understand your codebase before they act. It assembles focused, reviewable context from files, CodeMaps, repository structure, and Git diffs, then hands that context to AI tools and CLI agents.

RepoPrompt CE also builds an agent harness around its bundled MCP server. Connect MCP-compatible clients and CLI agents to search repositories, inspect files, curate context, run agent sessions, and orchestrate work through a shared native macOS interface.

Get Started

Choose one of these setup paths. You do not need to open Xcode.

Install with Homebrew

For the signed and notarized public app, use the dedicated RepoPrompt CE Homebrew tap:

brew tap repoprompt/repoprompt-ce
brew install --cask repoprompt-ce

This installs /Applications/RepoPrompt CE.app from the repoprompt/homebrew-repoprompt-ce tap. The cask consumes the promoted public updater ZIP from repoprompt/repoprompt-ce-updates; it does not build from source. Source-build paths remain below for contributors and local development.

Build and launch locally

For development and quick evaluation, double-click Launch RepoPrompt CE.command in Finder.

The launcher requires Python 3, builds RepoPrompt CE through the coordinated developer daemon, opens the debug app, and keeps a small terminal window available for rebuild, status, and stop controls. It does not provide an uncoordinated no-Python fallback because lifecycle actions validate the exact debug executable path. It preserves an explicit compatible DEVELOPER_DIR, or selects an installed full Xcode for the launcher process without changing the system-wide xcode-select setting.

The debug launcher uses an available Apple Development: signing identity. If your Mac does not have one, run the same debug app from Terminal with explicit ad-hoc signing:

ALLOW_ADHOC_SIGNING=1 ./conductor app relaunch

Ad-hoc debug builds use in-memory secure storage, so saved API keys and secure permission changes do not persist across launches. For persistent debug Keychain storage, pass a stable Apple Development identity explicitly:

SIGN_IDENTITY="Apple Development: Your Name (TEAMID)" ./conductor app relaunch

For a stable locally signed app under /Applications, use the local production installer below. Its self-signed identity is separate from the debug launcher's Apple Development signing path.

Note: If you use the debug app to modify RepoPrompt CE itself, validation flows that launch the app or run live smoke checks may rebuild and relaunch it. Expect the debug app to restart while those checks run.

Key	Action
r	Rebuild and relaunch
s	Show app status
x	Stop the app
q	Close the launcher without stopping the app

Install a local production build