[PR #6991] fix(ghidra): bound bridge request lines above the authentication handshake #7554

New issue

Open

opened 2026-11-03 13:38:40 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented 2026-11-03 13:38:40 +00:00

Owner

Copy link

📋 Pull Request Information

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

Base: main ← Head: fix/ghidra-bridge-request-line-bound

---

📝 Commits (1)

• 480a720 fix(ghidra): bound bridge request lines above the authentication handshake

📊 Changes

4 files changed (+61 additions, -5 deletions)

View changed files

📝 bridge/ghidra/ReaGhidraBridge.java (+55 -1)
📝 docs/ghidra-provider.md (+4 -2)
📝 src/config/bridgeMaxRequestBytes.ts (+1 -1)
📝 tests/boundary/mcp/ghidraRequestCeilingMcp.test.ts (+1 -1)

📄 Description

Summary

The Ghidra bridge bounds its authentication frame at 64 KiB and then read every later request line with an unbounded BufferedReader.readLine(). Request lines are now read through a bounded helper that refuses a line above the configured ceiling and drops that connection, so the headless JVM no longer retains unbounded memory for a single request from any client.

The REA client already refuses its own oversized requests before writing, so what stayed unbounded was the retention path inside the bridge: an out-of-band client on the same machine, and every request arriving over the Unix-socket transport, where no bound existed even for the first one.

Problem and expected behavior

Smallest trigger: connect to a running bridge's socket and send a line longer than the ceiling without a newline.

Before this change, serveClient read with reader.readLine(), which grows until a newline or end of stream. The authentication handshake bounds its own frame and throws past that size, but the handshake result feeds only the first request on the loopback transport; every later line there, and every line on the Unix-socket path, arrived through the unbounded read. A client could keep the JVM allocating for exactly as long as it kept sending.

Expected behavior: the bridge retains at most one bounded request line, refuses a line above the ceiling the same way the handshake refuses an oversized frame, and closes that connection. Requests under the ceiling are byte-for-byte unchanged.

Change and scope

readBoundedLine replaces the single readLine() call in serveClient, which serves both transports. It reads one character at a time, returns the same line readLine would have produced, strips a trailing carriage return the way readLine does, and throws past an over-ceiling line so the connection closes through the existing try-with-resources.

The ceiling comes from REA_BRIDGE_MAX_REQUEST_BYTES in the bridge's environment, defaulting to 16 MiB when unset and clamping to the documented floor and maximum when set. The launch environment already passes a snapshot of REA's environment to the Ghidra process, so the shared setting reaches the bridge with no launcher change and both sides agree on one value. An out-of-band client that sets nothing gets the same 16 MiB default the client would.

The bound counts decoded characters rather than bytes. UTF-8 bytes are never fewer than characters, so a request the client admitted under its byte ceiling is never refused by the character count here. The client stays the exact enforcement point for the byte ceiling; the bridge bound is the retention limit for what the reader hands to the parser.

Deliberately left out: changing the handshake's own 64 KiB bound. That is shipped behavior on the loopback transport, and widening it is a separate decision about what a first request may carry. Also out of scope: replying with a correlated failure before dropping an over-ceiling connection. The line's id is not parsed at that point, so no correlated reply exists to send; the drop matches how the handshake already rejects an oversized frame without one.

Contract and boundary impact

• Semantic owner and earliest changed stage: bridge/ghidra/ReaGhidraBridge.java owns the bridge's socket protocol; the bound applies when a request line is read, before request parsing.
• Contribution scope fit and linked maintainer decision: routine fix inside an existing bridge boundary, no new provider, no target execution, injection, mutation, or protection recovery; not applicable.
• CLI and MCP/tool-catalog contract: none. No tool schema, description, or catalog change, and no TypeScript file is touched.
• Provider, bridge, target-format, or platform compatibility: Ghidra bridge on every platform, both transports. Requests under the ceiling behave identically, including carriage-return handling at end of line.
• Evidence, artifact, provenance, or reconstruction contract: none. Evidence content, provenance, and reconstruction output are untouched.
• Target selection, authority, upstream behavior, and cleanup details: not applicable.
• Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. No dependency, lockfile, catalog, or skill bundle change.

Expected effects (check known effects; use documentation-only on its own).

• 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: none. The repository carries no unit harness for the Java bridge sources; the CI lane compiles the packaged sources against a real Ghidra SDK, which is the available verification path for this file.
• Base reproduction or other evidence: source-derived only, and labeled as such. The unbounded read is visible at the single readLine() call site, and the handshake's own oversized-frame throw one read above shows the refusal shape the bridge already uses elsewhere. No runtime reproduction of the retention was executed.
• User-visible CLI/MCP output (if applicable): none for under-ceiling requests. An over-ceiling request now drops the connection where it previously retained the line; the connecting client sees its socket close.
• Remaining proof gaps: the bounded read has not executed against a live Ghidra bridge, and the compile itself happened only in CI. Runtime verification needs a bridge session, which maintainers or a follow-up with a Ghidra installation can provide.

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

This checkout has no JDK and repository policy keeps Ghidra bring-your-own, so no local command could compile or execute a Java change. What was done instead:

• Verified at the source level that exactly one unbounded read existed, that it served both transports, and that the replacement returns the same line content for any line under the ceiling, including carriage-return handling.
• Confirmed the launch environment passes REA's process environment to the Ghidra process, so the shared REA_BRIDGE_MAX_REQUEST_BYTES setting reaches the bridge without a launcher change.
• gh pr and issue searches across open and closed states found no existing claim on this boundary.
• The ghidra-bridge CI lane compiles the packaged bridge sources against a checksum-verified Ghidra SDK and is the verification path for this revision; it triggers on changes under bridge/ghidra/.

Compatibility, safety, and release

• Breaking changes or migration steps: none. A request under the ceiling produces the identical line; an over-ceiling request previously retained unbounded memory and now drops the connection. No ! marker is needed.
• Real Hopper/Ghidra, browser, or OS coverage: not run locally. The CI lane compiles the packaged sources, and runtime behavior of the bound needs a live bridge session.
• Package or release metadata impact: none. No dependency, lockfile, catalog, or skill bundle change.
• Security, privacy, process, or containment review: the change bounds one client-controlled retention path inside the bridge JVM and adds no new input path, no new network path, and no credential handling. The ceiling arrives through the process environment as a size setting; session tokens keep traveling through the private session descriptor and are not placed in the environment.

Author readiness

Human owner: @DeryFerd

• 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. The Java bridge has no unit harness in this repository; the CI compile lane and the unchanged under-ceiling behavior are the coverage, with the gap stated above.
• Owning docs, contracts, and generated metadata are updated where needed. No owning document describes the bridge's read loop, and no ceiling setting or contract changes.
• User-visible CLI/MCP changes include representative output. There is no output change for under-ceiling requests; the over-ceiling drop is described under Evidence.
• 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/6991 **Author:** [@DeryFerd](https://github.com/DeryFerd) **Created:** 10/24/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/ghidra-bridge-request-line-bound` --- ### 📝 Commits (1) - [`480a720`](https://github.com/morluto/rea/commit/480a72071b9254816742c55b37103dd01bc5d065) fix(ghidra): bound bridge request lines above the authentication handshake ### 📊 Changes **4 files changed** (+61 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `bridge/ghidra/ReaGhidraBridge.java` (+55 -1) 📝 `docs/ghidra-provider.md` (+4 -2) 📝 `src/config/bridgeMaxRequestBytes.ts` (+1 -1) 📝 `tests/boundary/mcp/ghidraRequestCeilingMcp.test.ts` (+1 -1) </details> ### 📄 Description ## Summary The Ghidra bridge bounds its authentication frame at 64 KiB and then read every later request line with an unbounded `BufferedReader.readLine()`. Request lines are now read through a bounded helper that refuses a line above the configured ceiling and drops that connection, so the headless JVM no longer retains unbounded memory for a single request from any client. The REA client already refuses its own oversized requests before writing, so what stayed unbounded was the retention path inside the bridge: an out-of-band client on the same machine, and every request arriving over the Unix-socket transport, where no bound existed even for the first one. ## Problem and expected behavior Smallest trigger: connect to a running bridge's socket and send a line longer than the ceiling without a newline. Before this change, `serveClient` read with `reader.readLine()`, which grows until a newline or end of stream. The authentication handshake bounds its own frame and throws past that size, but the handshake result feeds only the first request on the loopback transport; every later line there, and every line on the Unix-socket path, arrived through the unbounded read. A client could keep the JVM allocating for exactly as long as it kept sending. Expected behavior: the bridge retains at most one bounded request line, refuses a line above the ceiling the same way the handshake refuses an oversized frame, and closes that connection. Requests under the ceiling are byte-for-byte unchanged. ## Change and scope `readBoundedLine` replaces the single `readLine()` call in `serveClient`, which serves both transports. It reads one character at a time, returns the same line `readLine` would have produced, strips a trailing carriage return the way `readLine` does, and throws past an over-ceiling line so the connection closes through the existing try-with-resources. The ceiling comes from `REA_BRIDGE_MAX_REQUEST_BYTES` in the bridge's environment, defaulting to 16 MiB when unset and clamping to the documented floor and maximum when set. The launch environment already passes a snapshot of REA's environment to the Ghidra process, so the shared setting reaches the bridge with no launcher change and both sides agree on one value. An out-of-band client that sets nothing gets the same 16 MiB default the client would. The bound counts decoded characters rather than bytes. UTF-8 bytes are never fewer than characters, so a request the client admitted under its byte ceiling is never refused by the character count here. The client stays the exact enforcement point for the byte ceiling; the bridge bound is the retention limit for what the reader hands to the parser. Deliberately left out: changing the handshake's own 64 KiB bound. That is shipped behavior on the loopback transport, and widening it is a separate decision about what a first request may carry. Also out of scope: replying with a correlated failure before dropping an over-ceiling connection. The line's id is not parsed at that point, so no correlated reply exists to send; the drop matches how the handshake already rejects an oversized frame without one. ## Contract and boundary impact - Semantic owner and earliest changed stage: `bridge/ghidra/ReaGhidraBridge.java` owns the bridge's socket protocol; the bound applies when a request line is read, before request parsing. - Contribution scope fit and linked maintainer decision: routine fix inside an existing bridge boundary, no new provider, no target execution, injection, mutation, or protection recovery; not applicable. - CLI and MCP/tool-catalog contract: none. No tool schema, description, or catalog change, and no TypeScript file is touched. - Provider, bridge, target-format, or platform compatibility: Ghidra bridge on every platform, both transports. Requests under the ceiling behave identically, including carriage-return handling at end of line. - Evidence, artifact, provenance, or reconstruction contract: none. Evidence content, provenance, and reconstruction output are untouched. - Target selection, authority, upstream behavior, and cleanup details: not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. No dependency, lockfile, catalog, or skill bundle change. Expected effects (check known effects; use documentation-only on its own). - [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: none. The repository carries no unit harness for the Java bridge sources; the CI lane compiles the packaged sources against a real Ghidra SDK, which is the available verification path for this file. - Base reproduction or other evidence: source-derived only, and labeled as such. The unbounded read is visible at the single `readLine()` call site, and the handshake's own oversized-frame throw one read above shows the refusal shape the bridge already uses elsewhere. No runtime reproduction of the retention was executed. - User-visible CLI/MCP output (if applicable): none for under-ceiling requests. An over-ceiling request now drops the connection where it previously retained the line; the connecting client sees its socket close. - Remaining proof gaps: the bounded read has not executed against a live Ghidra bridge, and the compile itself happened only in CI. Runtime verification needs a bridge session, which maintainers or a follow-up with a Ghidra installation can provide. 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 This checkout has no JDK and repository policy keeps Ghidra bring-your-own, so no local command could compile or execute a Java change. What was done instead: - Verified at the source level that exactly one unbounded read existed, that it served both transports, and that the replacement returns the same line content for any line under the ceiling, including carriage-return handling. - Confirmed the launch environment passes REA's process environment to the Ghidra process, so the shared `REA_BRIDGE_MAX_REQUEST_BYTES` setting reaches the bridge without a launcher change. - `gh pr` and issue searches across open and closed states found no existing claim on this boundary. - The `ghidra-bridge` CI lane compiles the packaged bridge sources against a checksum-verified Ghidra SDK and is the verification path for this revision; it triggers on changes under `bridge/ghidra/`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. A request under the ceiling produces the identical line; an over-ceiling request previously retained unbounded memory and now drops the connection. No `!` marker is needed. - Real Hopper/Ghidra, browser, or OS coverage: not run locally. The CI lane compiles the packaged sources, and runtime behavior of the bound needs a live bridge session. - Package or release metadata impact: none. No dependency, lockfile, catalog, or skill bundle change. - Security, privacy, process, or containment review: the change bounds one client-controlled retention path inside the bridge JVM and adds no new input path, no new network path, and no credential handling. The ceiling arrives through the process environment as a size setting; session tokens keep traveling through the private session descriptor and are not placed in the environment. ## Author readiness Human owner: @DeryFerd - [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. The Java bridge has no unit harness in this repository; the CI compile lane and the unchanged under-ceiling behavior are the coverage, with the gap stated above. - [x] Owning docs, contracts, and generated metadata are updated where needed. No owning document describes the bridge's read loop, and no ceiling setting or contract changes. - [x] User-visible CLI/MCP changes include representative output. There is no output change for under-ceiling requests; the over-ceiling drop is described under Evidence. - [x] 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.}

bsakaguchi added the

pull-request

label 2026-11-03 13:38:40 +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

Subscribe

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#7554

No description provided.