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
{{ message }}
Repository navigation
[FEATURE]:[Web]: Clickable file:line references in messages (jump to file and line) #13430
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
In the OpenCode web UI, references to source files with line numbers (e.g. src/foo/bar.ts:123) shown in assistant messages or logs are currently rendered as plain text.
I would like these references to be clickable, so that clicking them:
Opens the referenced file in the web file viewer
Automatically scrolls to (or highlights) the specified line number
This would bring the web experience closer to the desktop version and significantly improve code navigation and review workflows.
Example
When a message contains something like:
src/XXXX.Core/XXXXX/XXXXXXX.cs:545
*.txt
Plaintext
Clicking it should:
Open XXXXXXX.cs in the web file viewer
Jump directly to line 545 (or the closest available line)
Why this matters
This is a very common workflow when reviewing explanations, logs, or analysis generated by OpenCode.
On desktop, similar references can already be navigated efficiently.
On web, users currently have to:
Manually search for the file
Scroll to the line number by hand
This breaks context and slows down debugging, review, and learning workflows.
For users relying on the web UI (including remote access or mirror use cases), this missing feature is especially noticeable.
Expected behavior / possible implementation
Possible approaches (implementation detail up to maintainers):
Detect path/to/file:line patterns in rendered messages
Render them as clickable links
On click:
Open the file in the existing web file viewer
Scroll to / focus the target line
Gracefully handle cases where:
The file does not exist
The line number is out of range
Even a minimal implementation (open file + approximate scroll) would already be a big usability improvement.
Current behavior
File and line references are displayed as plain text
No navigation or interaction is available from messages in the web UI
Additional context
This feature would also align well with ongoing efforts to improve web/desktop parity and make the web UI more suitable for serious code review and debugging tasks.
If needed, I can provide screenshots or short screen recordings to demonstrate the current limitation.
Reacted by SR, Sinisa Mikasinovic, Dmitry Spikhalsky, Artiom Neganov, 肥康 and Krzysztof Heim
I did, but I deleted my fork.
I started using OpenCode Desktop because it was great how it was showing
multiple projects and multiple chats. Over time it went the wrong
direction: now every project is a letter, no icon, no name, horrible usage
of the real estate...
I ended up deleting my fork and my PR.
Now I'm using Codex Desktop.
It's clunky when you want to work with local models, but the management of
multiple projects is so much better.
And they also have implemented the change I was suggesting.
Activity
stenci commentedon Mar 16, 2026
I opened a duplicate by mistake in #17816, but this is the right issue.
I have a working local implementation of this in the desktop app.
A few behaviors it currently covers:
utils.pyfile:linerefs likeutils.py:123utils.py:123-130/and\Attaching a short video showing the behavior.
If useful, I can open a PR or compare these behaviors against #15269 so the remaining gaps are clear.
OpenCode.Deeplinks.mp4
manifestcowboy commentedon Mar 19, 2026
Please add!
Spikhalskiy commentedon May 4, 2026
It doesn't seem like Desktop has it either, at least in 1.14.32.
file:line are rendered as plain text without an ability to navigate to them.
OnkelTem commentedon Jun 8, 2026
@stenci Do you have this as a PR?
stenci commentedon Jun 9, 2026
OnkelTem commentedon Jun 9, 2026
I see, thank you @stenci
github-actions commentedon Aug 9, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.