Blue inline links in extension lead to poor user experience in many cases

Resolved 💬 3 comments Opened Dec 25, 2025 by btraut Closed Mar 29, 2026

What version of Codex is running?

0.63.0

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

_No response_

What issue are you seeing?

<img width="944" height="266" alt="Image" src="https://github.com/user-attachments/assets/4b09ef36-eb96-4000-9d50-7fc5d1b86efa" />

I like the idea of linkifying file paths and URLs, but there's a number of problems with their current implementation:

  1. In cases such as the one above, the agent is trying to tell me something about the hostname, but the hostname is stripped off and I must hover in order to understand what it's saying.
  1. Worse still, I've seen a number of cases where it failed to differentiate between many files that were named similarly but different only in (hidden) base path. I don't have a screenshot handy, but it said something along the lines of, "This problem happened in <package.json> and <package.json>, but not <package.json>".
  1. All these links show a cursor:pointer when very few of them are actually clickable. It's a great feature to be able to click them to navigate to parts of the code or to pop a URL into my browser, but if it's not actually a real URL I'm intended to follow, it doesn't make sense to linkify or give me a pointer.

What steps can reproduce the bug?

See conversation id 019b543d-d834-7211-84d7-f596097e6494. I'm not sure how to repro exactly, but it's not too hard to prompt your way into similar issues.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