-
Notifications
You must be signed in to change notification settings - Fork 1k
Open
Labels
enhancementRequested improvement or new capability.Requested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I am describing a concrete problem or use case, not just a vague idea.
Area
apps/desktop
Problem or use case
LLMs often emits URIs in output, but they are currently plain text.
This this forces users to copy/paste links manually, which is slow and error-prone, especially when the assistant is referencing files, local resources, or web pages as part of a coding workflow.
Proposed solution
Detect supported URIs in assistant output and render them as clickable links.
Why this matters
This would benefits anyone using T3 Code for development, debugging, or navigation across local files and web references. The outcome is faster iteration, less copy/paste, and a more natural “assistant as navigator” experience.
Smallest useful scope
Make relative/absolute file paths, http/https links, clickable. Use default handler.
Alternatives considered
No response
Risks or tradeoffs
No response
Examples or references
Codex in Warp Terminal
Contribution
- I would be open to helping implement this.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementRequested improvement or new capability.Requested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.