Skip to content
Ryan Cole edited this page Nov 15, 2026 · 3 revisions

permanent beta

Permanent Beta keeps function hooks working when the program they hook is rebuilt or updated.

A hook (Microsoft Detours, MinHook, …) patches a function at an address in one specific build. When the program is rebuilt, every address moves and the hooks break. pbeta finds each hooked function in the new build, verifies it's the same function, and rewrites your hook list with the new addresses. Anything it isn't sure about goes to a review queue instead of being guessed. The hook host, a generic hook DLL, then attaches your hooks in whichever build is running.

Windows PE binaries, x64 and x86 (32-bit), built with MSVC. Free and open source (Apache-2.0).

Start here

Page For
Installation Building pbeta, pbeta-mcp and the hook host from source
Quick Start The demo in two minutes, then your own program
How It Works Analysis, matching, verification, acceptance policy, outcomes

Using it

Page For
Hook Manifest The hooks.toml format
Review Queue Deciding what pbeta wouldn't
Hook Host Running your hooks in any build without hook plumbing
Behavioral Evidence Scenario traces and replaying recorded calls
CLI Reference Every pbeta command

Integrations

Page For
AI Proposer Asking Claude about functions matching left unmatched (opt-in)
MCP Server pbeta-mcp, for AI agents
Ghidra Integration Headless exporter and the review window
IDA Plugin Carrying names, prototypes and comments to a new build

Project

Page For
FAQ Common questions and rough edges
Contributing Building, testing, what a change needs

Principles

  • Wrong is worse than unknown. Ambiguity gives no answer, only a review item. A hook is never patched at a guessed address.
  • Matching proposes, verification judges. Every candidate, from any source, passes the same independent checks and acceptance policy.
  • Deterministic first. An AI model can propose candidates for leftovers; its proposals are verified and only ever queued for review.
  • Evidence is kept. Accepted mappings and review decisions are stored with their evidence, append-only.
  • Local by default. Nothing leaves the machine unless you opt in.

Legal

Only analyze and instrument software you have the right to. The project doesn't support, and won't accept contributions for, circumventing DRM, anti-tamper or anti-cheat protections: the analyzer refuses binaries that look packed or protected.

Clone this wiki locally