
Coderabbit renamed its Agent add-on CodeRabbit Engineer and hid the price
By Rob Litterst, Co-founder, PricingSaaS
Published
Coderabbit renamed its Agent add-on to CodeRabbit Engineer and removed its price from the card.
Coderabbit’s pricing page · Change detected
What changed
Per Coderabbit's pricing page, as detected by Pulse on Oct 10, 2026, the on-demand cards were rebuilt: Security Scan became Deep Scan, and the Agent card -- previously priced at $0.40 per agent minute -- became CodeRabbit Engineer with no price shown on the card; per that same Coderabbit pricing page on Oct 10, 2026, the $0.40-per-minute rate now appears only in the FAQ. The same Oct 10, 2026 page added Slop detection, which flags low-quality AI-generated PRs, to the feature lists of all four plans: Essentials, Team, Advanced and Enterprise. Per Coderabbit's pricing page on Oct 10, 2026, Enterprise Controls also gained a new 'Custom finishing recipes per repository' row, set at 10 for Team and 20 for both Advanced and Enterprise, with Essentials left out.
Why it matters
For a buyer, the price did not move -- its visibility did. Taking the $0.40-per-minute figure off the CodeRabbit Engineer card, as Coderabbit did on its pricing page on Oct 10, 2026, and leaving it only in the FAQ makes the add-on read as included or flat-rate at a glance, which raises the odds a team underestimates usage cost until the invoice arrives. Putting Slop detection on every tier, including Essentials, removes it as a reason to upgrade, so Coderabbit is pushing tier differentiation toward configurability (the new Custom finishing recipes row) rather than toward which AI-review features you get. Teams evaluating CodeRabbit for budget reasons should price the Engineer add-on from the FAQ rate before assuming the card's silence means it is free. Watch whether other review tools follow by hiding per-unit usage rates on their own cards while keeping headline plan prices unchanged.
In context
Pulse has tracked 16 real pricing-page changes to Coderabbit since May 18, 2026, and this is its second move to the on-demand add-on area in 19 days: on Sep 21, 2026, it had already folded usage-based reviews into a new On demand products section. Pulling the $0.40-per-minute rate off the Engineer card, per Coderabbit's pricing page as of Oct 10, 2026, and leaving it shown only in the FAQ, reads as an effort to make the add-on look included rather than metered, though usage pricing itself has not changed. Rolling Slop detection into Essentials as well as the paid tiers, while reserving the new Custom finishing recipes row for Team, Advanced and Enterprise, keeps the free-to-paid gap defined by configurability rather than by AI-review features. fal added Flux 3 image editing to its rate card on Oct 9, 2026, a reminder that feature additions are common across the companies Pulse tracks right now. Watch whether Coderabbit's FAQ-only rate resurfaces on the add-on card as usage climbs, or whether it folds the charge into a flat fee instead.
Common questions
How do we estimate what CodeRabbit Engineer will actually cost us?
Pull your last invoice's charges for the old Agent add-on rather than guessing from the blank card -- the per-minute rate itself hasn't changed, only its visibility has, so past usage is a better forecast than the card's silence.
Is this a one-off tidy-up or part of a pattern?
It's worth checking Coderabbit's pricing page again before your next renewal: its on-demand section has now changed in back-to-back updates, and nothing here rules out another rework before Enterprise contracts come up for review.
Which plans get the new Custom finishing recipes row?
If your team is on Essentials, that's the one tier with no per-repository finishing customization at all -- worth weighing before deciding whether a move to Team unlocks enough value to justify the price gap.
Sources
- Pulse: Coderabbit pricing changes, Oct 10, 2026pricingsaas.com/companies/coderabbit/diffs/2026D283
- Coderabbit pricing pagecoderabbit.ai/pricing