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 #5283] feat(mcp): hold several analysis targets open concurrently #6855

New issue
Open
opened 2026-11-01 21:43:34 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:43:34 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/5283
Author: @goncalompontes
Created: 10/19/2026
Status: 🔄 Open

Base: main ← Head: feat/multi-target-sessions

📝 Commits (1)

  • 0aff2bd feat(mcp): hold several analysis targets open concurrently

📊 Changes

49 files changed (+1669 additions, -88 deletions)

View changed files

📝 docs/mcp-contracts.md (+22 -4)
➕ docs/specs/multi-target-sessions/spec.md (+155 -0)
➕ docs/specs/multi-target-sessions/tasks.md (+58 -0)
📝 docs/tool-design.md (+6 -0)
📝 docs/user-visible-errors.csv (+2 -1)
📝 src/application/AnalysisProvider.ts (+2 -0)
📝 src/application/DirectAnalysis.ts (+7 -6)
📝 src/application/DirectAnalysisCleanup.ts (+3 -2)
📝 src/application/DirectAnalysisDependencies.ts (+9 -9)
📝 src/application/binary/BinarySession.ts (+67 -10)
📝 src/application/binary/BinarySessionComposition.ts (+6 -4)
📝 src/application/binary/BinarySessionPort.ts (+68 -8)
➕ src/application/binary/BinaryTargetRegistry.test.ts (+164 -0)
➕ src/application/binary/BinaryTargetRegistry.ts (+709 -0)
📝 src/composition/binary.ts (+12 -7)
➕ src/config/binaryTargetLimits.ts (+14 -0)
📝 src/config/environment.ts (+11 -0)
📝 src/config/parseConfig.ts (+2 -0)
📝 src/config/types.ts (+2 -0)
📝 src/contracts/officialToolContracts.ts (+4 -1)

...and 29 more files

📄 Description

Summary

Tracks #5272. One MCP server can now hold several analysis targets at once. Each target keeps its own provider process, lifecycle lock, cancellation scope, and analysis snapshot, so work on different targets no longer replaces the current target or serializes behind it.

This is a draft because #5272 changes the target-bound tool contract and needs a maintainer scope decision before integration. keep_others_open is opt-in; the default remains today's single-target replacement.

Problem and expected behavior

BinarySession owns one active binding and one transition chain. Opening another target drains calls and retires the current provider, even though each Ghidra analysis already runs in its own JVM. A game with many DLLs therefore has to be analysed one module at a time.

After this change, open_binary returns an opaque target_id. keep_others_open: true adds a slot instead of replacing the current one. Official analysis tools accept an optional target_id; omitting it addresses the current target, so existing transcripts keep working. binary_session reports target_id and open_target_ids; close_binary accepts target_id. Unknown handles return target_not_open with the open ids and no paths.

Change and scope

  • BinaryTargetRegistry (src/application/binary/BinaryTargetRegistry.ts) owns independent BinarySession slots. Slots share one investigation-record store and provider registry; each keeps its own transition lock, calls, provider client, and snapshot cache.
  • REA_MAX_OPEN_TARGETS (default 4) bounds open slots with a capacity refusal. REA_MAX_CONCURRENT_ANALYSES (default 2) bounds overlapping starts with FIFO admission.
  • Routing happens once in withAdmittedAnalysis; the selector is stripped before provider parameters and Evidence parameters.
  • Server shutdown uses closeAll; the close_binary tool still closes only the selected/current slot.
  • Added the draft design and task status in docs/specs/multi-target-sessions/, plus updates to docs/mcp-contracts.md, docs/tool-design.md, and docs/user-visible-errors.csv.

Not included in this draft:

  • target_id on enhanced workflows, native, artifact, managed, and provider-specific tools. Official analysis and lifecycle tools are covered; the remaining families follow the same admission seam.
  • rea analyze <path>... --concurrency N.
  • A real-provider concurrent-versus-serial measurement. No number is claimed.

Contract and boundary impact

  • Semantic owner and earliest changed stage: application BinaryTargetRegistry; provider clients are created per slot as before.
  • Contribution scope fit and linked maintainer decision: pending. #5272 requires an explicit maintainer scope decision for the target-bound selector.
  • CLI and MCP/tool-catalog contract: additive optional target_id on official analysis tools and lifecycle inputs; keep_others_open defaults to false; new target_not_open error code.
  • Provider, bridge, target-format, or platform compatibility: no provider protocol change. Each slot uses the existing provider lifecycle.
  • Evidence, artifact, provenance, or reconstruction contract: Evidence stays bound to the target digest. The handle is routing metadata only and is not written into provider parameters.
  • Target selection, authority, upstream behavior, and cleanup details: read-only analysis; server shutdown closes every slot.
  • Generated metadata: docs/public/product-catalog.json and skills/ are generated outputs and are not committed.

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: src/application/binary/BinaryTargetRegistry.test.ts covers reopen identity, two-target routing, replacement, capacity refusal, unknown handles, FIFO start queueing, per-slot close, and close-all shutdown. tests/boundary/mcp/multiTargetSessionMcp.test.ts drives two targets over the MCP client/server boundary with an in-memory transport, checks status handles, routed Evidence identity, target_not_open, and closing one slot.
  • Base reproduction or other evidence: the existing BinarySession composition, liveness, status, contract, and error-projection tests still pass unchanged.
  • User-visible CLI/MCP output: in-memory MCP test asserts open_binary.result.target_id, binary_session.result.target_id/open_target_ids, and target_not_open.
  • Remaining proof gaps: real Ghidra concurrency measurements; built boundary runner (npm run test:focused) could not execute in this worktree because the packaged Windows native controls are missing. The boundary test was executed directly with npx vitest run. npm run docs:check is blocked for the same native-controls reason.

