Skip to content

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

Closed as duplicate

Description

@2024sy

Feature hasn't been suggested before.

  • 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)

  1. AI mentions a file path in conversation: "check src/components/Button.tsx"
  2. User sees the plain text path
  3. User must look at the file tree on the right
  4. User manually expands folders to find the file
  5. 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

Activity

  1. added
    discussionUsed for feature requests, proposals, ideas, etc. Open discussion
    on Mar 14, 2026
  2. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Mar 14, 2026
  3. github-actions commented on Mar 14, 2026

    @github-actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • 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:

    If you believe this was flagged incorrectly, please let a maintainer know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreAnything pertaining to core functionality of the application (opencode server stuff)discussionUsed for feature requests, proposals, ideas, etc. Open discussionneeds:complianceThis means the issue will auto-close after 2 hours.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions