Declarative Binary Automation
Debugging binary issues often requires executing a series of precise steps: selecting a range, reversing endianness, verifying a checksum, applying an XOR mask, or checking a struct field.
Bitpeek Recipes codify these operations into a versioned, declarative JSON document (recipe-v1.json) that can be replayed deterministically across Web, CLI, and MCP environments.
Supported Recipe Operations
Version 1 of the Recipe Runner supports twelve pure algorithmic operations:
inspect-scalar: Decodes unsigned/signed integers or floats at specified offsets.reverse: Reverses byte order across the selected range.invert: Flips all bits across the selection.xor-mask: Applies a repeating byte mask across selected bytes.fill: Fills the selected range with a constant byte value (0..255).byteswap: Swaps endianness in 2, 4, or 8-byte word groupings.find-pattern: Searches for exact or wildcard byte patterns.extract-strings: Scans for printable ASCII or UTF-16 text.compute-hash: Calculates SHA-256, CRC-32, or CRC-16 checksums.inspect-structure: Parses ELF, PNG, or custom schema hierarchies.diff: Compares working bytes against a secondary reference input.apply-patch: Atomically applies a verified offset patch.
Expected Outputs & Dry-Run Mode
Each recipe step can declare expectedOutputs containing assertion checks (such as expected SHA-256 hash or scalar values). If any check fails, execution halts with an explicit error code.
In dry-run mode (--dry-run), the recipe engine executes all steps in memory and returns the complete result report without writing any files to disk.
Local processing and privacy
The Recipes workflow opens the same Bitpeek browser workspace. Selected file bytes, file names, pasted input, searches, edits, hashes, and comparison data are processed in local browser memory and are not sent to a Bitpeek server.
The static guide itself can be read without opening a file or creating an account.
Frequently asked questions
Does a recipe embed the binary file inside the JSON?
No. Recipes separate code from data; inputs specify file IDs, expected byte lengths, and SHA-256 fingerprints to ensure correct input binding.
Can recipes run arbitrary JavaScript or shell scripts?
No. Recipes are strictly declarative JSON specifications executed by the sandboxed Bitpeek core. No arbitrary code execution is permitted.