On this page
Files and workspaces
Browse one or more workspace roots, search the right files, and keep project context focused.
A project is the work you want to change. A workspace can contain one folder or multiple repository roots. The Files pane keeps each root distinct so you can browse, search, preview, and add the right context to a task.
Open the smallest useful folder or workspace
For an empty workspace, use the editor's Open Folder flow. RevampKey does not add a separate product-specific Add Folder button.
Expand the roots and directories you need
Single-root workspaces show one root header. Multi-root workspaces show a distinct header for each root; expand directories beneath the root that owns the behavior you want to inspect.
Choose files for preview or chat context
Click a file for a preview. Double-click it to pin it when you need it to remain visible, or use Add to chat to include it in the current request.
Search, refresh, and review status before starting
Search by file name or path across all roots, refresh when the project changes, and use drag, multi-selection, or Cmd/Ctrl+Enter where supported by the current editor surface.
Distinct roots
Each repository keeps its own root header and directory tree in a multi-root workspace.
Fast file actions
Preview with a click, pin with a double-click, drag items, or add a selection to the active chat.
Search across roots
Search matches by name or path across the roots currently open in the workspace.
Understand the visible states
| State | What you see | Useful next action |
|---|---|---|
| Loading | A root or directory is still being read. | Wait for the tree to settle before selecting files. |
| No folder | The workspace has no folder open. | Use the editor's Open Folder flow. |
| Empty | A root is open but has no visible entries. | Check the folder and workspace you opened. |
| No results | A name or path search found no match across the roots. | Try a shorter name, path segment, or another root. |
Git status letters can appear beside files when the repository exposes them. Treat them as a quick cue, then review the file itself and the project's Git state before deciding what belongs in the task. Common visible letters include M for modified, A for added, D for deleted, and ? for untracked content.
For structural context that is separate from browsing files, read Codebase Structure. For extra task inputs, see Context and attachments.