Codex Overleaf Link plugin
A Chrome extension adds a Codex panel to Overleaf: it reads the LaTeX project and edits it with tracked changes and undo.
- 111 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- In Auto mode Codex edits project files without asking before each edit
- The extension installs a Native Messaging host that runs the Codex CLI on your computer
Install
- Works in
Manual install
npm exec --yes codex-overleaf-link@2.6.5 -- install-managedThe Install with npm section. Then in `chrome://extensions` turn on developer mode and load the unpacked extension from the printed folder.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- In Auto mode Codex edits project files without asking before each edit
- The extension installs a Native Messaging host that runs the Codex CLI on your computer
This is third-party code. Review the repository files before installing.
What it does
Codex Overleaf Link places a panel next to the Overleaf editor where you can ask about the project or have Codex edit it. Three modes: Ask only reads and touches nothing, Auto reads and edits in Editing mode, Auto + Track writes changes as tracked ones so the Review panel looks like hand edits. The Accept changes and Undo changes buttons accept a run's edits or restore written files and remove created ones, also after a page reload. Context is added with `@` or a button, `@compile-log` can be attached to analyse a build error, lines like `main.tex:22-24` can be selected and the edit limited to the selection. Codex works on your computer through the Codex CLI: the extension syncs the project into a local mirror, starts `codex app-server`, compares the result with the baseline and writes patches through the editor. Deleting files and replacing images and PDFs always ask for confirmation.
Who it is for. Researchers and LaTeX authors in Overleaf who want to edit text and analyse build errors with Codex right in the editor.
Good fit when
- A paper section should be rewritten so the edits read as tracked changes.
- The build fails and the compile log is added to context.
- An edit should be limited to the selected lines of a file.
- A Codex run should be undone if the result is unsatisfactory.
Not a fit when
- The project is closed to external tools and its text must not go to a model.
- There is no Chrome or Chromium, Node.js 20 and an installed Codex CLI.
- Tracked changes are unavailable on the project owner's plan and untracked edits are not allowed.
Example request
Rewrite the introduction in main.tex shorter and tighter, make the edits tracked, then attach @compile-log and explain the error.Limitations
Chrome (or Chromium on Linux), Node.js 20 and an installed, signed-in Codex CLI are required. The extension is installed unpacked in developer mode and is not published to the Chrome store. Tracked changes depend on the Overleaf project owner's plan, and when unavailable the panel asks about writing without tracking. In Auto mode Codex does not ask before each edit, and undo stops at a file you edited again after the run. Context goes to Codex or to the provider you configured. The repository was last updated on 29 October 2026 and uses the MIT licence.
How to disable. Remove the extension in `chrome://extensions`, then the managed `~/.codex-overleaf/` folder with project mirrors and configuration. Session history sits in the Overleaf site IndexedDB and is deleted separately.
FAQ
How do Ask, Auto and Auto + Track differ?
Ask only reads, Auto reads and edits in Editing mode and Auto + Track writes changes as tracked changes.
How to undo a run?
With the Undo changes button: it restores written files and removes created ones but stops at a file edited later.
Where does Codex run?
On your computer through the Codex CLI. The extension syncs the project into a local mirror, starts `codex app-server` and writes patches through the editor.
Can another model provider be used?
Yes, experimentally: in Settings, Models & connections add a provider with an HTTPS address, key and model IDs.
What always requires confirmation?
Deleting files and adding or replacing images and PDFs, even in Auto mode.
Discussion
No questions or reviews yet.
Related
PluginsA skill and CLI olcli that edit Overleaf projects directly: precise replacements, uploads, PDF builds and a live edit session.
An Overleaf CLI that pulls LaTeX projects to a folder, pushes edits, compiles PDFs and exposes them to an agent through MCP
Aldine is a self-hosted LaTeX editor with collaboration and git, whose built-in MCP lets Claude edit and typeset a document.
An MCP server for Overleaf: the agent reads a LaTeX project over Git, finds sections and edits them with a commit
A LaTeX, Typst and Markdown editor with a local MCP server: an agent reads, edits and compiles the open project
Overleaf MCP Server: LaTeX projects over Git
Overleaf MCP Server (YounesBensafia)
An agent reads and edits Overleaf project files through standard Git sync and pushes the changes to the project itself
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Codex Overleaf Link (this card) | no | 111 | ||
| Overleaf Remote Skill | no | 120 | a skill and `olcli` CLI edit Overleaf projects directly from the command line; here a Codex panel inside the browser editor | |
| Overleaf MCP Server | no | API key | 357 | an MCP server reads the LaTeX project through Git and edits with a commit; here writing goes through the editor itself with tracked changes |
README in short
The README shows the panel next to the editor and PDF, covers modes and context, gives a data flow diagram and a table of storage locations on three systems.