morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #7041] feat(binary-ninja-headless): add owned headless Binary Ninja provider #7600

New issue
Open
opened 2026-11-03 13:39:02 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-03 13:39:02 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7041
Author: @ihabontop
Created: 10/24/2026
Status: 🔄 Open

Base: main ← Head: feat/binary-ninja-headless

📝 Commits (1)

  • d4deddf feat(binary-ninja-headless): add owned headless Binary Ninja provider

📊 Changes

30 files changed (+5300 additions, -12 deletions)

View changed files

➕ bridge/binaryninja/rea_binaryninja_bridge.py (+858 -0)
➕ bridge/binaryninja/test_rea_binaryninja_bridge.py (+389 -0)
📝 docs/.vitepress/config.ts (+4 -0)
📝 docs/architecture.mermaid (+7 -0)
➕ docs/binaryninja-headless-provider.md (+90 -0)
📝 docs/index.md (+1 -1)
📝 docs/installation.md (+7 -7)
📝 docs/mcp-contracts.md (+1 -0)
📝 docs/testing.md (+37 -0)
📝 package.json (+2 -1)
📝 scripts/lib/catalog-builders.mjs (+9 -0)
📝 scripts/lib/catalog-core.mjs (+2 -0)
📝 scripts/lib/module-boundaries.mjs (+1 -0)
📝 scripts/lib/test-projects.mjs (+1 -1)
➕ src/binaryNinjaHeadless/BinaryNinjaHeadlessBridgeProcess.ts (+464 -0)
➕ src/binaryNinjaHeadless/BinaryNinjaHeadlessInstallation.ts (+184 -0)
➕ src/binaryNinjaHeadless/BinaryNinjaHeadlessOperationRunner.ts (+483 -0)
➕ src/binaryNinjaHeadless/BinaryNinjaHeadlessProtocolValues.ts (+455 -0)
➕ src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.test.ts (+327 -0)
➕ src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.ts (+288 -0)

...and 10 more files

📄 Description

Summary

Adds binary-ninja-headless, a deep-analysis provider that starts an owned headless Binary Ninja Python interpreter, loads the admitted file read-only after verifying its Raw-view digest, waits for default auto-analysis, and serves REA's native analysis operations from that BinaryView. Refs #1551. Draft for the maintainer scope decision CONTRIBUTING requires for a new provider; it does not ask for integration yet.

It complements the attached GUI MCP adapter proposed in #5794: that adapter reads a file the analyst already opened in the GUI; this provider needs no GUI and reproduces analysis from the file alone, but requires a Binary Ninja license edition that permits headless use.

Problem and expected behavior

Binary Ninja users with a headless-capable license cannot point REA at Binary Ninja without keeping a GUI open. With this change, --provider binary-ninja-headless (or REA_ANALYSIS_PROVIDER / open_binary.provider_id) serves decompile, function, analyze, search, trace and the underlying native operations from an owned, digest-bound headless analysis, with the same Evidence and limitation reporting as the other providers.

Change and scope

  • src/binaryNinjaHeadless/: capabilities (identity, operations, limitations, effects), filesystem-only installation discovery, protocol values with zod schemas and projections to the shared REA shapes, an owned bridge process (NDJSON over stdio on spawnOwnedProviderProcess + ProviderProcessSupervisor, reply-size budget, startup deadline, cancellation stops the interpreter), an operation runner, a serial session client, and the AnalysisProviderCandidate.
  • bridge/binaryninja/rea_binaryninja_bridge.py: the Python side; one BinaryView per process, Binary Ninja log on stderr, requests validated and answered with stable error codes.
  • Configuration: BINARY_NINJA_INSTALL_DIR, REA_BINARY_NINJA_PYTHON, REA_BINARY_NINJA_STARTUP_TIMEOUT_MS (additive, optional).
  • Composition: registered in src/composition/binary.ts; catalog, module-boundary and test-project wiring.
  • Intentionally not included: list_segments (segment contract provenance is Hopper/Ghidra only), list_names, procedure_references, read_bytes, doctor integration, a real-provider verifier lane, engine-version commitment in the profile. These are listed in the guide as next steps.
  • Existing providers are unchanged.

Contribution scope: new provider; maintainer scope decision requested in #1551 (pending). No target execution, injection, mutation or protection recovery.

