Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: File path truncated in tooltip

Open Beginner friendly
#14,160 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
frontend, web-dev

Research direction

Start in apps/web and reproduce the issue by starting a new chat with an agent that outputs a deeply nested file path, then hover over the filename. Trace the tooltip rendering and verify that the complete path is visible rather than cut off, including in Firefox.

Written by the indexing model from the issue text.

Description

bug via-triage
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

Steps to reproduce
  1. start new chat with agent
  2. agent outputs a path to a file that is deeply nested in multiple directories
  3. hover over the filename to see the path
Expected behavior

I should see the full correct path

Actual behavior

The path is truncated and thus is identical to numerous other files the agent is typing

Impact

Minor bug or occasional failure

Version or commit

V0.0.42

Environment

Firefox 156.0.1 64 bit

Logs or stack traces
In the screenshot: the path is cutoff after "/generat" thus not letting me know which file it actually is.
Screenshots, recordings, or supporting files

Screenshot 2026-09-28 161907.png

Workaround

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.

Dominant language
TypeScript
Stars
23.6k
Forks
6.1k
Avg merge
10h 20m
Merged PRs (30d)
309

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.