Guides · 5 min read

Reverse engineering with a local model

Decompile binaries, read firmware and pick apart Android apps with Ghidra, IDA Pro, Binary Ninja, radare2 or JADX and a model on your own machine.

Reverse engineering means working out how software works without its source code: a binary, a firmware image, a file format, a network protocol or an Android app. A local model helps by turning assembly into readable code, naming functions and variables, and answering questions about what the code does. Running it on your own machine matters more here than almost anywhere else: the files you study are often confidential, under NDA or malicious, and should not be uploaded anywhere. Only analyse software you are allowed to.

Pick a host app and a plugin

Keep the reverse-engineering tool you already use and add a plugin that talks to your local model. The apps page lists each one.

Host appChat and explainAgent over MCP
Ghidra (free)GhidrAssist, OGhidraGhidraMCP, ReVa
IDA Pro (paid)GepettoIDA Pro MCP
Binary Ninja (paid)BinAssist—
radare2 (free)r2ai and decai—
JADX (free, Android)—JADX AI MCP

The MCP plugins don’t include a chat window. Connect them to an MCP client that runs local models, such as LM Studio or Jan.

Pick a model

Expectations

Models still invent function names and misread tricky code, and obfuscated or packed binaries confuse them, just as they confuse people. Treat the output as a fast first draft, check it against the disassembly, and keep notes in the tool rather than in the chat.

Was this guide useful?

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.