Troubleshooting
Your PR wasn't reviewed? Work through these common causes one by one — most issues are solved in under a minute.
No review was posted
Work through this checklist from the top — one of these is almost always the culprit:
- Did you comment
/pura reviewon the PR? Reviews are requested with that comment — they don't start on their own. The command must be the first line of the comment. - Is the PR a draft? Drafts are skipped — mark it ready for review, then comment
/pura reviewagain. - Is PURA installed on that repository?Check the GitHub App's repository access. You may have installed it on only certain repos, and this one might not be in the list.
- Is your account active? An expired trial with no paid plan pauses reviews until you pick a plan.
- Is the monthly review allowance used up?Each plan includes a set number of reviews per month. Once it's reached, PURA pauses reviews (with a note on the PR) until the 1st of next month — check usage in the dashboard or upgrade your plan.
Tip: You can manage repository access in your GitHub App settings at any time — just click Configure next to PURA in your GitHub Apps list.
Budget reached
If an agent has hit its daily, weekly, or monthly cap and no other provider in the chain fits, PURA pauses the review rather than overspending. You have a few options:
- Raise the cap on the agent in the dashboard.
- Add another provider to the agent so PURA has a fallback.
- Wait for the window to reset — daily caps reset overnight, weekly caps reset on Monday, and monthly caps reset on the 1st.
Check the analytics dashboard at app.pura.sh to see your current spend against each cap.
No agent matched the PR
A review only runs if there's an Active review agent, with a working provider key, whose scope allows that PR. A few things to check:
- Is the agent set to Active? Inactive agents are never used.
- Is the provider key on the agent valid? A missing or incorrect key means the agent can't run.
- If you've scoped agents by team, repo, author, or PR label, make sure at least one of them allows this particular PR. If none match, PURA has nowhere to route the review.
Easiest fix:Create or enable one agent with no scope restrictions — it acts as a catch-all for any PR that doesn't match a more specific agent.
It used a model I didn't expect
PURA routes each PR to a review agent based on the nature of the change and the guidance in your .pura/PURA.md, then reviews with that agent's first model. If the result surprises you, you have two levers:
- Adjust your
.pura/PURA.md— refine which kinds of changes should match which agent. - Set the model on the agent— PURA uses the first model in the provider's list, so put the model you want at the top, or route the PR to a different agent.
# PURA Review Routing
- Security, payments, or auth changes: use a top-tier model.
- General backend and product changes: a balanced model is fine.
- Docs, typos, and dependency bumps: a lean model is enough.Write plain English intent — PURA reads this file and uses it to decide how much firepower each PR deserves.
Still stuck?
If none of the steps above solved it, reach out and we'll help you get unstuck. [email protected]