[Bug]: relative file chips resolve against the thread's project root, not the directory the agent worked in
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
The issue identifies the affected area as apps/web chat file chips but does not name implementation files or tests. Start by tracing how inline file paths become chips and how their base directory is chosen, then inspect how thread activity records working directories. Done when a real relative path from another checkout opens from the correct root, with a defined fallback when that root is unavailable.
Written by the indexing model from the issue text.
Description
before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
area
apps/web (chat file chips)
what happens
an assistant message lists files with repo-relative paths in inline code, e.g. docs/guides/new_guide.md.
t3 renders a chip, but resolves it against the thread's project root.
the agent did its work in a different checkout (a worktree of another repo), so the chip opens "the file could not be accessed or read" even though the file exists and the path is correct relative to where the agent was working.
steps to reproduce
-
create a thread in project
repo-a(root/Users/me/devel/repo-a). in my case the thread was spawned through the t3 mcp orchestration tools, so it has noworktreePathand no branch. -
in that thread, have the agent
cdinto a worktree of a different repo, e.g./Users/me/devel/worktrees/repo-b-feature, make changes there and open a pr. -
the agent summarises the pr with repo-relative paths:
- `docs/guides/new_guide.md` is the new guide. - `server/config.yaml` and `config.test.yaml` each gain two lines. -
click a chip.
expected
the chip opens /Users/me/devel/worktrees/repo-b-feature/docs/guides/new_guide.md, or at least does not pretend to be a working link.
actual
the chip opens /Users/me/devel/repo-a/docs/guides/new_guide.md, which does not exist, and shows the "could not be accessed" panel.
a bare filename like config.test.yaml fails the same way.
why this is different from the existing issues
- #29421 / #30021 / #29657 deal with paths that do not exist anywhere (example paths in prose). #30021 (closed unmerged) would have rendered missing paths as plain code, #29657 keeps the full label but leaves them clickable. here the path is real, only the resolution root is wrong, so neither direction makes the chip work.
- the second comment on #29421 is the same shape (a correct path for another workspace), but framed as "should fall back to plain code".
- #30285 is related: pr descriptions turn the author's paths into links that open on the viewer's machine. same root cause, a path is resolved against the wrong base.
possible directions
- resolve relative chips against the agent's working directory at the time of the message (the cwd of the session, or the last
cd/ tool-call cwd t3 already sees in the activity log), falling back to the project root. - when the path does not exist under the project root, try the worktrees / checkouts the thread touched (its linked prs' head checkouts,
worktreePath), and only then fall back to plain code as in #30021. - for mcp-spawned threads that work in another repo, let the agent set or update the thread's working root, so chips and the diff view follow it.
workaround
instruct the agent (CLAUDE.md / AGENTS.md) to always write absolute paths in chips. this works, but agents drop it easily when listing files changed in a pr, because they naturally think in repo-relative terms there.
environment
t3 code desktop 0.1.9-nightly.20261110.4478, macos 26 (darwin 25.6.0), claude agent provider.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 4h 16m
- Merged PRs (30d)
- 352
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
Autocomplete still accepts an option after becoming disabledPossibly taken @Xapollon430 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
reduxjs/react-redux#2416 · 1 comment ·