Written against the build you can download today.
Documentation
Start with the tutorial if you have just installed this; the rest is reference. All of it is kept true the same way: every function named in the scripting reference is bound in the engine and every binding is on that page, every option in the command-line reference came from the binary’s own help, and every block of output was captured from a real run. Documentation that quietly drifts is worse than none, because the reader cannot tell which half is wrong.
Start here
Klarion end to end, in one sitting.
Opening your first binary, reading what the analysis found and what it admits it could not, naming and typing your way through it, and every route to the same engine without the window. Written for somebody who already reverse engineers.
Getting started
- TutorialKlarion end to end, for somebody who already reverse engineers: opening a binary, reading what the analysis found, naming, types, patching, projects, and every way to reach the engine without the window.
- Command lineAll nineteen klarion-cli commands: what each one does, whether it runs analysis or only reads the file, and what it emits.
Automation
- ScriptingKlarion embeds Lua and imports into your own Python. Rename by pattern, walk every cross-reference, or produce exactly the report you need, from the application or headless.
- MCP serverTwenty-two tools over JSON-RPC on stdio, so an agent drives the analysis engine the way you drive the window.