Understanding reviews
Plans & limits
The two allowance pools, what is free, and what happens at the cap.
What is metered
- A review run - One full review of one prompt. The Prompt Editor and the MCP draw from the same monthly pool, so it does not matter which tool you run it from.
- A PR review - One Git Action review of one pull request, however many prompt files it touches. It has its own, larger pool.
- Check changes - The incremental re-check after you edit a prompt Hosho has already reviewed, in the editor or the MCP. Free on every plan - iterating on a prompt is the work, and we do not charge for the work.
The two pools are independent: PR reviews have their own, larger allowance, so a busy release week in CI never eats the runs you wanted for the editor. Both belong to your organisation - all of its workspaces, keys and people draw from one pool. Allowances reset on the 1st of each month, UTC, and unused runs do not roll over.
The plans
| Plan | Price | Includes |
|---|---|---|
| Free | $0 | 5 review runs a month · 5 PR reviews a month |
| Pro | $25 /month | 25 review runs a month · 25 PR reviews a month |
| Team | $100 /month | 100 review runs a month · 100 PR reviews a month |
| Enterprise | Custom | Unlimited review runs · Unlimited PR reviews |
Full tier details and purchase live on the plans page.
What happens at the cap
Hitting the PR cap never fails your check.
- On a PR - the comment gains a banner naming the files not reviewed this run, the check stays green, and those files are reviewed automatically on the next push once the allowance resets or the plan is upgraded. A billing condition never blocks a merge.
- In the editor and the MCP - full reviews pause until the reset or an upgrade, and nothing you already ran is taken away. Check changes keeps working - it is free on every plan.
A cap is not a rate limit
Separately from the monthly allowance there is per-key traffic shaping. If you see a retry-shortly error, that is the rate limiter asking your CI to slow down for a moment - not your allowance. A cap message always says so explicitly, names your plan, and links the upgrade path.
Size and time, in practice
- A full review routinely takes several minutes; on a PR, expect 60-90 seconds per file. MCP clients need their per-server timeout raised - the install snippets set it for you.
- A PR comment that outgrows GitHub's size limit drops whole file sections from the tail, with a note - the full report is always in the Job Summary.
- Prompts reviewed with bundled context (skills, siblings, references) have generous but real bundle caps; a review tells you when something was left out.