Leakdown

Trust

Fixes for the problems people hit most.

Start with leakdown --doctor. It checks Node, Chromium, your AI CLI, mail and ffmpeg.

Common problems

Open a problem to see the fix.

The run stopped halfway

Your AI subscription likely hit its usage limit. Rerun the same command later; a ladder run from the same day picks up where it stopped.

--goal exited with 2

Nothing failed on your site. The run could not start: the URL was unreachable, the model stopped answering, or setup failed. Run leakdown --doctor.

There is only video.webm

ffmpeg is not installed. Install it and new sessions also save video.mp4. --doctor says whether it was found.

A flag seems to do nothing

Since 0.7.0 an unknown flag is an error, so check the exact spelling in Commands.

Prospects stop at "check your email"

Mail is not set up, so they cannot read the code. See Email walls.

A finding appears only once

It is marked unverified. Send the same persona again with --persona name,name,name.

Ctrl-C in a menu

It exits cleanly with status 130. Nothing is written.

--doctor says everything is fine but the run fails

The result is cached for a week. leakdown --doctor --force checks again, including a live call to your AI CLI.

"the brain is not answering"

Your AI CLI stopped replying, which is what a usage limit looks like. Wait for it to reset and rerun the same command; nothing is lost.

Report a bug

Open an issue on GitHub ↗ and include the version:

zsh
leakdown --versionleakdown 0.7.0
Ask the docsalpha
Open full page ↗

This is alpha. It does not write answers — it finds the paragraph of the docs that answers you and shows it word for word, or tells you the docs do not cover it. It can still pick the wrong paragraph, so check the page it links to before you rely on it.

Ask a question about the Leakdown CLI.

Answers are copied from the docs, never written. Type /help for commands.