Cached Reviews

Ever notice how sometimes reviews appear instantly? That’s caching at work.

The deal

We cache your reviews so you don’t have to wait every time you view the same code. But don’t worry—we automatically generate a fresh review whenever your code actually changes.

The magic: Instant results for unchanged code, fresh reviews when needed. All automatic.

How it works

We create a unique fingerprint (checksum) from your code changes + MR ID. Same code = same fingerprint = instant cached review.

Here’s what happens:

1. You request a review
2. We calculate a checksum of your code
3. Found a match? → Instant cached review
4. No match? → Generate new review and cache it

You don’t need to do anything. It just works.

When do we generate a fresh review?

Automatically, whenever:

• You push new commits — New code = new review
• You modify files — Any change triggers a new review
• First-time review — No cache exists yet

We compare checksums. Different checksum? Fresh review. Same checksum? Cached review.

Manually, when:

• You click the refresh button — Explicitly forces a new review, bypassing the cache

No manual work needed for automatic updates. You’re always looking at a review of your current code—unless you want a fresh perspective, then just hit refresh.

Why caching rocks

Speed: Cached reviews load in under a second instead of 5-15 seconds.

Consistency: Same code always gets the same review. No surprises.

Cost-effective: We don’t waste AI resources re-analyzing unchanged code.

Just works: Zero configuration. It’s automatic.

Situation	Time
First review	20-60 seconds
Viewing again	< 20 second ⚡
After code change	20-60 seconds

Your cache is private

• Personal — Only you see your cached reviews
• Persistent — Survives browser restarts and logins
• Automatic — No maintenance needed
• Secure — Stored safely in your account

When to use refresh

The cache is smart, but sometimes you want a fresh take:

• Different perspective — Get alternative suggestions
• After model updates — Try new AI capabilities
• Testing — Compare different approaches
• Something feels off — Force a fresh review

Hit the refresh button to bypass the cache completely.

Pro tip: Refresh gives you a completely new review from scratch. Great for getting a second opinion.

Examples

Scenario 1: Viewing the same code

1. Review your code → Takes 10 seconds
2. View it again → Instant (cached)
3. View it once more → Still instant

Scenario 2: Code changes

1. Review your code → Takes 10 seconds, gets cached
2. Push new commits → Checksum changes
3. View code → New review generated (10 seconds), cached
4. View again → Instant (new cache)

Scenario 3: Want a fresh take

1. Review your code → Cached
2. Hit refresh button → Bypass cache, new review
3. View again → Instant (updated cache)

Common questions

Will small changes trigger a new review?
Yes. Even tiny changes create a new checksum. That’s good—you always get feedback on your current code.

What if I just want a different opinion?
Hit the refresh button. It bypasses the cache and gives you a completely fresh review.

Do cached reviews expire?
Nope. They stick around until your code changes.

Is my cache shared with my team?
No. Your cache is yours. Everyone gets their own.

---

TL;DR: We cache reviews so you don’t wait for the same code twice. Code changes? We detect it automatically and generate a fresh review. Want a new perspective? Hit refresh. It’s all automatic.