REA 6.3.0 Released: Enhanced capture and contract format validation, with support for streaming JSON via CLI.

REA 6.3.0 Released: Enhanced capture and contract format validation, with support for streaming JSON via CLI.

1 month ago
duguying
42 views
Source: GitHub Releases

Reverse Engineering MCP Tool REA (Reverse Engineer Anything) releases rea-agents 6.3.0: This version includes 8 significant changes (tightening of capture and contract formats), approximately 70 bug fixes, and 3 performance optimizations. The command-line interface (CLI) has been updated to use a streaming approach for input and output, allowing it to handle documents of any length.

Related tags

#REA#逆向工程#MCP#开源

Overview of Release

REA (Reverse Engineer Anything) is a set of MCP tools specifically designed for reverse engineering. Its core purpose, as stated in one sentence, is: “To understand a desired functionality until the binary level.” It unifies the ability to inspect native binaries, JavaScript/Electron applications, .NET assemblies, Android APKs, firmware, websites, and runtime behavior using AI agents (Claude Code, Codex, Cursor, Gemini CLI, Grok Build, etc.), and can also be called directly from the terminal. Analysis is performed locally, with each conclusion accompanied by evidence and limitations. The project is open-source under the MIT license, and has over 60,000 GitHub stars in its README.

On October 9, 2026, REA released rea-agents 6.3.0. This is a substantial release: it includes 8 breaking changes (focused on the capture and contract data formats), 2 new features, approximately 70 bug fixes, 3 performance optimizations, and a number of improvements in refactoring, documentation, and testing. Given the high density of changes between 6.2.0 and 6.3.0, the official team specifically advises users to keep upgrading in the README.

Key Highlights

1. Breaking Changes: Tightened Capture and Contract Formats

The most significant change in this version is that certain data formats no longer “tolerate” default or synthetic values, affecting the following areas:

  • Captures: Missing historical producer accounting or transaction identifiers will be rejected; Web differences lacking accessibility or storage dimensions will also be rejected. The official recommendation is to retain original captures, re-collect with the current producer, and ensure that all dimensions are included in the comparison consumer (see the Process Capture Guide and the Browser Scenario Contract).
  • Browser: JSON shape paths now include properties and array element segments with types; the <code input_schema_shape> in WebMCP has been replaced by <code input_schema> and <code input_schema_sha256>, while preserving the declared examples and default values.
  • Processes: File system summaries omitting items must now provide a <code system_code>; budget and change files omitting items use <code null>; files with unavailable omissions retain the corresponding operating system error code.
  • Contracts: Provider analysis output must explicitly provide metadata that was previously patched with default values; nullable facets that are not supported must be reported as <code null>.
  • JavaScript: Semantic graph facts now store evidence context IDs and locations; diagrams and semantic tracking results require inline <code evidence_contexts> tables; simultaneously, <code truncated_scopes> statistics have been removed.
  • Native Analysis: Objective-C property markers now only contain names and values; attribute reports can be empty for atomic and read-only facts; class flags, ivar counts, and method requirements can be nullable when not observed.

2. New Features

  • Setup OMP registration (#1301): The setup process now includes OMP registration.
  • JavaScript: Electron Integrity Mismatch Recording: Electron application analysis now records cases where integrity checks fail, facilitating the determination of whether the analyzed output has been tampered with or is inconsistent with the declared specifications.

3. Key Fixes: CLI Streaming and Artifact Extraction

Approximately 70 fixes are distributed across multiple sub-systems, some of which are noteworthy:

  • JSON input/output in CLI no longer limited by total document length: New streaming JSON input and output (#1360, fixes

More News

Want to see more quality content?

Browse all news