[FEATURE]: Make local file paths clickable in terminal output

[Xi0ng8]

Problem

When opencode generates files (reports, documents, images, etc.), the file paths displayed in the terminal are not clickable. Users have to manually copy the path and run open <path> to view the files.

Current Behavior

File paths appear as plain text in the terminal, requiring manual copy-paste to open.

Expected Behavior

File paths should be rendered as clickable links using the file:// protocol, similar to how iTerm2, VS Code Terminal, and other modern CLI tools handle local paths.

Use Case

When running tasks that generate multiple files (reports, charts, documents), users need to quickly open and review these files. Currently, they must manually navigate and open each file.

Suggested Implementation

1. Detect file paths in output
2. Render using file:// protocol prefix for clickability
3. Or provide a command like /open <filename> to open recent files

Environment

• OS: macOS
• Terminal: iTerm2 / Terminal.app
• Use case: Generating reports, charts, and documentation files

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• Feature request titles must start with [FEATURE]: (e.g., [FEATURE]: Make local file paths clickable in terminal output)

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:

• [FEATURE]: Desktop: Clickable file paths in chat to open/reveal in Explorer #17209: Clickable file paths in chat to open/reveal in Explorer (Desktop)
• [FEATURE]: Clickable file paths in agent responses #11432: Clickable file paths in agent responses
• [FEATURE]: Make file references in assistant responses clickable #17816: Make file references in assistant responses clickable

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

[github-actions]

Thanks for updating the issue! It now clearly describes the problem, current behavior, expected behavior, and includes environment details. Everything looks good — appreciate you taking the time to fill it out properly.

[Xi0ng8]

Clarification:

The core issue is that clicking on non-URL text incorrectly prepends http:// to the path.

Examples:

• Output: reports/ → Click opens: http://report (fails)
• Output: test_report.xlsx → Click opens: http://test_report.xlsx (fails)

Expected behavior:

• https:// links: Open in browser (works correctly)
• Local file paths: Should open with system default handler, not prepend http://

[ctf0]

we need a URL handler, similar to sublime, vscode & claude Claude Code URL Handler.app