Validation performed

  • npm run check:fast — passed (typecheck and lint).
  • npm run test:local -- src/application/binary/BinaryTargetRegistry.test.ts tests/composition/analysis-sessions/binarySession.test.ts — 51 passed.
  • npm run test:local -- src/domain/analysisErrorProjection.test.ts src/domain/analysisErrorCleanup.test.ts src/contracts/sessionLifecycleInputs.test.ts — 72 passed.
  • npm run test:local -- src/contracts/... tests/composition/analysis-sessions/binarySession.test.ts — 150 passed (contracts and session).
  • npx vitest run tests/boundary/mcp/multiTargetSessionMcp.test.ts — 2 passed.
  • npx vitest run tests/boundary/mcp/ghidraEvidenceMcp.test.ts tests/boundary/mcp/ghidraInventoryMcp.test.ts — 14 passed, 1 failed on the pre-existing missing Windows native controls (PrivateRuntimeRootUnavailableError), not on this change.
  • npm run docs:check — not run to completion; blocked by missing native/windows/build/manifest.json.

Compatibility, safety, and release

  • Breaking changes or migration steps: none required. target_id and keep_others_open are additive; omission preserves single-target behavior.
  • Real Hopper/Ghidra, browser, or OS coverage: no real-provider run. The fixtures exercise the application and MCP boundaries only.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: no new execution, injection, mutation, or network capability. target_not_open omits paths.

Author readiness

