Choose a harness and a driving model, connect your own local Claude Code CLI as the prover, and send a statement straight from here.
Leak’s main strength is the strength of its tools — see the Leak services. Be sure to connect context-rich tools when using this harness for the best performance.
Prove-or-split: each goal gets a bounded direct attempt, then is broken into toolchain-verified sub-lemmas (recursively) and assembled into one sorry-free proof. Hacker mode leads with the compiler (verify_full_script) and strong automation. Needs a verify_full_script MCP server connected. Runs under a compute budget of 30 min that you can extend live (+5 min).
Prover activity
No activity yet — send a problem to the prover.
Universe
Every theorem in Tengoku is a star, every library a galaxy. Load the visualiser to watch Leak work in it: Leak I’s searches dim the field and light up what they find, and each step Leak IV verifies leaves a line of light between the lemmas it used. Send a statement above and the run plays out here live, or replay recorded runs.
about 7.5 MB, loaded only when you ask
This page is under construction; the write-up on Leak’s architecture and methodology is at /about/leak.
