Repository navigation
IDA Plugin
Carries your work from an old build's IDA database to a new build's: function names, prototypes, comments and local types, across the function mappings Permanent Beta accepted (by verification or a reviewer) only. Ambiguous, in-review and unmatched functions get nothing, and are listed. Full reference: integrations/ida/README.md.
Needs IDA Home or Pro 9.x with IDAPython (not IDA Free) and a pbeta build. Names have been checked in IDA Home 9.5;
prototypes and comments not yet.
Copy ida-plugin.json, permanent_beta_ida.py and the permanent_beta folder from integrations/ida into a folder
of their own, such as %APPDATA%\Hex-Rays\IDA Pro\plugins\permanent-beta, and restart IDA. It loads with each
database and adds Edit > Plugins > Permanent Beta.
- Analyze both builds:
pbeta analyze old.exe --out old.json, and the same for the new one. - In the old database: Edit > Plugins > Permanent Beta > Export markup... writes a
pbeta-markupJSON file of the names, prototypes, comments and local types you set. - In the new database: Apply markup from an older build... asks for
pbeta, the markup export, both analyses and, optionally, the review store. It runspbeta mappings --markupand asks before writing. - The results window lists each function as carried, kept, skipped or pending, with the reason.
Rules: each database must be its analysis's build (by SHA-256). Names and prototypes you already set in the new
database are kept. A prototype that doesn't fit the new function's register arguments isn't applied. Each carried
function gets a pbeta: comment naming the source build and who decided the mapping. Applying twice changes
nothing.
Hex-Rays' IDA MCP (IDA 9.4+, with idalib) and pbeta-mcp work together: pbeta-mcp gives the agent
the review queue and evidence, IDA MCP lets it read the code. Two things to know:
- In Claude Code's auto mode, IDA MCP's calls are refused. Use another permission mode.
- IDA MCP loads a build's PDB when it finds one, so the agent sees real names. Open copies of the binaries away from their PDBs to keep a review honest.
Setup for Claude Code:
claude plugin marketplace add HexRaysSA/claude-marketplace
claude plugin install ida-mcp@HexRaysSAthen add pbeta-mcp to .mcp.json as on MCP Server.
Permanent Beta is Apache-2.0. Found something wrong on this page? Open an issue.
Getting started
Using it
Integrations
Project