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
When Open Code displays file paths in chat messages, these paths are rendered as plain text. Users must manually navigate to the file tree on the right side and locate the file to open it. #17478
I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Problem Description
When Open Code displays file paths in chat messages, these paths are rendered as plain text. Users must manually navigate to the file tree on the right side and locate the file to open it.
Current Workflow (Painful)
AI mentions a file path in conversation: "check src/components/Button.tsx"
User sees the plain text path
User must look at the file tree on the right
User manually expands folders to find the file
User clicks the file to open it
Expected Behavior
File paths should be clickable/hyperlinked directly in the chat message, allowing users to jump to the file with a single click.
Use Cases
Code Review:
AI: "There's an error in src/utils/helpers.ts at line 42"
Current: User has to manually find this file in the file tree
Expected: User clicks the path and file opens at line 42
Navigation:
AI: "The configuration is in config/settings.json"
Current: User must manually navigate to the config folder
Expected: User clicks the path and file opens immediately
Multiple Files:
AI: "You need to modify both old/file.ts and new/file.ts"
Current: User must locate each file separately
Expected: User can click each path to quickly navigate
Why This Matters
Breaks the flow of conversation
Time-consuming for large projects with deep folder structures
Interrupts the coding thought process
Less efficient than expected for an AI coding assistant
Feature request titles must start with [FEATURE]: — the current title does not follow this format.
The issue appears to contain AI-generated content (extensive structured formatting, multiple use case sections, etc.), which is not acceptable per our guidelines.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Activity
github-actions commentedon Mar 14, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:— the current title does not follow this format.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
If you believe this was flagged incorrectly, please let a maintainer know.