Repository navigation
feat(vscode): show PR review comments inline in diffs - #13541
Merged
Merged
Conversation
Contributor
Code Review SummaryStatus: 1 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (6 files)
Fix these issues in Kilo Cloud Previous Review Summaries (4 snapshots, latest commit a729c8f)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit a729c8f)Status: 2 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (11 files)
Fix these issues in Kilo Cloud Previous review (commit 6971faf)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Files Reviewed (24 files)
Fix these issues in Kilo Cloud Previous review (commit 26f9d9c)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (8 files)
Fix these issues in Kilo Cloud Previous review (commit 3141112)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (78 files)
Reviewed by grok-4.6 · Input: 182.7K · Output: 13.8K · Cached: 389.5K Review guidance: REVIEW.md from base branch |
marius-kilocode
force-pushed
the
integrate-pr-comments-into-diff-ui
branch
from
September 4, 2026 12:05
26f9d9c to
687e41a
Compare
marius-kilocode
force-pushed
the
integrate-pr-comments-into-diff-ui
branch
from
September 4, 2026 13:20
6971faf to
7474ecc
Compare
marius-kilocode
enabled auto-merge
September 7, 2026 07:55
chrarnoldus
approved these changes
Sep 7, 2026
This was referenced Sep 8, 2026
This was referenced Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
GitHub PR review threads were separate from the code being reviewed. Moving a thread into chat also lost the direct path back to its location in the diff.
Why This Change Was Made
Keep remote review feedback next to the current code without replacing the existing local-comment workflow. Placement checks the file, side, hunk, and current content. Outdated or unmatched threads stay outside the current diff instead of appearing on a guessed line.
The implementation reuses the existing PR poller and diff virtualizers. Native PR polling state is isolated from the Changes panel, HTTPS validation is shared, and focused mapping, routing, lifecycle, and scroll tests replace the added render-bundle fixtures. No issue is linked because this is a standalone review-workflow enhancement.
User Impact
Evidence
Automated local checks passed: the complete extension unit suite (4,457 tests), extension build, lint, type checks, Knip, change-marker checks, and source-link extraction.
Isolated VS Code checks covered inline placement, large-file navigation, unified/split layouts, incoming-thread insertion and removal, same-line threads, an active local-comment draft, and live/closed-chat delivery. The visible code stayed within 0.21 CSS pixels in all 12 insertion/removal cases. The local editor retained its DOM node, focus, and draft text when another thread arrived on the same line.
In the controlled 8 MB / 100-thread fixture, the synchronous refresh handler fell from a 1,399.6 ms median to 2.5 ms over three warm samples at the same 792 × 811 viewport. This measures the handler, not asynchronous layout or paint. The isolated instance had no GitHub credentials, so authenticated polling was not part of those automated UI checks.
Resulting UI
PR thread in the diff:
Local review note in the same workflow:
Thread after sending it to chat:
Manual Test