Add real-time co-editing with Overleaf

Open
#458 1 comment 1 reaction 1 assignee View on GitHub

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

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

area/collaboration area/editor

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Oleafly/Oleafly

All issues in Oleafly/Oleafly

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.