Contract and boundary impact

  • Semantic owner and earliest changed stage: new provider adapter src/binaryNinjaHeadless/ and bridge; application and contract layers unchanged.
  • Contribution scope fit and linked maintainer decision: pending in #1551.
  • CLI and MCP/tool-catalog contract: no new tools or schemas; the provider catalog gains one provider entry.
  • Provider, bridge, target-format, or platform compatibility: Binary Ninja 6.0 headless API; PE, ELF and thin Mach-O executables on x86, x86_64, arm, arm64, mips, powerpc, riscv; Windows bundled interpreter by default, explicit interpreter elsewhere.
  • Evidence, artifact, provenance, or reconstruction contract: observations carry cachePolicy: live, Binary Ninja provenance strings in body/classification/locals, reference kinds reported as unavailable with the observed category, and relationship coverage unknown (callers) / partial-or-complete (callees).
  • Target selection, authority, upstream behavior, and cleanup details: REA owns the interpreter process; Binary Ninja writes only its own user directory; close releases the view and stops the process; failed startups are not cached.
  • Generated metadata, package, or installation impact: package.json#files ships the bridge script; test:python runs its unit test; no installer changes.

Expected effects:

  • Read existing files or captured data.
  • Launch or attach to a process.
  • Inject instrumentation or run scripts/code.
  • Change process memory, registers, files, or configuration.
  • Contact network services.
  • Recover protected code or work around protections.
  • Documentation or usability only; no target interaction.
  • Not sure yet; investigation or maintainer guidance needed.

Evidence and regression coverage

  • Tests added or updated: src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.test.ts (availability, target support, profile binding), src/binaryNinjaHeadless/BinaryNinjaHeadlessSessionClient.test.ts (launch contract, projections against functionDossierSchema and instruction windows, caller mistakes, startup failure attribution, deadline, cancellation, protocol faults, reply bounds, close) with tests/fixtures/fakeBinaryNinjaBridge.mjs; bridge/binaryninja/test_rea_binaryninja_bridge.py with a fake binaryninja module.

  • Base reproduction or other evidence: real-engine run recorded in docs/testing.md#binary-ninja-headless-lane (Windows 11 x64, Binary Ninja 6.0.10905, where.exe).

  • User-visible CLI/MCP output: rea decompile 'C:\Windows\System32\where.exe' --procedure __wmainCRTStartup --provider binary-ninja-headless --json returns Pseudo C Evidence with provider binary-ninja-headless, profile mode owned-headless, and raw engine facts (core_version 6.0.10905).

  • Remaining proof gaps: MCP parity, Linux and macOS hosts, ELF and Mach-O targets, other Binary Ninja releases and license editions, cancellation against the real engine, token/CPU/memory measurements.

  • Observed, derived, and inferred claims remain distinguishable.

  • Artifact identity, source provenance, and failed attempts remain preserved.

  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm run check:fast — passed (typecheck and lint, 2 tasks successful).
  • npm run test:local -- src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.test.ts src/binaryNinjaHeadless/BinaryNinjaHeadlessSessionClient.test.ts src/config.test.ts — 111 tests passed.
  • python -m unittest bridge/binaryninja/test_rea_binaryninja_bridge.py (CPython 3.14) — 10 tests passed.
  • Production CLI against real Binary Ninja 6.0.10905 on Windows 11 x64 with where.exe: decompile, function --detail complete, analyze, search --pattern 'cannot be run', trace --query 'cannot be run' — all exit 0; every output parsed against the built Evidence schema and its output contract; dossier parsed against functionDossierSchema.

Compatibility, safety, and release

  • Breaking changes or migration steps: none; all settings are new and optional.
  • Real Hopper/Ghidra, browser, or OS coverage: existing providers untouched; real Binary Ninja coverage limited to one Windows host.
  • Package or release metadata impact: one new packaged bridge script; one provider catalog entry.
  • Security, privacy, process, or containment review: the interpreter runs with the current user's permissions under REA's owned-process supervision, user plugins and settings disabled, no network use by REA; Binary Ninja's own license and user directory behavior is unchanged.

Author readiness

