Install ProPR, or skip the server
Run npm install -g propr-cli and propr setup on a Linux Docker host (quickstart). ProPR Hosted runs a dedicated instance for you when you would rather not run one.
ProPR: the agent-neutral alternative to Kiro after Amazon Q
AWS is retiring Amazon Q Developer for Kiro, which runs hosted agents from an IDE, CLI, the web, and a GitHub app. ProPR runs the same GitHub loop on your own server with any of five agents.
vs
Amazon Q and Kiro
Hosted Kiro, self-hosted ProPR
Kiro is the AWS-hosted agent with its own models and credit tiers. ProPR is the delivery layer that routes work to Claude Code, Codex, Antigravity CLI, Mistral Vibe, OpenCode, or direct provider access on your own server.
Kiro path
kiro label or /kiro → hosted sandbox → pull request/kiro all and /kiro fix push updates for reviewer comments.ProPR pathPlan → isolated workspace → GitHub PR → follow-up commitThe same GitHub loop, any of five agents, on your server.
Switch from Kiro to ProPR.
What you keep: your GitHub repositories and review process, and any Claude or ChatGPT plan, which ProPR runs through Claude Code or Codex.
The same ideas, ProPR's names
| Kiro | ProPR |
|---|---|
kiro label or /kiro | AI label on the issue |
| Specs: requirements, design, tasks | Plan, approved before code runs |
| Hosted sandbox | Isolated workspace on your server |
/kiro all, /kiro fix | Any plain PR comment; /fix for review findings |
/q review | /review |
| Kiro-hosted models on credit tiers | Your provider plans or API keys, no markup |
From zero to the first pull request
Add the same repository and sign in your agent
Open the web UI, sign in with GitHub, and add the repository. Sign in Claude Code, Codex, or Antigravity CLI with the plan you already hold.
Start the first task and approve the plan
Add the AI label to the issue you would have labelled kiro, then approve the plan.
Review the pull request in GitHub
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 CI failure playbook turns a red check into the next commit.
What stays with Kiro: Kiro runs without a server and reaches into AWS surfaces; ProPR runs on your Linux Docker host or a Hosted plan and speaks only to GitHub.
Amazon Q Developer brought issue-to-PR development and automatic code review into GitHub through the /q dev and /q review commands. AWS stopped new Q Developer sign-ups on 15 May 2026, stops new installs of the GitHub app on 18 November 2026, and points existing users to Kiro. The 30 April 2026 announcement set end of support for the IDE plugins and paid subscriptions at 30 April 2027, and the Amazon Q Developer for GitHub app ends on 30 January 2027. Q Developer inside the AWS Management Console and the Slack and Teams chat apps continue.
Kiro picks up the GitHub loop. Add the kiro label or comment /kiro on an issue and the Kiro Agent GitHub app clones the repository into a hosted sandbox, implements the change, and opens the pull request. /kiro all and /kiro fix push updates for reviewer comments, and Kiro addresses failing GitHub Action checks on its own. Specs break a task into requirements, design, and tasks before implementation. The models are hosted by Kiro, with Claude, OpenAI GPT, and open-weight options on credit tiers from free to $200 per month.
ProPR runs the same GitHub PR loop, provider-neutral and self-hosted. The change starts as a reviewed plan, runs in isolation on your host, opens a pull request, and improves from plain comments, with Claude Code, Codex, Antigravity CLI, Mistral Vibe, OpenCode, or direct API access doing the work on your own credentials. ProPR never marks up tokens.
Kiro fits best when...
- You are migrating off Amazon Q Developer and want the vendor-provided path: Kiro IDE for the plugins, Kiro CLI for the Q CLI, Kiro GitHub app for the Q GitHub app.
- Spec-driven development with Kiro-hosted models covers the need.
- A hosted sandbox and AWS billing are acceptable for every repository.
ProPR fits best when...
- You choose the agent and model per task, across providers, on subscriptions or keys you already hold.
- Plans, task records, logs, and cost visibility live in your own deployment.
- Plain GitHub comments become follow-up commits from any of the five agents on the same branch.
A hosted AWS agent versus provider-neutral PR delivery.
| Question | Kiro | ProPR |
|---|---|---|
| Status of Amazon Q Developer | Replaces it; Q IDE plugins end 30 April 2027 | Unaffected |
| GitHub issue becomes a pull request | Yes, kiro label or /kiro | Yes |
| Plan before implementation | Specs: requirements, design, tasks | Reviewed plan on every task |
| GitHub comments drive follow-up commits | Yes, /kiro all or /kiro fix, task creator only | Any plain comment, any agent |
| Choose Claude Code, Codex, Antigravity CLI, Mistral Vibe, OpenCode, or direct APIs | No, Kiro-hosted models only | Yes |
| Self-hosted execution, task records, and logs | No, hosted sandbox | Yes |
| Platform pricing beyond model costs | Credit tiers, $0–$200/mo per user | None, Apache 2.0 |
Verified November 2026: AWS end-of-support announcement, Amazon Q Developer for GitHub docs, kiro.dev/docs/web/github, kiro.dev/docs/specs, kiro.dev/docs/models, kiro.dev/pricing.