Oleafly beta

Deutsch | English | Español | Français | 日本語 | 한국어 | Português | Русский | 中文 | العربية

A live collaborative LaTeX, Typst & Markdown editor for research.

Oleafly is a powerful editor for research writing in LaTeX, Typst and Markdown. The source, PDF, citations, figures, checks and Git history of a project all sit in one place. Write with your coauthors in real time, keep your projects in sync across computers, and bring Claude Code, Codex or any model you like into the project.

Free forever · Open source · No Oleafly account · No tracking

Why Oleafly

Everything here is free, including what other editors keep for paid plans: real-time collaboration with as many coauthors as you invite, full version history, Git and GitHub sync, Zotero, grammar checking and AI.

• Write with your coauthors in real time, with shared cursors and comments, on a server your lab sets up with one command.
• An editor made for long documents: completion for labels, citations and commands, live error checking, an outline of the whole project, Vim and Emacs keys, a visual mode and a searchable palette of 236 LaTeX symbols.
• Compile on your own computer. Tectonic, Typst and Pandoc are built in, and TeX Live, MacTeX, MiKTeX or TinyTeX take over when a project needs a full distribution.
• Click in the PDF to jump to the source and back, and the last good PDF stays on screen while you fix an error.
• Every project is a Git repository you can push to GitHub, and checkpoints save a snapshot after each successful compile.
• Cite from your Zotero library as you type, and search arXiv, Semantic Scholar, Crossref, PubMed and OpenAlex without leaving the editor.
• Spelling and grammar checks tuned for academic writing run on your computer.
• Preflight catches broken references, missing figures, fonts that didn't embed, accessibility gaps and anything that would unblind a review, before you submit.
• Draw figures that stay as TikZ, Typst or Mermaid code, and start from more than 1,700 templates for papers, theses, slides, posters and CVs.
• Import from Word, a PDF, an arXiv source, a GitHub repository or an online LaTeX account.
• Cloud sync keeps your projects on every computer you use, and you can keep writing offline.
• Claude Code, Codex and 12 more agents work inside your project, or connect any model, local ones included. AI is optional, and each change it makes is a diff you can review and undo.
• Research tasks run a literature review, an evidence audit or a revision pass in a separate copy of the project while you keep writing, and you pick which changed files to keep.

Write together, live

Share a project to your lab's Oleafly Server and everyone edits the same files at once. You see each person's cursor and selection, who's online, and what changed while you were away. Click someone's avatar to jump to the line they're working on.

• Comment on any selection in LaTeX, Typst or Markdown, then reply, mention someone, resolve or reopen. A mentioned coauthor gets one email, and can turn those off.
• Edits you make offline merge when you reconnect. If they overlap with someone else's, Oleafly shows you both and asks before it applies anything.
• AI edits, Zotero citations, renames, deletes and figures all travel too. If two people replace the same figure at once, both versions are kept.
• The main file, compiler, spelling language and Typst options are shared, so the whole team compiles the project the same way.
• Each project has an owner, editors and viewers. Guests invited by email see only the projects they were invited to.

Run the server yourself

Oleafly Server installs with one command on a Linux machine, whether that's a lab workstation, a university VM or a small cloud server:

curl -fsSL https://oleafly.com/server/install.sh | sudo sh

It's a single Rust binary that uses SQLite, keeps files on disk or in any S3-compatible store, and sends email over SMTP if you set it up. People sign in with GitHub or any OpenID Connect provider, so your university's single sign-on works. There are ready-made configs for Docker Compose, Coolify, Render and systemd, and guides for Railway, Cloudflare Tunnel and university certificates.

Admins get a console in Oleafly for people, access rules, projects, email and the security log. Every device signs its changes, and the server builds each snapshot from that signed history instead of trusting uploads.

Read the server guide for setup, backups and the full list of who can do what.

Cloud sync across your computers

Turn on cloud sync and your library projects and app settings follow you from one computer to the next. Every download is checked against its record before it replaces a file, and a file you have open with unsaved changes is never overwritten.

• When two computers edit the same file, both versions are kept, each named after the computer that wrote it.
• Deleting most of a project at once puts it on hold until you confirm, so one bad move can't empty it everywhere.
• Files deleted on another computer go to the Trash here instead of vanishing.
• On a new computer, Oleafly asks once whether to keep this computer's settings or the synced ones.

Bring your projects with you

Moving from an online LaTeX editor? Sign in to your account once from Oleafly, pick the projects you want, and they come over with their files, compiler and main file, ready to compile. It works with a university's own server too.

With a Git token from that account, Oleafly can keep an imported project in sync both ways, so coauthors who stay online keep working the way they do now. Two-way sync uses the service's own Git integration, which needs a paid or university plan on the project owner's account.

You can also start from a project ZIP, a GitHub repository, a Word document, an arXiv source bundle, or a PDF that Oleafly rebuilds as editable LaTeX. Or open a folder where it already is.

AI agents that work inside your project

Pick an agent from the catalog and it works in your project with the source,