feat(web): filter PR comments by bots and resolved threads

[juliusmarminge]

The Summary tab put bot comments and resolved or dismissed comments in two collapsed groups at the bottom of the conversation. Reading them meant opening a group and paging inside it, and the choice was forgotten on every pull request.

The groups are gone. A Filter menu next to the sort toggle has two checkboxes, "Bot comments" and "Resolved or dismissed". Both start hidden. When shown, those comments join the main list in time order and share its paging. Resolved and dismissed comments still render as collapsed cards. The trigger reads "N hidden" while anything is filtered out, and the section says so when the filter hides every comment. The choice is saved in local storage, so it carries across pull requests and reloads.

Before	After (default)	After (resolved shown)

Captured on #17101 in a dev server seeded from real data; the before is the same page served from main.

Verification:

• vp test run src/components/pullRequest/PullRequestSummaryTab.test.tsx covers the default hiding, the hidden count, bots joining the paged list, resolved cards appearing, and the choice surviving a remount on another pull request.
• tsc --noEmit for apps/web, lint on the changed files.
• In the browser: toggled both filters on feat: manage skills and MCP servers in Settings → Tools #17101, then opened feat(server): /mcp narrows a client's modes from T3-Mode-Limit #16653 and confirmed the stored choice applied there.

Scope: web only. Mobile has no pull request conversation list, and the Timeline tab never grouped bot comments.

Opus 5.5 in Claude Code, via T3 Code.

🤖 Generated with Claude Code

---

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The Summary tab now hides bot and resolved comments by default, replaces their prior grouped presentation, and persists each user's filter choice across pull requests. Because this changes the product's default behavior and the production conversation experience, it warrants human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	5.0 KiB	5.0 KiB	0 B (0.0%)	6.8 KiB	✅
Codex	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Codex	Live turn WebSocket wire	1.2 KiB	1.2 KiB	0 B (0.0%)	2.0 KiB	✅
Codex	Live turn WebSocket decoded	20.9 KiB	20.9 KiB	0 B (0.0%)	29.3 KiB	✅
Codex	Live turn messages	2	2	0 (0.0%)	8	✅
Claude	Total thread wire	5.0 KiB	5.0 KiB	+24 B (+0.5%)	6.8 KiB	✅
Claude	Thread snapshot wire	3.8 KiB	3.8 KiB	0 B (0.0%)	4.9 KiB	✅
Claude	Live turn WebSocket wire	1.2 KiB	1.2 KiB	+24 B (+2.0%)	2.0 KiB	✅
Claude	Live turn WebSocket decoded	21.2 KiB	21.2 KiB	+41 B (+0.2%)	29.3 KiB	✅
Claude	Live turn messages	1	2	+1 (+100.0%)	8	✅

Baseline: 51347ac · PR result: eb3181a · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Team
• Run ID: ce612e60-c193-40f0-b093-281ee7569945

---

📥 Commits

Reviewing files that changed from the base of the PR and between 51347ac and eb3181a.

---

📒 Files selected for processing (2)

• apps/web/src/components/pullRequest/PullRequestSummaryTab.test.tsx
• apps/web/src/components/pullRequest/PullRequestSummaryTab.tsx

---

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.

---

---

📝 Walkthrough

Walkthrough

The pull request summary adds browser-persisted filters for bot and resolved or dismissed comments. It applies filters before the recent-comment window and displays bot, resolved, and dismissed comments in the main list.

Changes

Comment filters

Layer / File(s)	Summary
Persisted filter and comment selection apps/web/src/components/pullRequest/PullRequestSummaryTab.tsx	The component adds schema-validated filter options for bot and resolved or dismissed comments. It applies the selected filters before the recent-comment window and counts hidden comments.
Unified comment list and filter controls apps/web/src/components/pullRequest/PullRequestSummaryTab.tsx, apps/web/src/components/pullRequest/PullRequestSummaryTab.test.tsx	Bot comments now appear in the main comment list. Resolved and dismissed comments render as collapsed entries. The filter menu persists selections, shows the hidden-comment count, and has a specific empty state when filters hide all comments. Tests cover filter visibility and persistence after rendering another pull request.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant PullRequestSummaryTab
  participant localStorage
  PullRequestSummaryTab->>localStorage: Read saved filter options
  localStorage-->>PullRequestSummaryTab: Return saved options
  PullRequestSummaryTab->>User: Render comments using filter options
  User->>PullRequestSummaryTab: Change a comment filter
  PullRequestSummaryTab->>localStorage: Save the selected option
  PullRequestSummaryTab->>User: Render the filtered comment list

Loading

Suggested reviewers: maria-rcks

---

Merge Risk: ⚪ Minimal · up to eb318

The comment filters and collapsed cards have no identified merge-blocking issue. Merge after normal checks.

Pre-merge checks | 3 | 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check		The description clearly covers the problem, implementation, scope, verification steps, and UI screenshots. However, it does not provide the required triaged issue or discussion link with explicit main…	Add the relevant triaged issue or approval discussion link, including the maintainer approval comment. Organize the content under the required Problem, Change, Scope and approval, and Verification headings if needed.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main change: adding web pull request comment filters for bot and resolved threads.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

---

Full details: Description check

Explanation

The description clearly covers the problem, implementation, scope, verification steps, and UI screenshots. However, it does not provide the required triaged issue or discussion link with explicit maintainer approval.

---

---

• Fix all pre-merge checks with AI

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

---

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

---

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}