Skip to content
Oleaflyv0.4.1

Quick answers about getting started, projects, compilation, assistants, and backups.

No. Download Oleafly, open it, and write. Optional services such as a cloud AI provider or GitHub use their own accounts.

Does Oleafly support LaTeX, Typst, and Markdown?

Section titled “Does Oleafly support LaTeX, Typst, and Markdown?”

Yes. Choose the engine when you create a project. Each engine has its own editing and export capabilities. The quickstart walks through your first PDF.

Yes. Import project source, a ZIP archive, or a Git repository. Oleafly also has conversion paths for DOCX and text-based PDFs. Read Bring an existing project to choose the right route.

You can write, organize files, use local proofreading, and run a downloaded local AI model without a cloud connection. Tectonic can compile with cached packages. New packages, remote references, cloud models, GitHub, and downloads need a connection. Prepare a project with a successful compile before you take it offline.

Your projects are ordinary folders in your local library. You can copy them, back them up, or open them in another tool. Where your data lives explains project files, app settings, and checkpoints.

Yes. Start with the thesis workflow or resume workflow. Both use the same editor, preview, references, and export tools as a research paper.

Check that the file came from the official releases and matches your platform. Follow the installation guide for the platform’s first-launch steps.

Choose the architecture that matches your computer and either the AppImage or Debian package. See Linux installation for system requirements.

Tectonic may need to download packages used by this document. They are cached for later builds. Open Logs to see what is happening.

If Tectonic’s offline mode is enabled, turn it off for one compile to fetch the package. For a system TeX toolchain, check LaTeX engines & packages.

Open Logs and check undefined citations and references first. Preflight helps find the affected source locations before you export.

Ask the assistant to read the log, fix the error, and compile again. Use Ask for approval when you want to review proposed actions along the way. You can also post the log in the help forum on Discord.

Available formats depend on the engine and document type. Check the export table.

Connect a model provider, use a local model, or choose a CLI agent. Set up AI covers each route.

No. Writing, compilation, citations, previews, diagrams, project history, and exports are available without an assistant.

It can work with project files, look up sources, inspect a PDF, create figures, run tools, and help repair a build. Choose a plan and approval policy that suits the work. See Chat & tools.

The model passed a tool-call probe. It helps you choose a model for project actions; it does not evaluate the quality of its writing or research. See Set up AI.

Some providers and CLI agents do not report usage. Unknown means the value is unavailable. Read Usage & budgets.

Yes. Use a built-in CLI agent connection or enable Oleafly’s local MCP server.

Open Checkpoints to compare source from successful builds and restore a version. Use Source Control for Git commits you manage yourself.

Share source archives or use GitHub sync to exchange commits. Agree on when to pull and push so each person starts from the latest shared version.

It backs up the project source. Automatic checkpoints, app preferences, and credentials live separately. Follow the backup guide to include what you need.

Open Settings → Help & About → Copy Info and include those details with a short description, steps to reproduce the problem, and the relevant log. Report it in Issues; use the Discord community for questions and workflow help.

Image preview

AI answers couldn’t load

Try again, or search the documentation.