fix(web): open diff files from nested projects

[gbarros-dev]

Projects nested inside a Git repository receive repository-relative diff paths, but the file viewer reads paths from the project root. Clicking frontend/Dockerfile from a frontend project therefore tries to open frontend/frontend/Dockerfile.

Diff paths are now translated to the active workspace before opening. Paths outside the configured project stay closed, Windows separators are handled, and separate worktrees retain their repository-relative paths.

Fixes #6166

Tests:

• pnpm exec vp test run apps/web/src/diffFileActions.test.ts
• pnpm --filter @t3tools/web typecheck

Generated with GPT-5.6 Sol in T3 Code's Codex harness, with a focused GPT-5.6 Terra review through Pi.

---

Note

Low Risk
Localized diff-click handling with explicit rejection of out-of-project paths; no auth or data-layer changes.

Overview
Fixes diff file clicks for projects nested inside a Git repo: Git reports paths like frontend/Dockerfile, but the in-app file viewer expects paths relative to the project root, which previously produced doubled paths (e.g. frontend/frontend/Dockerfile).

resolveDiffPathForWorkspace strips the workspace’s prefix under the repository root before opening in the right panel or external editor. Paths that don’t belong to the active project are ignored; separate worktrees keep full repo-relative paths when workspace isn’t under the main repo root. Windows separators and case-insensitive matching are handled.

DiffPanel supplies repositoryRoot from the project (skipped when the thread uses a worktree).

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

Note

Fix diff file opening for nested projects in DiffPanel

• Adds resolveDiffPathForWorkspace in diffFileActions.ts to validate and normalize diff file paths against the workspace root, supporting Windows paths and mixed separators.
• openDiffFilePrimaryAction now early-returns when a diff path is invalid, absolute, or outside the current workspace; valid paths use a workspace-relative path when opening the right panel or external editor.
• DiffPanel derives a repositoryRoot from the active project and forwards it to openDiffFilePrimaryAction so repository-relative paths can be resolved correctly for nested projects.
• Behavioral Change: diff files whose paths do not resolve within the active workspace now silently no-op instead of attempting to open.

^{Macroscope summarized e8f074a.}

[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: 1babe1ff-4c78-4850-9e23-b4f84c5bf890

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Approved e8f074a

This bug fix adds path resolution logic for opening diff files from nested projects. The changes are self-contained, defensively coded (rejecting invalid paths and path traversal attempts), and comprehensively tested covering edge cases like Windows paths and filesystem roots.

^{You can customize Macroscope's approvability policy. Learn more.}