Human owner: @ihabontop

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7041 **Author:** [@ihabontop](https://github.com/ihabontop) **Created:** 10/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/binary-ninja-headless` --- ### 📝 Commits (1) - [`d4deddf`](https://github.com/morluto/rea/commit/d4deddf8a38de83919373084680806fa0f3281b4) feat(binary-ninja-headless): add owned headless Binary Ninja provider ### 📊 Changes **30 files changed** (+5300 additions, -12 deletions) <details> <summary>View changed files</summary> ➕ `bridge/binaryninja/rea_binaryninja_bridge.py` (+858 -0) ➕ `bridge/binaryninja/test_rea_binaryninja_bridge.py` (+389 -0) 📝 `docs/.vitepress/config.ts` (+4 -0) 📝 `docs/architecture.mermaid` (+7 -0) ➕ `docs/binaryninja-headless-provider.md` (+90 -0) 📝 `docs/index.md` (+1 -1) 📝 `docs/installation.md` (+7 -7) 📝 `docs/mcp-contracts.md` (+1 -0) 📝 `docs/testing.md` (+37 -0) 📝 `package.json` (+2 -1) 📝 `scripts/lib/catalog-builders.mjs` (+9 -0) 📝 `scripts/lib/catalog-core.mjs` (+2 -0) 📝 `scripts/lib/module-boundaries.mjs` (+1 -0) 📝 `scripts/lib/test-projects.mjs` (+1 -1) ➕ `src/binaryNinjaHeadless/BinaryNinjaHeadlessBridgeProcess.ts` (+464 -0) ➕ `src/binaryNinjaHeadless/BinaryNinjaHeadlessInstallation.ts` (+184 -0) ➕ `src/binaryNinjaHeadless/BinaryNinjaHeadlessOperationRunner.ts` (+483 -0) ➕ `src/binaryNinjaHeadless/BinaryNinjaHeadlessProtocolValues.ts` (+455 -0) ➕ `src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.test.ts` (+327 -0) ➕ `src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.ts` (+288 -0) _...and 10 more files_ </details> ### 📄 Description ## Summary Adds `binary-ninja-headless`, a deep-analysis provider that starts an owned headless Binary Ninja Python interpreter, loads the admitted file read-only after verifying its Raw-view digest, waits for default auto-analysis, and serves REA's native analysis operations from that BinaryView. Refs #1551. Draft for the maintainer scope decision CONTRIBUTING requires for a new provider; it does not ask for integration yet. It complements the attached GUI MCP adapter proposed in #5794: that adapter reads a file the analyst already opened in the GUI; this provider needs no GUI and reproduces analysis from the file alone, but requires a Binary Ninja license edition that permits headless use. ## Problem and expected behavior Binary Ninja users with a headless-capable license cannot point REA at Binary Ninja without keeping a GUI open. With this change, `--provider binary-ninja-headless` (or `REA_ANALYSIS_PROVIDER` / `open_binary.provider_id`) serves `decompile`, `function`, `analyze`, `search`, `trace` and the underlying native operations from an owned, digest-bound headless analysis, with the same Evidence and limitation reporting as the other providers. ## Change and scope - `src/binaryNinjaHeadless/`: capabilities (identity, operations, limitations, effects), filesystem-only installation discovery, protocol values with zod schemas and projections to the shared REA shapes, an owned bridge process (NDJSON over stdio on `spawnOwnedProviderProcess` + `ProviderProcessSupervisor`, reply-size budget, startup deadline, cancellation stops the interpreter), an operation runner, a serial session client, and the `AnalysisProviderCandidate`. - `bridge/binaryninja/rea_binaryninja_bridge.py`: the Python side; one BinaryView per process, Binary Ninja log on stderr, requests validated and answered with stable error codes. - Configuration: `BINARY_NINJA_INSTALL_DIR`, `REA_BINARY_NINJA_PYTHON`, `REA_BINARY_NINJA_STARTUP_TIMEOUT_MS` (additive, optional). - Composition: registered in `src/composition/binary.ts`; catalog, module-boundary and test-project wiring. - Intentionally not included: `list_segments` (segment contract provenance is Hopper/Ghidra only), `list_names`, `procedure_references`, `read_bytes`, doctor integration, a real-provider verifier lane, engine-version commitment in the profile. These are listed in the guide as next steps. - Existing providers are unchanged. Contribution scope: new provider; maintainer scope decision requested in #1551 (pending). No target execution, injection, mutation or protection recovery. ## Contract and boundary impact - Semantic owner and earliest changed stage: new provider adapter `src/binaryNinjaHeadless/` and bridge; application and contract layers unchanged. - Contribution scope fit and linked maintainer decision: pending in #1551. - CLI and MCP/tool-catalog contract: no new tools or schemas; the provider catalog gains one provider entry. - Provider, bridge, target-format, or platform compatibility: Binary Ninja 6.0 headless API; PE, ELF and thin Mach-O executables on x86, x86_64, arm, arm64, mips, powerpc, riscv; Windows bundled interpreter by default, explicit interpreter elsewhere. - Evidence, artifact, provenance, or reconstruction contract: observations carry `cachePolicy: live`, Binary Ninja provenance strings in body/classification/locals, reference kinds reported as unavailable with the observed category, and relationship coverage unknown (callers) / partial-or-complete (callees). - Target selection, authority, upstream behavior, and cleanup details: REA owns the interpreter process; Binary Ninja writes only its own user directory; close releases the view and stops the process; failed startups are not cached. - Generated metadata, package, or installation impact: `package.json#files` ships the bridge script; `test:python` runs its unit test; no installer changes. Expected effects: - [x] Read existing files or captured data. - [x] Launch or attach to a process. - [ ] Inject instrumentation or run scripts/code. - [ ] Change process memory, registers, files, or configuration. - [ ] Contact network services. - [ ] Recover protected code or work around protections. - [ ] Documentation or usability only; no target interaction. - [ ] Not sure yet; investigation or maintainer guidance needed. ## Evidence and regression coverage - Tests added or updated: `src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.test.ts` (availability, target support, profile binding), `src/binaryNinjaHeadless/BinaryNinjaHeadlessSessionClient.test.ts` (launch contract, projections against `functionDossierSchema` and instruction windows, caller mistakes, startup failure attribution, deadline, cancellation, protocol faults, reply bounds, close) with `tests/fixtures/fakeBinaryNinjaBridge.mjs`; `bridge/binaryninja/test_rea_binaryninja_bridge.py` with a fake `binaryninja` module. - Base reproduction or other evidence: real-engine run recorded in `docs/testing.md#binary-ninja-headless-lane` (Windows 11 x64, Binary Ninja 6.0.10905, `where.exe`). - User-visible CLI/MCP output: `rea decompile 'C:\Windows\System32\where.exe' --procedure __wmainCRTStartup --provider binary-ninja-headless --json` returns Pseudo C Evidence with provider `binary-ninja-headless`, profile mode `owned-headless`, and raw engine facts (`core_version` 6.0.10905). - Remaining proof gaps: MCP parity, Linux and macOS hosts, ELF and Mach-O targets, other Binary Ninja releases and license editions, cancellation against the real engine, token/CPU/memory measurements. - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm run check:fast` — passed (typecheck and lint, 2 tasks successful). - `npm run test:local -- src/binaryNinjaHeadless/BinaryNinjaHeadlessProvider.test.ts src/binaryNinjaHeadless/BinaryNinjaHeadlessSessionClient.test.ts src/config.test.ts` — 111 tests passed. - `python -m unittest bridge/binaryninja/test_rea_binaryninja_bridge.py` (CPython 3.14) — 10 tests passed. - Production CLI against real Binary Ninja 6.0.10905 on Windows 11 x64 with `where.exe`: `decompile`, `function --detail complete`, `analyze`, `search --pattern 'cannot be run'`, `trace --query 'cannot be run'` — all exit 0; every output parsed against the built Evidence schema and its output contract; dossier parsed against `functionDossierSchema`. ## Compatibility, safety, and release - Breaking changes or migration steps: none; all settings are new and optional. - Real Hopper/Ghidra, browser, or OS coverage: existing providers untouched; real Binary Ninja coverage limited to one Windows host. - Package or release metadata impact: one new packaged bridge script; one provider catalog entry. - Security, privacy, process, or containment review: the interpreter runs with the current user's permissions under REA's owned-process supervision, user plugins and settings disabled, no network use by REA; Binary Ninja's own license and user directory behavior is unchanged. ## Author readiness Human owner: @ihabontop - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7600
No description provided.