feat(web): pull request files can be marked as viewed

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

[yordis]

• A review spread over an afternoon, or picked up on a second machine, starts again from the top every time, so large changes get read in the browser and only small ones stay here.
• The marks are the host's wherever the host keeps any, because a checkbox that looks like the one GitHub shows and quietly disagrees with it leaves a reviewer unsure which of the two knows what they have actually read.
• GitLab keeps its own viewed files in one browser's local storage, where nothing outside that browser can read or write them, so there is no shared record to be the host's. The marks are this environment's instead, and the surface says so rather than implying gitlab.com will show them.
• Declared per provider as where the marks live rather than whether they exist, so a host with nowhere to keep them hides the control instead of offering one that cannot keep its promise.
• Read apart from the patch, because viewed state moves on every press and a patch moves only when somebody pushes; sharing one read would mean either re-fetching a three-hundred-file diff per checkbox or showing a reader their own last press as stale.

---

Note

Medium Risk
Large cross-provider pull-request surface area (new persistence, caching, and Azure diff assembly); regressions could affect diff accuracy, viewed-state correctness, or Azure/GitHub API behavior under rate limits.

Overview
Adds per-file “viewed” tracking for pull requests end-to-end on the server: new filesViewed / setFilesViewed on PullRequestService, RPC auth for pullRequestsFilesViewed and pullRequestsSetFilesViewed, and provider support split by viewedFiles: "host" (GitHub GraphQL read/write) vs "environment" (SQLite marks plus host file revision lookups to detect pushes).

For environment-backed providers, migration 044 creates pull_request_files_viewed and PullRequestFilesViewedRepository stores cleared paths with a revision stamp; the service compares revisions (with caching, stale-while-revalidate, per-PR write ordering, and invalidation) so re-pushed files show as dismissed without re-fetching the whole diff on every checkbox.

Azure DevOps gains a real Code tab: capabilities.diff flips on, REST moves from az rest to az devops invoke, iteration changes are paged and turned into unified patches via the new diff dependency and azureDevOpsDiff.ts, plus getFileRevisions for viewed-state staleness. Bitbucket and GitLab add getFileRevisions (patch index lines / head blob GraphQL). Extensive unit tests cover paging limits, truncated diffs, and mark isolation across repos and PR numbers.

^{Reviewed by Cursor Bugbot for commit 6e9d61c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add ability to mark pull request files as viewed across providers

• Adds a "Viewed" checkbox to the PR code tab UI. Toggling a file collapses it and marks it viewed; changing the file's head revision shows a "Changed" indicator.
• GitHub viewed marks are stored on the host. GitLab, Bitbucket, and Azure DevOps marks are stored in the environment via a new SQLite table created by migration 044_PullRequestFilesViewed.
• The server fetches per-path head revisions to detect stale marks for environment-scoped providers.
• Risk: Azure DevOps PRs now use AzureDevOpsRepositoryLocation instead of threadsUrl. normalizeGitRemoteUrl now normalizes Azure DevOps SSH remotes to web spelling.

^{Macroscope summarized 6e9d61c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: db5e0854-7bcc-4529-902c-248e00159c3c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Warning

Your free Security trial is over. An organization admin can activate Security or dismiss this notice.

---

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

[macroscopeapp]

Reviewed the changed web UI: the new viewed-file checkbox in the diff header, the counter in the toolbar, and the fold/overlay logic modules. Two findings, both on changed lines in PullRequestCodeTab.tsx.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR introduces a substantial cross-provider viewed-file workflow with persistent state, new authenticated RPCs, provider integrations, and a newly enabled Azure DevOps diff path. It also changes authorization behavior and provider capability defaults, so the production blast radius warrants human review.

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

[macroscopeapp]

Reviewed the web UI changes (PullRequestCodeTab.tsx, pullRequestDiff.logic.ts, pullRequestFilesViewed.logic.ts, usePullRequestFilesViewed.ts) for shared-primitive use, Tailwind/CSS ownership and virtualizer behavior.

Both findings from the previous run are resolved: the Checkbox no longer carries a partial size-* override, and truncated is now threaded through the hook and surfaced in the meta line with the same Tooltip + TriangleAlertIcon treatment the withheld-diff caveat uses. Two remaining items below — one virtualizer regression risk, one accessible-name issue on the new control.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitHub

Screen.Recording.2026-08-20.at.6.15.29.PM.mov

[macroscopeapp]

One finding on the new viewed-files hook: the command-failure path surfaces an error toast for interrupt-only failures, which diverges from the repo's established useAtomCommand failure convention. Everything else in the web scope (Checkbox/Tooltip primitive use, the amber caveat icon matching the adjacent meta-line pattern, header portal render-prop stability via refs, explicit environmentId threading) looks consistent.

^{Posted via Macroscope — UI Consistency}

[yordis]

GitLab

Screen.Recording.2026-08-30.at.10.59.33.AM.mov

[yordis]

Azure DevOps

CleanShot.2026-08-30.at.18.22.41.mp4

[yordis]

Bitbucket

CleanShot.2026-08-30.at.18.30.34.mp4

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 75c0bb8. Configure here.}

[macroscopeapp]

One finding: the Azure-safe repository selector is applied to the right-panel branch but not to the sibling /pull-requests navigation in the same function, so an Azure DevOps link still opens a ref the server refuses.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One finding: the new "viewed" segment in the Code tab toolbar cannot shrink, which makes the already-tight meta strip overflow sooner in narrow panels. Everything else in scope looks consistent — the checkbox uses the shared Checkbox primitive with the same label-wrapping pattern as the other call sites, the render props stay identity-stable through refs with the marks folded into item.version, and usePullRequestFilesViewed resolves its environment from the explicit environmentId prop.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One convention finding: a known-tag recovery is expressed with Effect.catchIf instead of Effect.catchTags. Everything else in the new Effect service code (the PullRequestFilesViewed repository module's Context.Service/make/layer shape, namespace imports, dependency acquisition via yield*, and the new structured error mappings) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}