Lattice brings coding agents and Overleaf sync to local LaTeX writing

If you write academic papers, your desktop is probably a mess of reference managers, Overleaf tabs, local tex files, and a terminal running Claude Code to squash weird build errors. Constant app switching breaks focus fast.

Lattice wants to replace that fragmented workflow with a single local desktop workspace.

A local hub built around agents and sync

Lattice centers on local .tex files, packing one-click compilation, side-by-side PDF preview, bidirectional source-to-preview jumping, and error diagnostics directly into the editor. It pulls citations from arXiv, DOI, or BibTeX files, while keeping Markdown notes, whiteboards, and presentation slides in the same workspace.

Where it really stands out is collaboration and AI integration. Lattice features two-way sync with Overleaf, meaning you can work locally while your co-authors and advisors stay in their browser without changing habits.

It also hooks directly into coding agents like Claude Code and Codex. Agents can ingest the entire paper project, fix compilation errors, and refine text, letting you inspect every change through a built-in diff viewer.

Why it matters

The academic writing stack has been begging for an overhaul, but browser editors often struggle with deep AI agent integration. Lattice is smart not to try to kill Overleaf. Instead, it bridges the gap with two-way sync, giving you desktop speed and agentic automation without forcing collaborators onto a new platform.

We think this is a clever wedge into the researcher workflow. The real test will be how cleanly it handles sync conflicts when multiple people edit at once.