Skip to main content

Basic usage

That’s it. Kong opens the binary in Ghidra, runs the five-phase pipeline (triage → analysis → cleanup → synthesis → export), and writes results to ./kong_output/.
Kong TUI showing real-time analysis progress

TUI vs headless mode

By default, Kong runs with a terminal UI that shows real-time progress — current phase, function count, confidence distribution, and running cost. For CI pipelines, Docker containers, or environments without a terminal, use --headless:
Headless mode prints events to stdout instead of rendering the TUI.

Choosing a provider and model

Kong uses your default provider (set during kong setup). Override at runtime:
See LLM Providers for setup details.

Output control

Directory

Results go to ./kong_output by default. Override with --output:

Formats

Kong supports three output formats. The CLI default is source + json. Specify explicitly with -f:
See Output Formats for details on each.

Advanced flags

The --max-* flags are mainly useful for custom endpoints where local models may have smaller context windows.

Common workflows

What to expect

Analysis time and cost scale with function count and binary complexity: See the XZ Backdoor case study for a real-world example: 396 functions analyzed in 15 minutes for $6.63.

Further reading

Last modified on March 20, 2026