bitpeek
  1. Bitpeek
  2. Tools
  3. Changelog

Bitpeek Version History & Release Notes

Chronological record of releases, architectural decisions, format additions, performance improvements, and breaking changes.

Open Bitpeek v1.0.0 Local processing notes

Version 1.0.0 (September 2026) — Initial Production Release

The complete realization of the Bitpeek Masterplan specification:

  • Structure Inspector: Added ELF32/ELF64 and PNG interactive parsers with bi-directional field-to-byte coordinate selection. Added support for custom declarative JSON structure schemas.
  • Pure TypeScript Core: Established packages/core with zero external dependencies, streaming ByteSource abstractions, and NIST-verified SHA-256 (FIPS 180-4).
  • CLI Executable: Introduced bitpeek CLI tool supporting 9 commands (inspect, find, strings, hash, structure, diff, patch verify, patch apply, recipe run) with JSON mode and POSIX exit codes.
  • Model Context Protocol (MCP) Server: Implemented official stdio MCP server in packages/mcp exposing 12 tools for AI agents within a secure allowed-roots sandbox.
  • Deterministic Replay Recipes: Added declarative recipe runner (recipe-v1.json) and verifiable evidence report generator (evidence-report-v1.json).
  • Integrity Fixes: Integrated SafeStorage in-memory fallback for private browsing, fixed 0-byte document export bug, eliminated draft state ambiguity, and unified transactional history across patch and replacement operations.
  • Documentation Suite: Launched 14 comprehensive technical documentation pages, machine-readable manifests (/capabilities.json, /version.json, /llms.txt), and versioned schemas.

Local processing and privacy

The Changelog 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

How is Bitpeek versioned?

Bitpeek strictly follows Semantic Versioning (SemVer 2.0.0). Schema specifications (such as recipe-v1.json) maintain independent version numbers.

Where can I see the commit history?

The complete, unedited commit history is publicly available on GitHub at github.com/Yudis-bit/bitpeek.