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 #4275] [CLOSED] fix(ghidra): report JVM heap exhaustion as a memory constraint #6152

New issue
Closed
opened 2026-10-31 01:12:16 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:12:16 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4275
Author: @RishTheFish21
Created: 10/15/2026
Status: ❌ Closed

Base: main ← Head: fix/4241-ghidra-heap

📝 Commits (2)

  • cd2ee37 fix(ghidra): report JVM heap exhaustion as a memory constraint
  • cf884f4 fix(ghidra): advise a larger heap only for heap exhaustion

📊 Changes

8 files changed (+362 additions, -7 deletions)

View changed files

📝 docs/installation.md (+14 -0)
📝 src/ghidra/GhidraDiagnostics.ts (+3 -0)
📝 src/ghidra/GhidraLauncher.ts (+33 -6)
➕ src/ghidra/GhidraMemoryExhaustion.test.ts (+90 -0)
➕ src/ghidra/GhidraMemoryExhaustion.ts (+93 -0)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+123 -1)
📝 src/ghidra/GhidraProviderClient.ts (+4 -0)
📝 tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts (+2 -0)

📄 Description

Summary

When Ghidra's JVM runs out of heap during import or analysis, REA reports a generic execution_failure that tells the caller to run rea doctor. Doctor reports Ghidra as healthy, so the advice leads nowhere. The real cause (java.lang.OutOfMemoryError: Java heap space) is only visible deep inside details.diagnostics.stdout.text.

Now, when a failed Ghidra session's own output shows a JVM OutOfMemoryError, REA reports resource_constraint with resource: "memory", the heap size it launched Ghidra with, and memory-specific remediation.

Fixes #4241

Problem and expected behavior

docs/binary-diagnostics.md says memory allocation failures use resource_constraint, with effective limits (or an explicit unknown) and memory-specific guidance. No Ghidra path recognized OutOfMemoryError, so every heap exhaustion was projected as ProviderAdapterError (execution_failure), or as a timeout if the deadline hit first.

Smallest trigger: any target large enough to exhaust a small heap, e.g. GHIDRA_HEADLESS_MAXMEM=128M rea inspect "$(command -v node)" --provider ghidra --json.

Change and scope

  • src/ghidra/GhidraMemoryExhaustion.ts: looks for java.lang.OutOfMemoryError (with its detail, e.g. "Java heap space") in the retained Ghidra process stdout/stderr. When found, the failure becomes AnalysisResourceConstraintError("memory"):
    • reported_limits.jvm_max_heap is the heap REA launched with, or null if unknown.
    • The remediation is to raise GHIDRA_HEADLESS_MAXMEM above that value or skip heavy analyzers with REA_GHIDRA_DISABLED_ANALYZERS, then reopen. It also notes that rea doctor doesn't check heap size.
    • It applies to start, process, protocol and timeout failures, after cancellation is handled. Bridge-reported (remote) failures and cancellations are unchanged.
  • The launcher records the selected heap on the launch, and diagnostics expose it as jvm_max_heap.
    • On macOS/Linux it's the last -Xmx actually passed to the JVM.
    • On Windows, the headless script picks the heap itself, so only an explicit GHIDRA_HEADLESS_MAXMEM/GHIDRA_MAXMEM is reported. Otherwise it stays unknown.
  • docs/installation.md: documents the new classification under "Ghidra heap and CPU controls".

Not included: the issue's second request (naming REA_GHIDRA_STARTUP_TIMEOUT_MS in startup-timeout remediation) and the optional "Untested Go version" limitation. Both touch different code paths, so I'd do them separately.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

Contract and boundary impact

  • Semantic owner and earliest changed stage: Ghidra session error projection (projectPrimarySessionError in src/ghidra/GhidraProviderClient.ts); launch diagnostics in GhidraLauncher.ts / GhidraDiagnostics.ts.
  • Contribution scope fit and linked maintainer decision: Bug fix within the existing Ghidra provider boundary. Maintainer decision not applicable.
  • CLI and MCP/tool-catalog contract: Ghidra heap exhaustion now returns the existing resource_constraint code instead of execution_failure/provider_timeout. No schema change.
  • Provider, bridge, target-format, or platform compatibility: Ghidra only. No bridge (Java) change. Windows reports the heap only when it's explicitly configured.
  • Evidence, artifact, provenance, or reconstruction contract: Error-path only. No Evidence or analysis-profile change.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable. Cleanup behavior is unchanged.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact (CI generates and validates ignored catalogs and skills/; edit authored instructions in .agents/skills/reverse-engineer-anything/ and never commit build outputs): None.

