[Feature]: Defer file links that T3 code cannot handle to the OS

[tyteen4a03]

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/web

Problem or use case

Coding agents sometimes generate artifacts (videos, pdfs) that cannot be opened by T3 Code. Clicking on links for these show an unhelpful "cannot handle" error.

Proposed solution

For any artifacts that T3 code cannot (yet) natively open, it should defer to the OS to handle, either through the file picker functionality in the system, or default to File Explorer / Finder.

Why this matters

The links would otherwise be useless.

Smallest useful scope

The File Explorer / Finder solution, but ideally there should be an option to choose either option in the settings.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.