Cloning a repository
In an empty workspace, choose Clone from GitHub from File actions or the empty file explorer. Pasteowner/repo or the repository URL. To clone into a workspace that already has files, create a new workspace first. If the option is unavailable, turn on Show hidden files to check for existing contents.
Cloning defaults to Latest commit only, which is much faster; turn it off when you need history. Cancelling part-way removes what had arrived, so the workspace is empty again. The repository’s .git folder is hidden from the file tree and skipped by search like other dot-folders. Private repositories need GitHub access — see MCP integrations.
Downloading files and folders
Right-click a file or folder and select Download. Folders download as ZIP archives. Large downloads may need preparation; keep the app open until the download starts. If a transfer is already being prepared, wait and retry. Files too large for the editor offer a Download button so you can open them elsewhere. Folder archives have a deployment-specific size limit and omit symbolic links and workspace metadata or credential files. Qualia reports skipped entries. Empty folders cannot be downloaded as archives.Uploading files
Add files to the workspace by dragging them from your machine into the file tree, or with File actions → Upload files. Folders can be dragged in the same way, or chosen with File actions → Upload folder — see Folder uploads. Dropping onto a folder uploads into that folder; the toolbar actions upload into the workspace root. A progress notification shows how many files have finished. You can dismiss it without stopping the upload. Incoming files appear at their destination while uploading. Use Cancel upload in the Files header or notification to stop the batch, or × on an incoming file to cancel it individually while that action is available. Files already uploaded stay in the workspace. Failed transfers retry automatically. Only one upload runs at a time; wait for it to finish before adding another batch.Switching workspaces mid-upload
Switching workspaces stops the current upload. Files already transferred remain in the original workspace; the notification reports what finished.Uploading a file whose name already exists does not overwrite it. The server keeps both by renaming the new one (
data.csv becomes data (1).csv), and the upload toast tells you when this happened.Large uploads
Cloud uploads normally support files up to 30 GiB, depending on your deployment. Other remote workspaces may have lower limits; an oversized-file message shows the applicable limit. Local uploads are limited by available disk space. Large files can take time to finish after their transfer appears complete. Wait for completion confirmation before using them, and keep the app or browser tab open. The destination folder and incoming files cannot be moved or renamed while uploading.Still syncing
A file may show Syncing… before it is ready to use. Wait for it to finish, or choose Retry sync if the action appears after a long delay.Folder uploads
Whole folder trees upload the same way individual files do: drag a folder from your machine into the file tree, or use Upload folder from File actions or a folder’s context menu. The folder’s structure is recreated at the destination. Some contents are skipped rather than failing the upload:- Dependency and scratch directories (
.git,node_modules,.venv,venv,__pycache__,.ipynb_checkpoints) and.DS_Storefiles are left out. - A file or folder the browser cannot read is skipped and the rest of the upload continues.
Edit text files together in Cloud
Owners and Editors can edit the same text file at the same time, including Markdown source files up to 64 MiB. Viewers and Commenters can watch the shared draft. Hover over a collaborator’s cursor or avatar to see their name. Undo affects your own edits. Changes synchronize automatically, but saving is manual. Use File → Save or Cmd/Ctrl+S to write the shared draft to the file. Syncing… means edits are still being sent; Shared draft · Not saved to file means they have synchronized but need saving. Saved to file confirms the save. A synchronized draft remains available after you close the file. If Syncing edits before leaving… appears, wait for synchronization or choose Stay here. If it fails, Retry keeps your editor open while trying again. Heed the browser’s warning before refreshing or closing a tab: unsynchronized edits can be lost.Changes from agents or the terminal
Agents and shell commands use the saved file. Their changes do not automatically merge into the shared draft. A changed on disk notice means the saved file has changed while your shared draft remains available.- To keep your draft separately, use File → Save As and choose a new path. The original shared draft stays open.
- To replace the shared draft with the saved file, choose Reload saved file in the notice, or Revert unsaved changes in the command palette. Confirm only when you want to replace unsaved edits for everyone.
- If saving reports a conflict, keep a separate copy or reload the saved file before continuing.