Find, preview and share files
On this page
Find the right code or document, inspect it and give an agent precise context.
Before you start
Open the workspace and its file sidebar. Scrolls is the file browser; Peruse is the built-in file viewer.
Open a file
- Choose All to browse the workspace tree, or Changed to focus on Git changes.
- Single-click a file for a preview. Double-click it to keep it open as a persistent file tab.
- For Markdown, use Preview to read the rendered document and Raw to inspect the source.
- Use the file action menu for Open in Editor, Open Containing Folder or Copy Path.
Source text, rendered Markdown and supported images have in-app viewing routes. Markdown can be exported to PDF. Use an external application for formats the viewer cannot render; PDF export is not the same as a universal PDF reader.
Search the right place
| What you need | Where to search |
|---|---|
| A filename | All → Search the archives…; filename wildcards such as *.rs work |
| Text in the current file | Focus Peruse and press Ctrl/Cmd+F |
| An earlier terminal message | Focus that terminal and press Ctrl/Cmd+F |
| Text in changed code | Ask the agent to inspect and search git diff in its terminal |
| Text across repository files | Ask an agent to search the repository, or use your external editor |
Filename search does not search directory paths or file contents. Check the repository path shown under each result when repositories contain matching filenames. If the file index is stale, use the refresh icon beside Scrolls, then search again.
Give files to an agent
Right-click the correct file and choose Copy Path. Focus the agent terminal, type your instruction and paste the path using that terminal's paste shortcut (Ctrl+Shift+V in the recorded Linux session). Submit the instruction directly in the terminal. You can also drag a workspace file row into the focused terminal or use the row's > action to insert its path.
For a shared image, attach it to a synced Thy Quill note, then ask the agent directly in its terminal to retrieve and open that attachment through its tools. Wait for the upload to finish and verify the actual image it opens.
Read the attached screenshot and the settings component at this path. Explain why the empty state differs from the design, then propose a focused change.
Edit a file
Use Open in Editor for normal source editing, or give the agent a precise edit instruction in its terminal. Ask it to show the saved change and relevant checks. Peruse is principally a viewer rather than a full embedded code editor.
Check the result
Confirm that the agent identifies the actual file and attachment. After editing, reopen the file or its diff and check the saved content.
The recorded example
The native video searches for readme in Ember Studio, which contains separate app and website repositories. It opens the app's README.md, keeps it in Peruse, switches to Raw, and searches its contents for device. It then copies that file's path and pastes it into the agent terminal with this instruction:
Read [the copied path]. Tell me the commands under Run and what Local data says about saved view and search. Report the exact file path and its SHA-256. Save these results in file-context-proof.json. Preserve every existing file and note. No tests, commits, workers or external actions.
The agent reads the actual file, returns npm run dev and npm test, and identifies that this demo app saves its view and search on the same device. Its returned path, file hash and saved result are checked against the original file. Existing files and Quill notes remain unchanged. The video finishes by returning to the same persistent README in Peruse.