Skip to content

feat(reviews): two-section Reviews tab#3053

Open
codebanditssss wants to merge 2 commits into
mainfrom
feat/reviews-tab-two-section
Open

feat(reviews): two-section Reviews tab#3053
codebanditssss wants to merge 2 commits into
mainfrom
feat/reviews-tab-two-section

Conversation

@codebanditssss

@codebanditssss codebanditssss commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

Splits the Reviews tab into two sections, per issue #2433:

  • Pull request reviews — GitHub review summaries (reviewer, verdict, body) from the session PR API. Only shows when a PR has review summaries.
  • AO code reviews — the existing reviewer pane, relabeled.

Both render one collapsible PR row per PR. Headers show PR identity + update context only; verdicts live in the expanded rows (no duplicate pills). Sits in the same bg-surface card as the Summary/Files tabs. All tokens, no hardcoded values.

Backend (persist/fetch/expose the review body) already merged via #3009 / #3049 / #3046.

image

@codebanditssss
codebanditssss marked this pull request as ready for review July 23, 2026 22:47
Comment thread frontend/src/renderer/components/SessionInspector.tsx
Split the Reviews tab into two sections:
- Pull request reviews: GitHub review summaries (reviewer, verdict,
  submitted body) from the session PR summary API.
- AO code reviews: the existing reviewer pane, relabeled.

Each section renders one collapsible PR row per attached PR. Headers show
PR identity and update context only; verdicts appear in the expanded rows,
so there are no duplicate verdict pills. Both sections sit in the same
bg-surface card the Summary and Files tabs use.

The Pull request reviews section only appears when a PR has review
summaries. All sizes/colors go through existing design tokens.
@codebanditssss
codebanditssss force-pushed the feat/reviews-tab-two-section branch from 5f0612f to 4320c22 Compare July 23, 2026 23:38

@Annieeeee11 Annieeeee11 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@neversettle17-101 neversettle17-101 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codebanditssss

  1. The codex alignment is wrong. Can we add the codex icon instead of the existing icon WDYT?
  2. Can we make sure that we don’t see open terminal till the review has been run?
  3. Wdyt should the AO code review be on top or the other? Because we would run the AO code reviews and then raise it for review to others
  4. Also do you think we should show the dot beside changes requested or approved?

Address review feedback on the two-section Reviews tab:
- show a codex mark for the AO reviewer harness instead of the generic
  shield (shield stays as the fallback for other harnesses)
- keep the Open terminal button out of the footer until a review has run
- link AO review rows to the posted GitHub review
- lead with AO code reviews, PR reviews below
- open up the AO panel spacing so rows are not stuck together
- seed mock PR review entries so the section renders in preview
@codebanditssss

Copy link
Copy Markdown
Collaborator Author

@codebanditssss

  1. The codex alignment is wrong. Can we add the codex icon instead of the existing icon WDYT?
  2. Can we make sure that we don’t see open terminal till the review has been run?
  3. Wdyt should the AO code review be on top or the other? Because we would run the AO code reviews and then raise it for review to others
  4. Also do you think we should show the dot beside changes requested or approved?

hey, pushed the fixes to the reviews PR:

  • swapped in a codex mark for the reviewer instead of the shield
  • open terminal only shows up once a review has actually run
  • added a "view review" link on the AO review rows that goes to the posted github review
  • moved AO code reviews on top, PR reviews below (went with your point about running AO first then raising it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants