You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I right click the file, click copy path, paste it in a text document and see the full path.
It's unfortunately a tedious process especially when an agent outputs multiple file paths per response.
Confirmed on current main, which is the same tooltip code as v0.0.42. The hover tooltip is the absolute path, but it is forced onto one line and clipped at the tooltip’s max width, so the filename drops off the right edge. Paths that share a long prefix look identical. That matches the screenshot cutting off at /generat.
The chip label is only the basename (plus a parent suffix when two basenames collide). The full path is only in the tooltip, in MarkdownFileLink in apps/web/src/components/ChatMarkdown.tsx: targetPath inside a whitespace-nowrap overflow-x-auto box. That box sits in TooltipPopup (apps/web/src/components/ui/tooltip.tsx), whose viewport is overflow-clip and whose code variant is capped at max-w-120. The positioner is pointer-events-none, so the pointer never enters the popup. With overlay scrollbars, which only show while the scroll box is hovered, the overflow reads as a hard cut: no ellipsis, no scrollbar. Copy full path from the context menu still has the whole string, which is why that workaround works.
#11558 makes the popup accept pointer events so a long path can be scrolled and selected. It is the same interaction, but it is not merged, and the filename would still be off-screen until you scroll. Dropping whitespace-nowrap and letting the code tooltip variant wrap would show the full path on hover.
Related implementation: #18246 replaces the closed #8825 with a GPT-6.1 Sol rebuild. It adds an opt-in Settings → General → File chip paths option that shows workspace-relative, home-relative, or absolute paths directly in web/desktop chat chips. Short labels remain the default.
This provides inline path context without hovering, but does not change the tooltip clipping reported here. The replacement PR is still unmerged.
Activity
juliusmarminge commentedon Sep 28, 2026
Triage
Confirmed on current
main, which is the same tooltip code as v0.0.42. The hover tooltip is the absolute path, but it is forced onto one line and clipped at the tooltip’s max width, so the filename drops off the right edge. Paths that share a long prefix look identical. That matches the screenshot cutting off at/generat.The chip label is only the basename (plus a parent suffix when two basenames collide). The full path is only in the tooltip, in
MarkdownFileLinkinapps/web/src/components/ChatMarkdown.tsx:targetPathinside awhitespace-nowrap overflow-x-autobox. That box sits inTooltipPopup(apps/web/src/components/ui/tooltip.tsx), whose viewport isoverflow-clipand whosecodevariant is capped atmax-w-120. The positioner ispointer-events-none, so the pointer never enters the popup. With overlay scrollbars, which only show while the scroll box is hovered, the overflow reads as a hard cut: no ellipsis, no scrollbar. Copy full path from the context menu still has the whole string, which is why that workaround works.#11558 makes the popup accept pointer events so a long path can be scrolled and selected. It is the same interaction, but it is not merged, and the filename would still be off-screen until you scroll. Dropping
whitespace-nowrapand letting thecodetooltip variant wrap would show the full path on hover.ricardosalta commentedon Oct 10, 2026
⌾ Agent identity: vps-codex-gpt-6-1-sol-xhigh
Related implementation: #18246 replaces the closed #8825 with a GPT-6.1 Sol rebuild. It adds an opt-in Settings → General → File chip paths option that shows workspace-relative, home-relative, or absolute paths directly in web/desktop chat chips. Short labels remain the default.
This provides inline path context without hovering, but does not change the tooltip clipping reported here. The replacement PR is still unmerged.