ProPR and Aider: a PR path for terminal pair programming

Aider is an Apache 2.0 command-line tool that pairs you with a model inside a local Git repository. ProPR adds the plan, the isolated run, the pull request, and the follow-up commits Aider never produces.

ProPR
vs
Aider

Local commits, then a pull request

Aider commits every edit to your own checkout. ProPR takes it from there: a reviewed plan, a branch, a pull request, and the review answers.

Aider pathTerminal chat → architect and editor models → commit to your checkoutNo hosted mode, no GitHub App, no pull request step.
ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitThe plan, the branch, the pull request, and the review answers Aider leaves to you.

Aider is close to the developer, and like ProPR it is open source under Apache 2.0. It runs entirely on your machine, commits each edit to your local checkout, and works with OpenAI, Anthropic, Gemini, Bedrock, Ollama, OpenRouter, and any OpenAI-compatible endpoint on your own key. Its architect mode splits a task between a reasoning model that proposes the change and an editor model that applies it.

Aider has no hosted mode, no GitHub App, and no pull request step: after a useful local session, you still scope the work, explain it, clean the branch, open the PR, answer review feedback, and leave history for the next person. ProPR does that packaging: a reviewed plan, an isolated run, a pull request, follow-up commits from GitHub comments, and a record of the agent, duration, tokens, and cost of every run.

A finished task: Implement PR #318 on northwind/orders-api, its run on Claude Opus 5.5 for 19 minutes, 2.4M tokens in and an estimated $1.42
A finished task's record: the pull request it opened, the agent, duration, tokens, and estimated cost, kept for the next person.

Aider versus ProPR.

QuestionAiderProPR
Live local coding in a terminalYesNo, unattended runs
Open sourceApache 2.0Apache 2.0
Runs on your own provider keysYes, many providersYes, subscriptions or API keys
Opens the pull requestNo, local commits onlyYes
GitHub comments become commitsNoAny plain comment
Shared task record and logsNoYes

Choose Aider for architect-mode edits in your own checkout.

Aider keeps you in the terminal while you investigate a bug, try local edits, or learn a code path one prompt at a time, with a reasoning model proposing the change, an editor model applying it, and every edit committed locally.

Verified November 2026: github.com/Aider-AI/aider, aider.chat/docs/llms, aider.chat/docs/usage/modes.

Use Aider with ProPR.

Stays in Aider

  • Architect-mode sessions in your own checkout, with every edit committed locally.
  • Investigating a bug or learning a code path one prompt at a time.
  • Your provider keys; Aider keeps using them directly.

Moves to ProPR

  • The branch, the pull request, and the review answers Aider leaves to you.
  • Scoped tasks that run unattended in an isolated workspace on your server.
  • Follow-up commits from plain GitHub comments, with the run's agent, duration, tokens, and cost on record.

Wire them together

Install ProPR beside Aider

Run propr setup on a Linux Docker host (quickstart) or pick a ProPR Hosted plan, add the repository, and sign in Claude Code, Codex, or another supported agent.

Hand over the change once it has a shape

When an Aider session shows you what the fix is, write it as a GitHub issue and add the AI label. ProPR plans it, runs the agent in isolation, and opens the pull request.

Steer from the pull request

Review the diff the way you review any pull request. A plain comment on it becomes the next commit on the same branch; /review posts scored findings and /fix applies them. The follow-up playbook walks one comment to its commit.