1.11.0: clicking a file path got smarter
As of 2026-07-25. A snapshot; the living reference is the configuration guide.
Nothing to configure — just click.
What changed
Clicking a file path an agent printed used to do the same thing whatever the file was: serve the bytes. A .md opened as source, a .csv as a wall of commas, a .ts as plain text. Each kind now opens as the thing it is.
| Kind | Opens as |
|---|---|
.md | Rendered (follows your system light/dark setting) |
.json | Indented |
.csv / .tsv | A table with a sticky header, scrolling inside its own box |
Source, .txt (about 40 extensions) | The in-app Files view — editable, highlighted |
| Images / PDF / SVG / HTML | In a browser tab, as-is |
How to use it
Have an agent write something out and click the path it prints. Only files inside that session’s working directory.
The CSV parser follows RFC 4180 and is written out rather than pulled in — its output was cross-checked against Python’s csv.reader and that agreement is pinned as a test. A loose parser silently splits a field in half, which is a wrong table nobody notices.
The Files view is linkable
/files takes a ?path=, so the file being edited rides the URL. Reload and the same file opens; the URL can be shared.