[Bug]: relative file chips resolve against the thread's project root, not the directory the agent worked in
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- typescript
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- TypeScript
- スター
- 24.8k
- フォーク
- 6.4k
- 平均マージ
- 4時間 16分
- マージ済み PR（30日）
- 352
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
pingdotgg/t3code のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 1 日以内に返信
pingdotgg/t3code の issue をすべて見る
似ている issue
-
Autocomplete still accepts an option after becoming disabled対応中かも @Xapollon430 が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
reduxjs/react-redux#2416 · コメント 1 件 ·