Expected effects (check known effects; use documentation-only on its own).
Unchecked items do not establish absence; leave uncertainties visible.

  • 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/ghidra/GhidraMemoryExhaustion.test.ts: reads OutOfMemoryError with and without detail from stdout and stderr; bounds long details; ignores mentions outside the process streams. Heap selection uses the last POSIX -Xmx, and Windows reports only explicit settings.
    • src/ghidra/GhidraProvider.behavior.test.ts: a process failure with heap exhaustion in stdout projects to resource_constraint with jvm_max_heap: "4G" and the new remediation. A timeout with GC overhead limit exceeded and no recorded heap reports jvm_max_heap: null. Failures without an OOM, and bridge-reported failures, are unchanged.
    • tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts: a real launch records jvmMaxHeap: "1G" and diagnostics expose it.
  • Base reproduction or other evidence: Real Ghidra 12.1.4 on macOS arm64, GHIDRA_HEADLESS_MAXMEM=128M rea inspect "$(command -v node)" --provider ghidra --json:
    • upstream/main: "code":"execution_failure". The only mention of the cause is buried in stdout diagnostics: OutOfMemoryError: Java heap space\n\tat java.base/java.lang.Long.valueOf(...).
    • this branch: "code":"resource_constraint", "jvm_max_heap":"128M", message Ghidra's JVM ran out of memory (java.lang.OutOfMemoryError: Java heap space) with a maximum heap of 128M.
  • User-visible CLI/MCP output (if applicable): see above.
  • Remaining proof gaps: Not run on Linux or Windows. I didn't reproduce the issue's Go/Hugo target or confirm that a larger heap lets it finish. An OutOfMemoryError printed earlier in a long session will classify a later process failure as memory too, since the classification reads the session's retained output.

For evidence-bearing changes:

  • 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 test:focused -- src/ghidra/GhidraMemoryExhaustion.test.ts src/ghidra/GhidraProvider.behavior.test.ts tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts: passed
  • npm run check:fast: passed
  • npm run lint: passed
  • npm run knip: passed
  • npm run docs:check: passed
  • Real Ghidra 12.1.4 before/after run on macOS arm64 (above): execution_failure → resource_constraint with jvm_max_heap: "128M"

Compatibility, safety, and release

  • Breaking changes or migration steps: Callers that matched execution_failure for Ghidra heap exhaustion now receive resource_constraint (resource: "memory"). Other failures are unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: Real Ghidra 12.1.4 on macOS arm64. Hopper is unaffected.
  • Package or release metadata impact: None.
  • Security, privacy, process, or containment review: Reads already-retained, already-redacted process output. No new process or target interaction.

Author readiness

Human owner: @RishTheFish21

  • 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.

