Files & preview
Browse the project, open any file in a viewer that fits it, and read code or watch documents update beside the terminal while an agent works.
File browser
Press ⌘B
to show the folder of the active terminal. It follows cd and refreshes when files change. The .* button shows or hides hidden files.
File viewer
Click a file in the browser and it opens in the preview panel beside the terminal; ⌘-click (Ctrl-click on Windows and Linux) or Open in tab opens it in a tab, where you can edit code and other text. (A file path clicked in the terminal works the same way.) A tab shows each file with the right view:
| File | How it opens |
|---|---|
| Markdown | Rendered, with tables, images and ```mermaid diagrams. Source switches to the editor. |
| Page through and zoom. | |
Word (.docx) |
A readable rendering of the document. |
| Images | PNG, JPEG, GIF, SVG, WebP, BMP, ICO. |
| HTML | A static render (scripts don’t run). Source switches to the editor. |
Mermaid (.mmd) |
A live diagram with a chat box that edits it through a local Ollama model. |
| Anything else | The Monaco code editor with syntax highlighting. ⌘S |
| saves. |

In rendered documents, links behave the way you’d expect: web links open in your browser, #section links scroll to the heading, and relative links such as ../README.md open that file in a tab. Relative images load from the document’s own folder.
Preview panel
Click a file path in the terminal, or a file in the file browser, and the file opens in the preview panel beside the terminal, whatever kind of file it is. Focus does not move into the panel. Press ⌘⇧B to show or hide the panel; opening it this way moves focus into it, and Esc gives focus back to the terminal. (With text selected in the panel’s editor, the first Esc clears the selection and a second one returns to the terminal.) Each tab has its own file in the panel.
- Code and other text shows read-only in the same Monaco editor as the file tab, with syntax highlighting. Open in tab opens the file in a tab, where you can edit and save it. That includes Mermaid (
.mmd) files and contract ABI/IDL.jsonfiles, which the panel shows as code: their diagram and ABI views are in the tab. - Large files: a text file over 2 MB shows its first 2 MB (“Showing the first 2.0 MB of 48.3 MB.”). It has no Open in tab. A ⌘-click still opens it in a tab, which loads the whole file.
- Not UTF-8: text that isn’t valid UTF-8 shows with the unreadable bytes replaced. It has no Open in tab, because the tab can’t edit it; a ⌘-click opens a tab that shows a read error.
- Binary files (a NUL byte near the start, as in a
.zipor UTF-16 text) aren’t shown: the panel says “Binary file, not shown” with its size. - Markdown, HTML, PDFs, Word documents and images render as they do in the file tab. PDFs page and zoom with the same viewer the file tab uses, so they render the same on macOS and Linux.
With LIVE on (the button in the panel’s header), the panel follows the file as it changes, handy for watching an agent write a spec or a source file. It refreshes shortly after each write, and about once a second while a file keeps growing, such as a log. Your scroll position and cursor stay where they were.
- Deleted on disk: if the file is deleted, the panel keeps showing its last content under a “Deleted on disk” note, and checks for it every few seconds (less often the longer it is gone, at most every 30 seconds). When the file comes back, for example after a rebuild of
dist/or agit checkout, the note goes and the panel follows the new file. - Not live: if the file can’t be watched, the footer says “Not live” with the reason, and the panel tries again after its next good read of the file. Your LIVE/STATIC choice is not changed, and another file starts fresh. Refresh always shows the file as it is now.
- On macOS, a folder moved away with nothing put in its place may show no note; the panel picks the file up again when it is back.
HTML in the preview may run scripts, for pages that need them. They run isolated from the app.
Safe by default
Markdown and documents come from repositories you may not control, and the app has access to your terminals. Everything rendered is sanitized first, so raw HTML or a javascript: link in a README can’t run code in ADE.