Skip to content

FAQ & troubleshooting

No. Oleafly has no accounts and no login. Install it and write. See the Philosophy.

Only for a few explicit things: fetching a LaTeX package the first time a document uses it, citation lookups, cloud AI providers (local Ollama excepted), GitHub sync, and update checks. Writing, compiling (after first fetch), spellcheck, grammar, diagrams, and Preflight all run offline. Offline mode (Settings, General) guarantees the compiler never touches the network.

Plain folders under ~/.openleaf/projects/, each with your .tex, .bib, images, and a real .git repo. Back them up, copy them, or open them with other tools freely. See Where your data lives.

Yes. The Tectonic engine emits real selectable Unicode text with embedded subset fonts, and the ATS-badged resume templates follow single-column, linear-reading-order rules. Then Preflight shows you exactly what a parser extracts from your PDF, so you’re not taking anyone’s word for it.

Short answer: everything runs on your machine, offline, for free, with your files in real Git repos. Long answer with tables: Why Oleafly.

macOS says the app is damaged or can’t be checked

Section titled “macOS says the app is damaged or can’t be checked”

The builds aren’t notarized yet. Right-click the app and choose Open, or clear the quarantine flag once; the exact commands are in the install guide.

Click More info, then Run anyway. Same cause: unsigned builds, on the roadmap.

Anything 2024-era or newer (glibc 2.39+): Ubuntu 24.04+, Fedora 40+, Debian 13+. AppImage, deb, and rpm are all published.

That’s the one-time package fetch: Tectonic downloads what your document needs and caches it. Every compile after that is fast and offline. See Compiling.

A package is missing and the compile errors out

Section titled “A package is missing and the compile errors out”

If Offline mode is on, turn it off for one compile so the package can be fetched and cached, then turn it back on.

The compile succeeded but with warnings. Do I care?

Section titled “The compile succeeded but with warnings. Do I care?”

You still got a PDF (the amber chip tells you). Click Logs to read them; undefined references and citations are the warnings most worth fixing, and Preflight pinpoints those precisely.

Open Logs for the parsed error list, or just ask the AI: “fix the LaTeX errors” runs a compile-read-fix-verify loop with your approval on every change.

Yes, and Oleafly downloads it for you automatically on first use. No manual install. See Export formats.

OpenAI, Anthropic, Z.AI (GLM), Groq, OpenRouter, DeepSeek, Mistral, xAI, and Ollama for fully local models. Models and setup: Set up AI.

The AI says it has no key / errors on send

Section titled “The AI says it has no key / errors on send”

Open Settings, AI Assistant and check that a provider has a saved key and the green Active badge. The error messages themselves usually say what’s wrong: invalid key, empty balance, or rate limit.

Yes: install Ollama, ollama pull llama3.2, then Check for Ollama in settings. No key, no cloud.

Can the AI change my files without asking?

Section titled “Can the AI change my files without asking?”

No. Every file-changing tool pauses for your approval with a diff, and the assistant checkpoints your project in Git before its first edit. See Chat & tools.

I don’t see a device code when connecting

Section titled “I don’t see a device code when connecting”

Try again in a moment, or use the PAT route under “Advanced: use a personal access token” in Settings, GitHub.

Push fails with “No remote ‘origin’”

Section titled “Push fails with “No remote ‘origin’””

Publish the project first (Source Control, Publish to GitHub). Push and Pull need a remote to exist.

Pull first, then push. The ahead/behind indicator next to the branch pill warns you before this happens.

Yes: push on one, pull on the other. The workflow is spelled out in GitHub sync.

Oleafly shows the raw Git message and leaves resolution to you: fix it with any Git tool (the project is a normal repo), then keep working in the app.

Add ~/.openleaf/projects/ to your normal backup, export a .zip per project, or push to GitHub. All three, ideally. See Where your data lives.

Deleting removes the folder from disk, so: from your backup or from GitHub if you pushed it. Files deleted inside a project can come back via Git history if they were ever committed.

Can I edit project files with another editor?

Section titled “Can I edit project files with another editor?”

Yes, they’re plain files. Do it while the project is closed in Oleafly (or reopen it afterward), so the app’s autosave doesn’t overwrite your external changes with what it had in memory.

  • Search the issues.
  • The app logs errors to ~/.openleaf/app.log; include the relevant snippet in a report.
  • Open a new issue with steps to reproduce and your OS.