🔄 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/4275 **Author:** [@RishTheFish21](https://github.com/RishTheFish21) **Created:** 10/15/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/4241-ghidra-heap` --- ### 📝 Commits (2) - [`cd2ee37`](https://github.com/morluto/rea/commit/cd2ee3785fae75567e084449dc3659653472b2b1) fix(ghidra): report JVM heap exhaustion as a memory constraint - [`cf884f4`](https://github.com/morluto/rea/commit/cf884f41efb17170b32d47a1f4b8c3846f91c3c3) fix(ghidra): advise a larger heap only for heap exhaustion ### 📊 Changes **8 files changed** (+362 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+14 -0) 📝 `src/ghidra/GhidraDiagnostics.ts` (+3 -0) 📝 `src/ghidra/GhidraLauncher.ts` (+33 -6) ➕ `src/ghidra/GhidraMemoryExhaustion.test.ts` (+90 -0) ➕ `src/ghidra/GhidraMemoryExhaustion.ts` (+93 -0) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+123 -1) 📝 `src/ghidra/GhidraProviderClient.ts` (+4 -0) 📝 `tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts` (+2 -0) </details> ### 📄 Description ## Summary When Ghidra's JVM runs out of heap during import or analysis, REA reports a generic `execution_failure` that tells the caller to run `rea doctor`. Doctor reports Ghidra as healthy, so the advice leads nowhere. The real cause (`java.lang.OutOfMemoryError: Java heap space`) is only visible deep inside `details.diagnostics.stdout.text`. Now, when a failed Ghidra session's own output shows a JVM `OutOfMemoryError`, REA reports `resource_constraint` with `resource: "memory"`, the heap size it launched Ghidra with, and memory-specific remediation. Fixes #4241 ## Problem and expected behavior `docs/binary-diagnostics.md` says memory allocation failures use `resource_constraint`, with effective limits (or an explicit unknown) and memory-specific guidance. No Ghidra path recognized `OutOfMemoryError`, so every heap exhaustion was projected as `ProviderAdapterError` (`execution_failure`), or as a timeout if the deadline hit first. Smallest trigger: any target large enough to exhaust a small heap, e.g. `GHIDRA_HEADLESS_MAXMEM=128M rea inspect "$(command -v node)" --provider ghidra --json`. ## Change and scope - `src/ghidra/GhidraMemoryExhaustion.ts`: looks for `java.lang.OutOfMemoryError` (with its detail, e.g. "Java heap space") in the retained Ghidra process stdout/stderr. When found, the failure becomes `AnalysisResourceConstraintError("memory")`: - `reported_limits.jvm_max_heap` is the heap REA launched with, or `null` if unknown. - The remediation is to raise `GHIDRA_HEADLESS_MAXMEM` above that value or skip heavy analyzers with `REA_GHIDRA_DISABLED_ANALYZERS`, then reopen. It also notes that `rea doctor` doesn't check heap size. - It applies to start, process, protocol and timeout failures, after cancellation is handled. Bridge-reported (`remote`) failures and cancellations are unchanged. - The launcher records the selected heap on the launch, and diagnostics expose it as `jvm_max_heap`. - On macOS/Linux it's the last `-Xmx` actually passed to the JVM. - On Windows, the headless script picks the heap itself, so only an explicit `GHIDRA_HEADLESS_MAXMEM`/`GHIDRA_MAXMEM` is reported. Otherwise it stays unknown. - `docs/installation.md`: documents the new classification under "Ghidra heap and CPU controls". Not included: the issue's second request (naming `REA_GHIDRA_STARTUP_TIMEOUT_MS` in startup-timeout remediation) and the optional "Untested Go version" limitation. Both touch different code paths, so I'd do them separately. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. ## Contract and boundary impact - Semantic owner and earliest changed stage: Ghidra session error projection (`projectPrimarySessionError` in `src/ghidra/GhidraProviderClient.ts`); launch diagnostics in `GhidraLauncher.ts` / `GhidraDiagnostics.ts`. - Contribution scope fit and linked maintainer decision: Bug fix within the existing Ghidra provider boundary. Maintainer decision not applicable. - CLI and MCP/tool-catalog contract: Ghidra heap exhaustion now returns the existing `resource_constraint` code instead of `execution_failure`/`provider_timeout`. No schema change. - Provider, bridge, target-format, or platform compatibility: Ghidra only. No bridge (Java) change. Windows reports the heap only when it's explicitly configured. - Evidence, artifact, provenance, or reconstruction contract: Error-path only. No Evidence or analysis-profile change. - Target selection, authority, upstream behavior, and cleanup details (if applicable): Not applicable. Cleanup behavior is unchanged. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact (CI generates and validates ignored catalogs and `skills/`; edit authored instructions in `.agents/skills/reverse-engineer-anything/` and never commit build outputs): None. Expected effects (check known effects; use documentation-only on its own). Unchecked items do not establish absence; leave uncertainties visible. - [x] 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/ghidra/GhidraMemoryExhaustion.test.ts`: reads `OutOfMemoryError` with and without detail from stdout and stderr; bounds long details; ignores mentions outside the process streams. Heap selection uses the last POSIX `-Xmx`, and Windows reports only explicit settings. - `src/ghidra/GhidraProvider.behavior.test.ts`: a process failure with heap exhaustion in stdout projects to `resource_constraint` with `jvm_max_heap: "4G"` and the new remediation. A timeout with `GC overhead limit exceeded` and no recorded heap reports `jvm_max_heap: null`. Failures without an OOM, and bridge-reported failures, are unchanged. - `tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts`: a real launch records `jvmMaxHeap: "1G"` and diagnostics expose it. - Base reproduction or other evidence: Real Ghidra 12.1.4 on macOS arm64, `GHIDRA_HEADLESS_MAXMEM=128M rea inspect "$(command -v node)" --provider ghidra --json`: - upstream/main: `"code":"execution_failure"`. The only mention of the cause is buried in stdout diagnostics: `OutOfMemoryError: Java heap space\n\tat java.base/java.lang.Long.valueOf(...)`. - this branch: `"code":"resource_constraint"`, `"jvm_max_heap":"128M"`, message `Ghidra's JVM ran out of memory (java.lang.OutOfMemoryError: Java heap space) with a maximum heap of 128M.` - User-visible CLI/MCP output (if applicable): see above. - Remaining proof gaps: Not run on Linux or Windows. I didn't reproduce the issue's Go/Hugo target or confirm that a larger heap lets it finish. An `OutOfMemoryError` printed earlier in a long session will classify a later process failure as memory too, since the classification reads the session's retained output. For evidence-bearing changes: - [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 test:focused -- src/ghidra/GhidraMemoryExhaustion.test.ts src/ghidra/GhidraProvider.behavior.test.ts tests/boundary/providers/ghidra/ghidraJavaLaunch.test.ts`: passed - `npm run check:fast`: passed - `npm run lint`: passed - `npm run knip`: passed - `npm run docs:check`: passed - Real Ghidra 12.1.4 before/after run on macOS arm64 (above): `execution_failure` → `resource_constraint` with `jvm_max_heap: "128M"` ## Compatibility, safety, and release - Breaking changes or migration steps: Callers that matched `execution_failure` for Ghidra heap exhaustion now receive `resource_constraint` (`resource: "memory"`). Other failures are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: Real Ghidra 12.1.4 on macOS arm64. Hopper is unaffected. - Package or release metadata impact: None. - Security, privacy, process, or containment review: Reads already-retained, already-redacted process output. No new process or target interaction. ## Author readiness Human owner: @RishTheFish21 - [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 - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] 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. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:12:16 +00:00
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#6152
No description provided.