Repository navigation
FAQ
Windows x64 PE executables built with MSVC, including /O2, /Od, identical-code folding, /LTCG, PGO and debug
builds with incremental linking. ELF, ARM64 and 32-bit x86 aren't started.
No. Matching works on stripped binaries. With PDBs you get better matching, exact signature and struct-change proposals, argument decoding in the host's log, and much better replay.
Because the engine needs evidence independent of how it found the match, and a hook's criticality may require more than it has (How It Works). An unmatched-looking leaf function with no strings often needs one more check, such as a matched caller or a behavioral pass. Accept it yourself (Review Queue) or add Behavioral Evidence.
Because a wrong pick patches the wrong code. Identical candidates are always ambiguous; you decide.
Yes. The manifest is library-neutral. Use pbeta header to generate hooks.gen.h with each build's RVAs and
patterns, keyed by the exe's SHA-256, or read the repaired manifests yourself.
Not unless you run the AI Proposer with --allow-remote.
No. The analyzer refuses binaries that look packed or protected, and features for defeating integrity checks, anti-tamper or anti-cheat won't be accepted.
- Thresholds in the acceptance policy aren't calibrated yet (
[Guess]in the design doc). -
binddoesn't check that the manifest's RVAs belong to the build it binds to. - Replay needs both builds' PDBs for globals, models only a few imports, and the recorder's size limits are guesses.
Without the
emulatorfeature every case is inconclusive. - The hook host's thunk handles up to 12 parameters and no variadic functions. It can't attach to a running process.
Where things stand overall: docs/STATUS.md.
Permanent Beta is Apache-2.0. Found something wrong on this page? Open an issue.
Getting started
Using it
Integrations
Project