Write, explore, and improve Lean proofs in your browser with a Lemex assistant.
Developed by EPFL LARA.
- Start with Lean: use Mathlib Playground, import a Git repository, or upload your files.
- Explore proofs: edit alongside live goals, diagnostics, declaration search, and local Lean books.
- Ask Lemex: select a proof to complete, repair, or optimize, using models available with your own API key.
- Write LaTeX: edit documents beside their PDF with the optional TeX worker.
- Stay in control: review edits, steer separate chats, and commit or push your work.
If your imported repository has no Lean setup, choose a Lean version and libraries after import. LeanFlow adds the selected environment while keeping your existing files. Repositories with Lean configuration keep their pinned environment.
EPFL early access: Open LeanFlow from the EPFL network or VPN and sign in with EPFL. Existing token users should sign in with their token first, then choose Assistant settings → Link EPFL account once to keep their projects. For access help, contact lazar.milikic@epfl.ch.
Self-host LeanFlow Web for yourself or trusted collaborators on Linux with Node.js 24+, Python 3.11+, Git, and Docker. Setup uses a precompiled Lemex release; no Rust build is needed.
- Install: prepare the app and sign in.
- Host for a team: add persistent storage, a service, and an HTTPS address.
- Use LeanFlow Web: work with projects, proofs, and Lemex.
Each collaborator has an individual account and saves their own provider API key; EPFL RCP is the default. Instances can use invitation tokens or optional EPFL sign-in. Existing token users should link EPFL from Assistant settings to keep their projects. Before inviting a team, complete the short installation verification.
- Bugs and ideas: search existing issues before opening an issue. For bugs, include steps to reproduce, expected and actual behavior, and your browser and Lean version when relevant.
- Contribute: fork the repository, create a branch, and submit a focused pull request explaining the change and how you checked it. Discuss larger changes in an issue first.
- Security: report vulnerabilities privately using the security policy. Keep access tokens, API keys, and private project content out of issues and pull requests.
After setup, use npm run dev for development with your settings exported. See AGENTS.md for code practices, formatting, and checks.
See Configuration for advanced settings and Checks and releases for GitHub Actions.
Built on lean4web, lean4monaco, and the Lean infoview, with Lemex and LeanProbe.
Apache-2.0. See NOTICE for upstream attribution.