Feature hasn't been suggested before.
Describe the enhancement you want to request
Problem
When an agent responds with file paths in its text (e.g., mentioning src/components/Button.tsx or /path/to/file.ts), users currently cannot click on these paths to quickly open the file in the review panel. This requires users to manually:
- Copy the file path from the response
- Use the "Open file" command (Cmd+P)
- Paste and search for the file
- Select and open it
This creates unnecessary friction, especially when the agent mentions multiple files or when navigating through code explanations.
Proposed Solution
Make inline code elements in agent markdown responses clickable when they look like file paths. Clicking should:
- Open the file in a new tab in the review panel
- Focus the newly opened tab
- Load and display the file content
Expected Behavior
When an agent responds with text like:
The main rendering logic is in packages/ui/src/components/markdown.tsx and the styles are in packages/ui/src/components/markdown.css.
Users should be able to:
- See a pointer cursor when hovering over the file paths
- See an underline effect on hover for visual feedback
- Click to immediately open the file in the review panel
Supported Path Formats
- Relative paths:
src/components/Button.tsx
- Dot-relative paths:
./src/foo.ts, ../bar.js
- Absolute paths:
/home/user/project/file.ts
Use Cases
- Code review: Agent explains changes across multiple files - click to navigate between them
- Debugging: Agent identifies problematic files - click to inspect immediately
- Learning codebase: Agent describes architecture - click to explore referenced files
- Refactoring: Agent suggests files to modify - click to open and edit
Feature hasn't been suggested before.
Describe the enhancement you want to request
Problem
When an agent responds with file paths in its text (e.g., mentioning
src/components/Button.tsxor/path/to/file.ts), users currently cannot click on these paths to quickly open the file in the review panel. This requires users to manually:This creates unnecessary friction, especially when the agent mentions multiple files or when navigating through code explanations.
Proposed Solution
Make inline code elements in agent markdown responses clickable when they look like file paths. Clicking should:
Expected Behavior
When an agent responds with text like:
Users should be able to:
Supported Path Formats
src/components/Button.tsx./src/foo.ts,../bar.js/home/user/project/file.tsUse Cases