Investigate why copilot code review is slow

[benvillalobos]

Context

It takes about 20 seconds for code review comments to appear. Where's the bottleneck?

20251112-1825-19.9408451.mp4

[benvillalobos]

Could be:

• When we call the GH agent
• When we look up custom instructions
• Possibly other areas in our code

[benvillalobos]

Definitions:

CCR (Copilot Code Review)

• Same agent that runs on normal GH prs when you assign @copilot
• We send code to, owned by GH.
• They have a snippet API that looks at code
• The original CCR API takes diffs

Local Code Review

• Is not CCR. It's our own prompt built locally with context collected locally, executed against CAPI.

[benvillalobos]

"Usage by Entry Point" is data only coming from core.

• CCR's speed is not something we can control. Perhaps we improve perception of speed here (better progress indicator)

Harald's take on important things to tackle:

• Figure out the entry points
  • Diff against base branch
  • Review before commit (figure out with Lad)

[benvillalobos]

After discussions with @chrmarti , @digitarald , and Elle (PM on GH PR side), I've found that code review is in fact not slow.

The real issue is about how we display progress to the user. Cursor has a shiny button that shows progress within the button itself.