Your files and data
Know what travels with a project and how to back up source, history, and app data.
Este conteúdo não está disponível em sua língua ainda.
Your manuscript is a folder of ordinary source files. You can open those files with another editor, back them up, or take them out of Oleafly.
Project files
Section titled “Project files”Library projects normally live under ~/.oleafly/projects/. A project can contain a LaTeX, Typst, or Markdown main document, a bibliography, figures, and research material.
project.json records the project’s identity and settings, including its main document, engine, and pinned Typst version. A .git directory holds Git history. A project Oleafly creates or imports normally starts with one commit of its files, called “Create project” (see Git and source control). The .oleafly/build/ directory contains generated build output and can be recreated by compiling.
A Typst project can keep copies of the packages it imports in a typst-packages folder, so it compiles offline and on other computers. Typst also uses the fonts in a project’s fonts folder. Both folders travel with the project.
A folder you open in place stays where it is. Oleafly keeps that folder’s builds, settings, checkpoints, and chats in its own data folder, so nothing is added to yours.
Data stored outside the project
Section titled “Data stored outside the project”App preferences, encrypted provider credentials, chat and usage records, downloaded tools such as extra Typst versions, and saved checkpoints belong to local app storage. So do the copies of a project that Oleafly keeps from before each assistant or agent turn, which let you undo the files that turn changed. The copy of your Zotero library that @ search reads lives there too, not in the project. Copying a manuscript folder does not copy all of that app data.
Linked folders remain in their original locations. A source archive does not include their contents merely because you linked them.
Back up your work
Section titled “Back up your work”| What you want to keep | How to keep it |
|---|---|
| Manuscript source and project assets | Copy the project folder or export a source ZIP |
| Git commits | Back up the repository or push to your configured remote |
| Saved checkpoints | Export an encrypted history archive from Versioning |
| App preferences and local records | Include the Oleafly data directory in your normal computer backup |
| Linked data and references | Back up their original folders |
| Library projects and settings, off this computer | Turn on cloud sync to keep a copy in your Dropbox |
A source ZIP excludes build caches and Git. Use GitHub sync for a remote repository and checkpoint archives for checkpoint history.
Move to another computer
Section titled “Move to another computer”Install Oleafly and copy or clone the manuscript project. Reconnect linked folders and model providers on that machine. The project carries its compiler choice and metadata; additional tools or packages may need installation. A Typst project that pins a version this computer doesn’t have offers to download it before compiling.
Paths on screen
Section titled “Paths on screen”Paths inside your home folder appear as ~/… in Settings, version history, engine and agent details, and chat. In Settings, file and folder paths also stay blurred until you hover over them or reach them with Tab, so a screenshot doesn’t show where your files live.
Network access
Section titled “Network access”Writing and local proofing happen on your machine. Hosted AI receives the context supplied to the selected provider. Zotero citations talk to the Zotero app on your computer, or to zotero.org when you connect an account. Citation search, Zotero import, the alphaXiv tools, GitHub sync, Typst package and version downloads, other downloads, and update checks contact their respective services. Live collaboration sends each shared project to the collaboration server it is shared on. Cloud sync sends your library projects and settings to your own Dropbox. Opening Settings → Help & About fetches public numbers: the project’s GitHub star and fork counts and how many members are online in the Discord community. The requests carry no account, project, or usage information, and offline mode skips the Discord one. Tectonic and Typst both support cached compilation through offline mode.