Workflows and apps
Local folders and files
Attach a folder on your PC to a conversation, edit the originals with a safety version behind every save, restore from local history, and keep a cloud copy of a file.
Attach a folder to a conversation
Open Local files from the composer's + menu, choose Work on originals, then Choose folder on this PC or drop a folder on the window. The app's consent window asks Use this folder in this conversation? and the Folder permission: Read and edit files (save changes and new files in this folder) or Reference only (read files without changing them). Use folder attaches it. A conversation can hold up to ten folders; each shows as a chip under the composer with FOLDER or REFERENCE on it.
Use this folder in this conversation?
Automatic local history preserves originals.
Files stay on this PC. Relevant file content may be sent to the AI to answer your request.
The Local files pane
The pane opens in the right dock. The header shows the folder, its access (Read and edit or Reference only) and This PC, then History, Terminal, Refresh files and More folder actions: Add folder, Disconnect folder, Browse project file, Open path or new file. FILES on the left lists the folder with Filter files; with several folders attached, Active local folder switches between them. Lato reads the latest file on your PC every time; nothing is cached stale.
Choose a file to read or edit.
Lato reads the latest file on your PC. History is opened only when you ask for it.Edit originals and save on the PC
Open a file and the editor reads Editing original on PC. Save writes it back to the same file and records a safety version first: Saved on PC · Safety version recorded. A reference-only folder opens files but never writes. Tag file in chat puts the file into your message so Lato works on that exact file; when Lato edits it for you, the same safety version is kept.
Executive summary
Harbourline Logistics needs a rear extension that keeps the loading dock open through the build. This proposal sets out a staged approach, itemised by labour and materials, with allowances stated as allowances.
Local history and restore
History lists every managed edit as a task with the files it touched. For each file: Restore before edit, Compare with current file, and Restore files on PC for the whole task. Safety versions stay on the PC with the originals; nothing is uploaded. Manage history storage frees older versions: Free older local history keeps the newest 100 finished tasks and removes older recovery versions.
Safety versions are kept on this PC for every managed edit. Manage history storage keeps the newest 100 finished tasks.
Cloud copies
A cloud copy is a saved file uploaded to your account so you can reach it when the PC is offline, for example from your phone. From an open, saved file choose Create a cloud copy; the dialog says what it is: an independent copy that does not sync, with the local original and its history staying on the PC. Cloud copies, from the folder chips or the Local files popup, lists them with Download and Attach to chat.
Upload the full saved file to your account so you can access it when this computer is offline.
This creates an independent copy. Future edits to the local file and cloud copy do not sync. The local original and its history stay on this PC.
The local terminal
Terminal opens a Local terminal on the PC inside the pane, in the attached folder. Use it to run and test the project you attached; the code agent uses the same terminal for the attached project when you ask it to run checks. It needs the PC online with computer access enabled; saves are never queued while disconnected.
$ npm test
> storefront@0.1.0 test
> vitest run
✓ src/App.test.tsx (4 tests) 212ms
Test Files 1 passed (1)
Tests 4 passed (4)
$ ▍Practise this in Oppermind Academy
Follow the related tutorial or course and apply the concept to a real task.