Skip to main content
We are very proud to announce the release of Overleaf Pro 6.3.1, the most powerful and feature-rich online LaTeX editor in the community. A patch release usually means a handful of small fixes. This one goes much further: alongside dozens of bug fixes, it brings five new features, and it connects your projects to the places you already work, from Dropbox and GitLab to the AI agent in your terminal.

​
Changes

  • Dropbox Sync (early preview): keep every project in sync with your own Dropbox, in both directions.
  • GitLab Sync (early preview): two-way sync with GitLab.com or your self-managed GitLab.
  • MCP Server: let Claude Code, Codex, Cursor, VS Code or Gemini CLI work on a project directly.
  • GitHub Enterprise: point GitHub Sync at your own GitHub Enterprise instance.
  • Handwritten Symbol Recognition: draw a symbol, get the LaTeX command.
  • OVERLEAF_DISABLE_LOCAL_LOGIN: hide the email and password login so users sign in only with SSO.
  • Bug fixes found by our E2E testing system and Internal Horizon Issue Investigation.
  • Upstream Overleaf 6.3.1 patches.
Dropbox Sync and GitLab Sync ship in 6.3.1 as early previews for gray testing, and will be officially released in v6.4.0. Their configuration and behavior may still change before then. Both are off by default. Please report any issues on GitHub.

​
Feature 01: Dropbox Sync (Preview)

Some people never want to think about Git. They just want their thesis to be a folder on their laptop, and Dropbox Sync gives them exactly that. Each user links their own Dropbox account, and their owned and shared projects appear under Apps/<your app name>/. Edit in Overleaf and the change shows up in Dropbox. Edit the file locally in your favorite editor, save it, and the change comes back to Overleaf through a signed webhook. For admins: Git bridge must be enabled. Create an app in the Dropbox App Console, then set DROPBOX_ENABLED, DROPBOX_APP_KEY, DROPBOX_APP_SECRET, DROPBOX_APP_NAME and DROPBOX_TOKEN_CIPHER_PASSWORD. DROPBOX_SYNC_PROXY_URL is optional, for servers that can’t reach Dropbox directly. Then create the MongoDB indexes Dropbox Sync needs, once, before users link their accounts. See Dropbox Synchronisation for the full setup instructions.

​
Feature 02: GitLab Sync (Preview)

GitHub Sync has been one of our most loved features since 6.2, and many universities and companies keep their code on GitLab instead. GitLab Sync works the same way: link your account, import a repository from the new project menu, or export a project to a new GitLab project. Then push and pull from the editor, and merge through merge requests. It works with GitLab.com and with self-managed GitLab 15.10 or later. Set GITLAB_SYNC_ENABLED, GITLAB_SYNC_CLIENT_ID, GITLAB_SYNC_CLIENT_SECRET and GITLAB_TOKEN_CIPHER_PASSWORD, plus GITLAB_SYNC_URL for a self-managed instance. See GitLab Synchronisation for the full setup instructions. GitLab Sync

​
Feature 03: MCP Server

In 6.3 we put an AI assistant inside the editor. In 6.3.1 we open the door the other way: every project now has its own MCP server, so the AI agent you already use can work on your paper directly. Ask Claude Code to fix the typos in the introduction, ask Codex to compile and fix the LaTeX errors, or ask Cursor to answer the open review comments. The agent reads and edits files live, so you and your collaborators see its edits appear in the editor as it types. It can also compile, read the log, fetch the PDF, count words and list versions. The endpoint is /project/<project_id>/mcp. Authenticate with the same Git token you use for git clone. Access follows the project’s sharing settings, so a viewer’s agent can read but not edit, and every tool is rate limited. There is nothing else to configure: the MCP server is enabled together with Git bridge. MCP Server See MCP Server for how to connect each AI client.

​
Feature 04: GitHub Enterprise

GitHub Sync is no longer limited to github.com. Set GITHUB_SYNC_URL to your GitHub Enterprise Server, or to GitHub Enterprise Cloud with data residency (GHE.com), and the REST and GraphQL endpoints are derived from it. If your instance does something unusual, override them with GITHUB_SYNC_API_URL and GITHUB_SYNC_GRAPHQL_URL. Leave them unset and everything stays on github.com. See GitHub Synchronisation for details.

​
Feature 05: Handwritten Symbol Recognition

You know what the symbol looks like, but not what it’s called. Is it \varsigma or \zeta? \models or \vDash? Switch the symbol palette to draw mode, sketch it with your mouse or trackpad, and the palette suggests the matching LaTeX commands. Recognition runs entirely in the browser, with a model trained by ayaka-notes, so nothing you draw leaves your machine. The draw toggle is hidden on browsers without OffscreenCanvas (e.g. Safari 15). Handwritten Symbol Recognition

​
Bug fixes

This release also brings a long list of fixes. Many of them were found by our new E2E testing system, which now runs suites for every module daily, and by Internal Horizon Issue Investigation: every time we fix a bug, we sweep the whole codebase for its siblings before we close it.
  • Authentication: local accounts can set and change their password on SSO instances, and OIDC users can no longer change their own email. LDAP, SAML and OIDC logins no longer fail when a name attribute has several values, and SAML/OIDC logout works again.
  • Suspended users: suspending a user now ends their sessions and closes their open editors, and their Git tokens and MCP downloads are rejected.
  • GitHub Sync: only the owner can export a project, edits made while pulling stay pending, empty files are synced, and manual merges are verified on GitHub.
  • Zotero / Mendeley: you get a relink message when your credentials stop working, and references are reindexed after an import.
  • External services: requests to Zotero, Mendeley, GitHub, GitLab and web search get a 3s connect timeout instead of 1s, so slower networks no longer fail.
  • Track changes: review data includes unloaded documents and unsaved changes.
  • Admin panel: restoring deleted projects, changing owners and editing users work correctly, and a failed email no longer breaks account creation or deletion.
  • Template gallery: an invalid sort returns 400 instead of 500, and publishing a project without a main file asks for one.
See the 6.3.1 release notes for the full list.

​
Upgrade

  • From 6.3.0: no migration is needed. Pull the new image and restart.
  • From 6.2.x or earlier with Zotero or Mendeley in use: run the Zotero / Mendeley migration from 6.3.0 first.
  • Dropbox Sync and GitLab Sync are off by default. GitLab Sync only needs new environment variables. Dropbox Sync also needs its MongoDB indexes created once, before users link their accounts: see Create the database indexes.

​
Contributors

Thanks to @CPT-KK for the SSO password and OIDC email fixes (#112), and to @aruznieto for OVERLEAF_DISABLE_LOCAL_LOGIN.

​
Docker Image

You can find docker image here: https://github.com/ayaka-notes/ayakaleaf-pro/pkgs/container/overleaf-pro
Release date: 2026-10-15Bugfixes
  • Fixed the download-all link in the compile output.
  • Fixed errors related to anonymous edits.
  • Restored the suspend_users script, with a --reenable option to lift suspensions.
  • Fixed the logo misalignment when both the header image URL and a nav title are set.
  • Fixed the export-user-projects.mjs script.
Other changes
  • Updated internal dependencies.
Source: https://docs.overleaf.com/on-premises/release-notes/release-notes-6.x.x
Last modified on October 18, 2026