[Onkarj012]

Problem

When a file preview shows a home path such as ~/.claude/CLAUDE.md, the ~ crumb is plain text. Every other folder crumb in that trail can be clicked, so there is no way to jump to the home folder.

fileBreadcrumbs gave the first crumb the path ~. isHostPath only accepts ~/, so isListableHostFolder("~") is false and FileBreadcrumbs renders the crumb as a label.

A raw ~/ path reaches the preview when the agent writes one and the client can't expand it. resolvePathLinkTarget only expands ~/ when the project folder is under /Users/<name>, /home/<name>, or C:\Users\<name>.

Change

In apps/web/src/components/files/filePath.ts, the home crumb of a host path now gets the path ~/, the same way a bare drive C: already becomes C:\. The server already expands ~/ to the home folder, so clicking the crumb opens the home folder listing and keeps the trail back to the file. A project-relative folder named ~ is unchanged.

Before	After

Scope and approval

This is a small fix for an obvious bug in the existing home-path breadcrumbs. No prior issue.

Verification

• vp test run src/components/files/filePath.test.ts: all pass. The updated home-path test and the new breadcrumbPathOf("~/") case fail without the fix.
• Lint and format on the changed files: pass. I did not run typecheck. The change only returns a different string.
• In the web app, I opened ~/home-crumb-demo/notes.md in the file preview. Before the fix, ~ was plain text. After it, ~ is a button, and clicking it lists the home folder with the trail to notes.md kept.
• Desktop uses the same web code. Mobile builds its own breadcrumbs and has no host-path crumbs, so it is unaffected.

Model and harness: Claude Opus 5.5 in Claude Code, running in T3 Code. Bug found by GPT-6.1-Sol in Codex.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at af0fa15

Macroscope's review found this PR approvable — This small web bug fix makes the ~ breadcrumb resolve as ~/, allowing users to open the home-folder listing while preserving project-relative paths and other breadcrumb behavior. The accompanying tests cover the changed home-path and project-folder cases, with no product-default or static-analysis configuration changes.

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

[coderabbitai]

Warning

Review limit reached

Only developers with an assigned seat can use this organization's usage-based review budget, and seats here are assigned manually. Ask an admin to assign a seat, or change the review continuation mode in Billing.

Next included review available in 1 minute.

Check out review usage here.

View limit details

Limit details: You’ve used all 10 included reviews currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: d487078
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: 887abb72-b036-4080-a36f-65d3ac9d7842

Commits

Reviewing files that changed from the base of the PR and between af0fa15 and d5931c7.

Files selected for processing: 2

• apps/web/src/components/files/filePath.test.ts
• apps/web/src/components/files/filePath.ts

No actionable comments were generated in the recent review.

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Path: .coderabbit.config.ts
• Review profile: CHILL
• Plan: Advanced
• Run ID: d918f52d-6a97-4788-8953-1ddcef7029d5

📥 Commits

Reviewing files that changed from the base of the PR and between 81dea78 and af0fa15.

📒 Files selected for processing: 2

• apps/web/src/components/files/filePath.test.ts
• apps/web/src/components/files/filePath.ts

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

Walkthrough

The breadcrumb path logic now normalizes a bare host-path ~ to ~/. Tests cover home-relative paths and project folders named ~.

Changes: Breadcrumb paths

Layer / File(s)	Summary
Normalize home-relative paths apps/web/src/components/files/filePath.ts, apps/web/src/components/files/filePath.test.ts	fileBreadcrumbs normalizes a bare host-path ~ to ~/. Tests cover listable home-relative paths, breadcrumbPathOf("~/"), and a project folder named ~.

Priority: Low

Estimated code review effort: 2 (Simple) | ~7 minutes

Change: Bug fix

Suggested reviewers: scratchyone, angelotadeucci

Merge Risk: Minimal · up to af0fa

The breadcrumb change is narrowly scoped and covered by relevant tests, with no unresolved merge-blocking risk.

Architecture risk: Low · up to af0fa

The change affects 1 system.

Changed systems: apps/web

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — apps/web (ui) was modified; 2 changed files map to changed impact.

Before / after behavior

• observed — Modified behavior in apps/web/src/components/files/filePath.test.ts: Replaced the home-relative breadcrumb test to expect ~ at path ~/, verify both ~/ and ~/.claude are listable, and add coverage ensuring a project folder named ~ remains inside the project.
• observed — Modified behavior in apps/web/src/components/files/filePath.test.ts: Added breadcrumbPathOf("~/") coverage, expecting the normalized path to remain ~/.
• observed — Modified behavior in apps/web/src/components/files/filePath.ts: Added normalization for a bare host-path ~ to ~/; other paths retain their existing behavior.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title clearly and concisely describes the main fix: making the home breadcrumb open the home folder.
Description check		The description includes the required Problem, Change, Scope and approval, and Verification sections. It explains the bug, implementation, scope rationale, focused tests, manual verification, screensh…
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 includes the required Problem, Change, Scope and approval, and Verification sections. It explains the bug, implementation, scope rationale, focused tests, manual verification, screenshots, and the checks that were not run.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• 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.}

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

merged main into the original branch, preserving @Onkarj012's commit and its one-expression fix. resolved the test conflict with only the home-path regressions, leaving main's unrelated test trimming intact. the diff against main remains two files.

verification:

• reproduced the inert ~ crumb in chrome on main. both home-path regression tests failed against main.
• all 21 focused tests passed on blacksmith. vp run check:changed passed format, lint, affected typechecks, knip, and tests.
• chrome opened the real host home listing through ~, retained the descendant trail, and returned to the same file. uploaded video playback and seeking passed.
• two independent read-only reviews approved d5931c7 without findings.
• github ci passed; no unresolved review findings.

unverified: desktop was not launched separately. coderabbit rate-limited the new review and marked its check successful; its original review had no findings.

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

Verified in a real dev environment

verified unchanged head d5931c7d0a95b6bb0a31b634cbb77f7d2b897be6 on this linux boat vm with repo playwright and /usr/bin/google-chrome.

• reproduced on github/main (949929dda5) in a separate worktree after vp i: opening a home-relative file from chat rendered an inert ~ label.
• installed and ran the exact pr head with one dev server at a time. added a real git project at /tmp/home-breadcrumb-project through the app. real codex gpt-6.1-sol turns created/read the files and returned markdown links; no mocks, fixtures, replay provider, or database edits.
• clicked the agent's ~/home-breadcrumb-verification/notes.md link. the pr's ~ button opened the real host home listing. the descendant trail remained visible; clicking the folder and file breadcrumbs returned to the same file and contents.
• neighboring checks: the project readme and a project-relative file inside a folder named ~ opened with their correct contents and project breadcrumbs.
• blacksmith: all 21 existing filePath tests passed. vp run check:changed d487078f11f80543da83e5316a82d43b0a8addbb passed format, lint, both knip checks, affected typechecks (2 packages), and focused tests. the explicit pr base was needed because the worker starts with shallow history; fetched the head's parents first.
• git.cafe reports 28 successful checks, zero pending or failing. no source changes or pushes were needed.
• inspected the captures; uploaded video playback reached the end, and seeking worked.

Not verified

native desktop, ios/android, windows drive paths, macos, and remote/relay/tunnel connections were not exercised on this linux web-client pass. other providers were not run; the changed breadcrumb code is provider-independent. this is a behavior verification, not a performance measurement. current-base mergeability is separate from this exact-head result.