Human owner:

  • 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/5283 **Author:** [@goncalompontes](https://github.com/goncalompontes) **Created:** 10/19/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/multi-target-sessions` --- ### 📝 Commits (1) - [`0aff2bd`](https://github.com/morluto/rea/commit/0aff2bd1d177afdb12444a162680dba555ae033c) feat(mcp): hold several analysis targets open concurrently ### 📊 Changes **49 files changed** (+1669 additions, -88 deletions) <details> <summary>View changed files</summary> 📝 `docs/mcp-contracts.md` (+22 -4) ➕ `docs/specs/multi-target-sessions/spec.md` (+155 -0) ➕ `docs/specs/multi-target-sessions/tasks.md` (+58 -0) 📝 `docs/tool-design.md` (+6 -0) 📝 `docs/user-visible-errors.csv` (+2 -1) 📝 `src/application/AnalysisProvider.ts` (+2 -0) 📝 `src/application/DirectAnalysis.ts` (+7 -6) 📝 `src/application/DirectAnalysisCleanup.ts` (+3 -2) 📝 `src/application/DirectAnalysisDependencies.ts` (+9 -9) 📝 `src/application/binary/BinarySession.ts` (+67 -10) 📝 `src/application/binary/BinarySessionComposition.ts` (+6 -4) 📝 `src/application/binary/BinarySessionPort.ts` (+68 -8) ➕ `src/application/binary/BinaryTargetRegistry.test.ts` (+164 -0) ➕ `src/application/binary/BinaryTargetRegistry.ts` (+709 -0) 📝 `src/composition/binary.ts` (+12 -7) ➕ `src/config/binaryTargetLimits.ts` (+14 -0) 📝 `src/config/environment.ts` (+11 -0) 📝 `src/config/parseConfig.ts` (+2 -0) 📝 `src/config/types.ts` (+2 -0) 📝 `src/contracts/officialToolContracts.ts` (+4 -1) _...and 29 more files_ </details> ### 📄 Description ## Summary Tracks #5272. One MCP server can now hold several analysis targets at once. Each target keeps its own provider process, lifecycle lock, cancellation scope, and analysis snapshot, so work on different targets no longer replaces the current target or serializes behind it. This is a draft because #5272 changes the target-bound tool contract and needs a maintainer scope decision before integration. `keep_others_open` is opt-in; the default remains today's single-target replacement. ## Problem and expected behavior `BinarySession` owns one active binding and one transition chain. Opening another target drains calls and retires the current provider, even though each Ghidra analysis already runs in its own JVM. A game with many DLLs therefore has to be analysed one module at a time. After this change, `open_binary` returns an opaque `target_id`. `keep_others_open: true` adds a slot instead of replacing the current one. Official analysis tools accept an optional `target_id`; omitting it addresses the current target, so existing transcripts keep working. `binary_session` reports `target_id` and `open_target_ids`; `close_binary` accepts `target_id`. Unknown handles return `target_not_open` with the open ids and no paths. ## Change and scope - `BinaryTargetRegistry` (`src/application/binary/BinaryTargetRegistry.ts`) owns independent `BinarySession` slots. Slots share one investigation-record store and provider registry; each keeps its own transition lock, calls, provider client, and snapshot cache. - `REA_MAX_OPEN_TARGETS` (default 4) bounds open slots with a `capacity` refusal. `REA_MAX_CONCURRENT_ANALYSES` (default 2) bounds overlapping starts with FIFO admission. - Routing happens once in `withAdmittedAnalysis`; the selector is stripped before provider parameters and Evidence parameters. - Server shutdown uses `closeAll`; the `close_binary` tool still closes only the selected/current slot. - Added the draft design and task status in `docs/specs/multi-target-sessions/`, plus updates to `docs/mcp-contracts.md`, `docs/tool-design.md`, and `docs/user-visible-errors.csv`. Not included in this draft: - `target_id` on enhanced workflows, native, artifact, managed, and provider-specific tools. Official analysis and lifecycle tools are covered; the remaining families follow the same admission seam. - `rea analyze <path>... --concurrency N`. - A real-provider concurrent-versus-serial measurement. No number is claimed. ## Contract and boundary impact - Semantic owner and earliest changed stage: application `BinaryTargetRegistry`; provider clients are created per slot as before. - Contribution scope fit and linked maintainer decision: pending. #5272 requires an explicit maintainer scope decision for the target-bound selector. - CLI and MCP/tool-catalog contract: additive optional `target_id` on official analysis tools and lifecycle inputs; `keep_others_open` defaults to false; new `target_not_open` error code. - Provider, bridge, target-format, or platform compatibility: no provider protocol change. Each slot uses the existing provider lifecycle. - Evidence, artifact, provenance, or reconstruction contract: Evidence stays bound to the target digest. The handle is routing metadata only and is not written into provider parameters. - Target selection, authority, upstream behavior, and cleanup details: read-only analysis; server shutdown closes every slot. - Generated metadata: `docs/public/product-catalog.json` and `skills/` are generated outputs and are not committed. Expected effects: - [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: `src/application/binary/BinaryTargetRegistry.test.ts` covers reopen identity, two-target routing, replacement, capacity refusal, unknown handles, FIFO start queueing, per-slot close, and close-all shutdown. `tests/boundary/mcp/multiTargetSessionMcp.test.ts` drives two targets over the MCP client/server boundary with an in-memory transport, checks status handles, routed Evidence identity, `target_not_open`, and closing one slot. - Base reproduction or other evidence: the existing `BinarySession` composition, liveness, status, contract, and error-projection tests still pass unchanged. - User-visible CLI/MCP output: in-memory MCP test asserts `open_binary.result.target_id`, `binary_session.result.target_id`/`open_target_ids`, and `target_not_open`. - Remaining proof gaps: real Ghidra concurrency measurements; built boundary runner (`npm run test:focused`) could not execute in this worktree because the packaged Windows native controls are missing. The boundary test was executed directly with `npx vitest run`. `npm run docs:check` is blocked for the same native-controls reason. ## Validation performed - `npm run check:fast` — passed (typecheck and lint). - `npm run test:local -- src/application/binary/BinaryTargetRegistry.test.ts tests/composition/analysis-sessions/binarySession.test.ts` — 51 passed. - `npm run test:local -- src/domain/analysisErrorProjection.test.ts src/domain/analysisErrorCleanup.test.ts src/contracts/sessionLifecycleInputs.test.ts` — 72 passed. - `npm run test:local -- src/contracts/... tests/composition/analysis-sessions/binarySession.test.ts` — 150 passed (contracts and session). - `npx vitest run tests/boundary/mcp/multiTargetSessionMcp.test.ts` — 2 passed. - `npx vitest run tests/boundary/mcp/ghidraEvidenceMcp.test.ts tests/boundary/mcp/ghidraInventoryMcp.test.ts` — 14 passed, 1 failed on the pre-existing missing Windows native controls (`PrivateRuntimeRootUnavailableError`), not on this change. - `npm run docs:check` — not run to completion; blocked by missing `native/windows/build/manifest.json`. ## Compatibility, safety, and release - Breaking changes or migration steps: none required. `target_id` and `keep_others_open` are additive; omission preserves single-target behavior. - Real Hopper/Ghidra, browser, or OS coverage: no real-provider run. The fixtures exercise the application and MCP boundaries only. - Package or release metadata impact: none. - Security, privacy, process, or containment review: no new execution, injection, mutation, or network capability. `target_not_open` omits paths. ## Author readiness Human owner: <!-- @GitHub-handle --> - [ ] 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`. - [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. - [ ] 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. --- <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#6855
No description provided.