Add real-time co-editing with Overleaf
Maintainers usually reply within 1 day
@prajwal-svm is already working on this.
Since Nov 15, 2026.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- latex, typescript
- Domain
- desktop-dev, networking
Research direction
Start with the existing Git-based sync described in the v0.4.7 release, then read Lattice's Overleaf protocol notes to see how it authenticates through a signed-in web session and exchanges live edits. The issue names no source files, so locate the Overleaf import and file-sync code before designing anything. Done means two-way text edits on an open .tex file, simultaneous edits, and reconnecting without losing local changes. The first step is a design discussion with maintainers, not a patch.
Written by the indexing model from the issue text.
Description
I’d like to edit a shared Overleaf project in Oleafly while my coauthors keep using the Overleaf web editor. When we open the same .tex file, edits from either side should appear in the other editor as we type.
Oleafly already imports Overleaf projects and syncs files through Git. Live editing would let us work on the same section together without waiting for the next sync. Current sync workflow
A first version could focus on two-way text edits in the open document, including simultaneous edits and reconnecting without losing local changes. Lattice is a reference for this workflow. It connects to Overleaf’s live editing protocol through a signed-in web session and does not require a Git token. Lattice integration · Protocol notes
- Dominant language
- TypeScript
- Stars
- 838
- Forks
- 50
- Avg merge
- 17h 11m
- Merged PRs (30d)
- 75
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Oleafly/Oleafly
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day