meertex is a LaTeX editor for the whole life of a paper, from the call for papers to camera-ready. Each paper carries its venue, its deadlines with countdowns and every version you handed in. meertex checks that your citations exist, and reviewers see how each of their comments was addressed.
You write on your own computer, in VS Code, vim or together with an LLM agent. Every save reaches your coauthors within a second. They edit the same document in the browser, with live cursors and a PDF that compiles as they type. A command line tool and an API make all of it ready for your LLM workflow.
Free to use at meertex.com. Sign in with your email address, no password needed. There is also a desktop app for macOS, Windows and Linux. meertex is open source, and the README explains how to run it on your own server. It is part of the Meerverse, the family of meer* apps.
Tour
A narrated tour of the real app, filmed with a made-up demo account. Watch a save in vim reach a coauthor's browser, the reference check catch a citation that does not exist, and a review on the PDF.
How it works
GitHub keeps a project's code in one place, with its history, its releases and the reviews around it. meertex does the same for a paper and adds what only papers have: a venue, deadlines and a bibliography that has to hold up. There is nothing to commit or push. Every save reaches all your computers and every coauthor within a second.
Its files and coauthors together with its venue, every deadline and the outcome.
A normal folder on each of your computers that follows every edit, from you and from everyone else.
The server commits the paper to git while you write, so every earlier state is still there.
Comments on the text or right on the PDF, suggestions applied with one click and an email to everyone involved.
Submission, rebuttal, revision and camera-ready, kept for good with their PDFs. Any two compare as a PDF with every change marked.
A PDF two seconds after the last edit, spelling and grammar as you type, and every citation looked up at Crossref, DBLP and arXiv.
Every date in the venue's time zone, with countdowns, reminder emails and a question once it has passed.
A rejected paper goes to the next venue as a fork that keeps its files and links back.
Each paper is one live document. Your laptop, your desktop, every open browser tab and every coauthor see the same text. When two people type at the same time, both edits are kept.
Check it out on as many computers as you like. Edit it with any editor, or let an LLM agent write with you. meertex sends every save to the server.
Everyone's edits come together here. meertex keeps a history you can go back to, saves the versions you handed in and compiles the PDF.
Everyone's cursor with their name, LaTeX autocomplete, the PDF next to the text, and reviews that show how each comment was addressed.
Features
Next to its text, a paper has coauthors, a venue, deadlines, the versions you handed in, reviews and a bibliography that has to hold up. meertex looks after each of them.
meertex keeps the paper's folder on your computer in step with everyone
else's edits. Files that a coauthor deleted go to a trash folder, so nothing
is lost. The files LaTeX writes while it compiles, such as .aux
files and your local PDF, stay on your computer.
$ meertex checkout 2027-icse-green-llm $ meertex service install
The browser editor works on the same document as your checkout, with everyone's
cursor and name. Autocomplete knows LaTeX commands and environments, every
\label in the project, the keys of every .bib file and
the paths for \input and \includegraphics. Invite
people by email as editors, reviewers or viewers.
The PDF compiles two seconds after the last edit, with pdfLaTeX, XeLaTeX or LuaLaTeX. Errors and warnings show up in a list, and a click opens the right line. Click the PDF to jump to the source, or jump from the text to its spot in the PDF.
Conference, track, links, page limit, template and every date from abstract registration to camera-ready, in the venue's time zone (AoE by default). Countdowns turn amber two weeks out and red in the last three days. A deadline that moved says so.
Once a deadline is over, meertex asks what happened. “Did you hand it in?” freezes the submission version from the state at the deadline, even when you answer three days late. “Was it accepted?” sets the outcome, so all your accepted papers are one filter away.
Submission, rebuttal, Revision N and camera-ready are saved for good, with the compiled PDF, the source as a zip and the PDF you actually uploaded. Compare any two by lines, by words, or as a PDF with every change marked.
Language models make up citations that look right: a real author with a title
they never wrote, a DOI that belongs to another paper, a link that was never
there. meertex looks up every entry of your .bib files at doi.org,
Crossref, Semantic Scholar, DBLP, arXiv and Open Library, and opens every link.
It shows what does not match, with the publisher's value one click away, and it
finds retracted papers and preprints that have been published since.
On request, an LLM reads each cited abstract and says whether it backs the sentence that cites it. When you checked an entry yourself, mark it. The mark lives in the entry and breaks as soon as anyone changes it.
$ meertex refs 2027-icse-green-llm check
In the desktop app the editor has an agent panel, as a fourth column next to the PDF or under the text. Ask it to tighten a paragraph, fix a table or address a reviewer's comment, and it edits your checkout of the paper. Its changes reach the editor and your coauthors within a second, and the History keeps every one of them.
It knows which file you have open and which lines you selected. It edits the paper's files on its own and asks you before it runs a command or looks outside the paper's folder. It is the Claude Code of your computer with your own sign-in, or a local model in Ollama that never sends the paper anywhere.
A reviewer comments on a passage of text, or double-clicks the PDF and meertex finds the line. A suggestion carries new text that the authors apply with one click. When a comment is resolved, meertex shows how the text changed, and the reviewer accepts it or reopens the comment. Everyone involved gets an email.
Each coauthor sorts papers into their own folders. Names follow your pattern. Start from a publisher's template zip, such as ACM's acmart or IEEE's kit, and resubmit a rejected paper to the next venue as a copy that keeps its files.
Sign in at meertex.com with an emailed link or code, with no password to remember. Coauthors only need a browser. meertex is open source under the AGPL-3.0-or-later, so you can also run it on your own server.
Screenshots
Real screenshots of a running meertex with a made-up demo account. Open one to see it full size.
\cite completion lists every key of the paper's .bib
with its title, and the PDF on the right compiled a moment ago.
Get started
All you need is an email address. Your coauthors only need a browser.
Enter your email address and meertex mails you a link and a code. Either one signs you in, and your account is ready. Start your first paper in the browser right away, empty or from a publisher's template.
In a paper's settings, invite people by email as editors, reviewers or viewers. They get an email, sign in the same way and write in the browser. There is nothing to install.
To write in your own editor or with an agent, install the meertex command line
tool from PyPI. It
needs Python 3.11 or newer. meertex login mails you a code, and
meertex checkout puts the paper in ~/papers.
$ pip install meertex $ meertex login --server meertex.com $ meertex checkout 2027-icse-green-llm
meertex sync keeps every paper folder up to date while it runs.
On Linux and macOS, meertex service install runs it in the
background. On Windows, leave it running in a terminal window.
$ meertex service install # Linux, macOS $ meertex sync # Windows
meertex is open source, so you can also run it yourself, on a laptop with
Docker or on a server with Coolify. The README explains how. The command line
tool then signs in with meertex login --server and your server's
address.
The README covers running your own server and the layout of the code.
docs/DESIGN.md describes every field and command, and
docs/agent.md explains how an agent works with your papers.
Command line
Everything you do in the browser also works in a terminal, from the first checkout to the last review comment.
Papers, dates, questions, versions, changes and compiling, each paper addressed by its name. Every command can answer in JSON for agents.
$ meertex projects --outcome accepted $ meertex show 2027-icse-green-llm $ meertex diff 2027-icse-green-llm submission --word $ meertex compile 2027-icse-green-llm
Read the open comments together with the text they are about, answer them, apply suggestions and resolve, without leaving the terminal.
$ meertex threads 2027-icse-green-llm $ meertex reply 2027-icse-green-llm a1b2c3d4 "Done, see line 4." $ meertex apply 2027-icse-green-llm 9f8e7d6c $ meertex resolve 2027-icse-green-llm a1b2c3d4
The command line tool is a Python package on
PyPI. Every change
to it is published as a new version, and pip install --upgrade fetches it.
$ pip install meertex # or: uv tool install meertex $ pip install --upgrade meertex $ meertex --help
For agents
The meertex skill starts a paper from a call for papers. It uses the command line tool, so install that first. In the desktop app, an LLM agent then writes with you next to the text.
Paste a conference URL into your LLM agent, and the meertex-new-paper skill does the rest.
~/papers/<name>.$ mkdir -p $SKILLS/meertex-new-paper $ curl -o $SKILLS/meertex-new-paper/SKILL.md \ https://raw.githubusercontent.com/ribalba/meertex/main/skills/meertex-new-paper/SKILL.md
$SKILLS is the folder your agent loads its skills from. In a clone
of the repository, make install-skill links it instead.
The desktop app runs the LLM agent of your computer in a panel of the editor. The Agent tab of each paper walks you through the setup and checks it.
$ meertex checkout 2027-icse-green-llm $ meertex service install $ curl -fsSL https://claude.ai/install.sh | bash # or: ollama pull qwen3-coder
With Ollama the model runs on your computer, and the paper stays there. To answer quickly, a local model needs a graphics card.
Desktop app
The desktop app opens meertex.com in its own window, with its own icon in the dock and the task bar. It keeps you signed in apart from your browser and shows PDFs right in the app. It also brings the agent panel, which runs the LLM agent of your computer next to the text. Everything else is the same meertex, so most new features arrive without a new download.
Open the .dmg and drag meertex into Applications. Apple has not notarized the app yet, so macOS stops its first start. Allow it once under System Settings, Privacy & Security, "Open Anyway".
Run the installer. Windows does not know the publisher yet, so SmartScreen warns once. Choose "More info" and then "Run anyway".
The .deb for Debian and Ubuntu and the .rpm for Fedora install meertex with its menu entry, and the sign-in link in your mail opens the app. The AppImage runs without installing.
Every change to the app is built and published on
GitHub.
For your own server, start the app with MEERTEX_URL set to its
address, as
electron/README.md
explains.