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 #6418] [CLOSED] fix(electron): admit file pages whose query or fragment encodes a separator #7347

New issue
Closed
opened 2026-11-01 21:47:13 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:47:13 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6418
Author: @viniciusdsandrade
Created: 10/22/2026
Status: ❌ Closed

Base: main ← Head: fix/5872-electron-encoded-separators-outside-path

📝 Commits (3)

  • 36ff03a fix(electron): admit file pages whose query or fragment encodes a separator
  • 3d19fe4 test(electron): list and inspect pages with encoded separators after the path
  • 7ef0211 test(electron): keep refusing an encoded backslash in a POSIX file path

📊 Changes

3 files changed (+58 additions, -1 deletions)

View changed files

📝 src/browser/ElectronFileScope.ts (+2 -1)
📝 tests/boundary/browser/cdpElectronProvider.test.ts (+42 -0)
📝 tests/boundary/filesystem/electronFileScope.test.ts (+14 -0)

📄 Description

Summary

Fixes #5872

list_electron_targets excluded a local file page as unsupported_url, and inspect_electron_page refused it as target_not_allowed, when only its query or fragment contained %2F or %5C, for example index.html?next=%2Fsettings or index.html#%5Csettings. The encoded-separator guard in the shared Electron file authorization tested the complete URL string before new URL separated its components, while fileURLToPath selects the file from the path alone.

The guard now tests the parsed pathname. Query and fragment text no longer affects authorization, and an encoded separator in the path is still refused.

Problem and expected behavior

  • Smallest trigger: a CDP page target whose URL is the file URL of a regular file followed by ?next=%2Fsettings, ?next=%5Csettings, #%2Fsettings or #%5Csettings.
  • Violated invariant: docs/electron-observation.md accepts hostless local file:// URLs that resolve to regular files and rejects encoded path separators. Existing tests already accept query and fragment text (?isBookDoubleClicked=0#/library, a 70,000-character query). fileURLToPath ignores the query and fragment, so these URLs select the same file as the plain URL.
  • Expected: the four suffix forms are listed and inspected with the same file_path as the plain URL; an encoded separator in the path stays refused.

Change and scope

  • src/browser/ElectronFileScope.ts: the /%(?:2f|5c)/iu test moves after URL parsing and the protocol, host and credential checks, and applies to url.pathname. Once those checks pass, the path is the only remaining component that can select a file. src/domain/javascript/javascriptStaticAnalysisHelpers.ts already applies the same rule to the part before ? or #.
  • tests/boundary/browser/cdpElectronProvider.test.ts: lists and inspects a regular file page through the provider for each of the four suffixes from the issue.
  • tests/boundary/filesystem/electronFileScope.test.ts: on POSIX, refuses %5C in the path even when it decodes to an existing file name containing a backslash. There fileURLToPath decodes %5C without complaint, so this pins the guard that moved; it is skipped on Windows, where fileURLToPath itself refuses encoded separators in the path.
  • Not included: the encoded-separator checks in JavaScript module and source-map path resolution, which belong to other owners. No documentation change: the target boundary already describes the rule as rejecting encoded path separators.

Follow the contribution scope.
Scope decision: not applicable (ordinary fix within the existing Electron target authorization).

Contract and boundary impact

  • Semantic owner and earliest changed stage: resolveAuthorizedElectronFile in src/browser/ElectronFileScope.ts, behind authorizedElectronFile, which the Electron provider uses for targets, frames, scripts, resources and workers, and the V8 Inspector runtime scope uses for file locations.
  • Contribution scope fit and linked maintainer decision: not applicable.
  • CLI and MCP/tool-catalog contract: schemas unchanged. A file URL whose path names a regular file or ASAR member is authorized regardless of encoded separators in its query or fragment.
  • Provider, bridge, target-format, or platform compatibility: CDP Electron provider and V8 Inspector file scope on every platform.
  • Evidence, artifact, provenance, or reconstruction contract: unchanged; file_path is still the canonical path.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): authorization still requires a hostless file URL without credentials whose path names a regular file or an ASAR member, and still refuses encoded separators in the path. Admitted pages continue through the existing CDP attachment path unchanged.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: 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: CdpElectronProvider URL suffixes in tests/boundary/browser/cdpElectronProvider.test.ts (four cases) and refuses an encoded backslash that names an existing POSIX file in tests/boundary/filesystem/electronFileScope.test.ts.
  • Base reproduction or other evidence: source-derived. On the base revision resolveAuthorizedElectronFile returns undefined at the whole-string test for each suffix, so listTargets counts the page under excluded.unsupported_url and the new provider test's targets expectation fails. The issue reports the same exclusion and the target_not_allowed refusal through the built CLI against a simulated CDP discovery endpoint. The POSIX path test passes on both revisions and guards the moved check.
  • User-visible CLI/MCP output (if applicable): by reading, the issue's seven-target reproduction now lists all seven targets with excluded.unsupported_url: 0 instead of three targets and unsupported_url: 4; not replayed here.
  • Remaining proof gaps: no real Electron application; the fake CDP browser supplies discovery and inspection replies.

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

  • No local test, build or typecheck commands were run; verification is source-derived and CI executes the test suite. The repository pre-commit hook ran oxlint --fix and oxfmt on the staged files without changes to the committed content.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Only file URLs with encoded separators confined to the query or fragment change outcome.
  • Real Hopper/Ghidra, browser, or OS coverage: none run.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the path that selects a file is checked exactly as before; fileURLToPath ignores the query and fragment, so they never reach stat or ASAR resolution.

Author readiness

Human owner: @viniciusdsandrade

  • 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/6418 **Author:** [@viniciusdsandrade](https://github.com/viniciusdsandrade) **Created:** 10/22/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/5872-electron-encoded-separators-outside-path` --- ### 📝 Commits (3) - [`36ff03a`](https://github.com/morluto/rea/commit/36ff03a62c2746f47b6027c2847ec2d12dbccc0b) fix(electron): admit file pages whose query or fragment encodes a separator - [`3d19fe4`](https://github.com/morluto/rea/commit/3d19fe48efebd08818a29d6469089cea9677e99e) test(electron): list and inspect pages with encoded separators after the path - [`7ef0211`](https://github.com/morluto/rea/commit/7ef02110e9714a02cd113d5908c9e33d73c3cf23) test(electron): keep refusing an encoded backslash in a POSIX file path ### 📊 Changes **3 files changed** (+58 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/browser/ElectronFileScope.ts` (+2 -1) 📝 `tests/boundary/browser/cdpElectronProvider.test.ts` (+42 -0) 📝 `tests/boundary/filesystem/electronFileScope.test.ts` (+14 -0) </details> ### 📄 Description ## Summary Fixes #5872 `list_electron_targets` excluded a local file page as `unsupported_url`, and `inspect_electron_page` refused it as `target_not_allowed`, when only its query or fragment contained `%2F` or `%5C`, for example `index.html?next=%2Fsettings` or `index.html#%5Csettings`. The encoded-separator guard in the shared Electron file authorization tested the complete URL string before `new URL` separated its components, while `fileURLToPath` selects the file from the path alone. The guard now tests the parsed pathname. Query and fragment text no longer affects authorization, and an encoded separator in the path is still refused. ## Problem and expected behavior - Smallest trigger: a CDP page target whose URL is the file URL of a regular file followed by `?next=%2Fsettings`, `?next=%5Csettings`, `#%2Fsettings` or `#%5Csettings`. - Violated invariant: [docs/electron-observation.md](https://github.com/morluto/rea/blob/main/docs/electron-observation.md#target-boundary) accepts hostless local `file://` URLs that resolve to regular files and rejects encoded path separators. Existing tests already accept query and fragment text (`?isBookDoubleClicked=0#/library`, a 70,000-character query). `fileURLToPath` ignores the query and fragment, so these URLs select the same file as the plain URL. - Expected: the four suffix forms are listed and inspected with the same `file_path` as the plain URL; an encoded separator in the path stays refused. ## Change and scope - `src/browser/ElectronFileScope.ts`: the `/%(?:2f|5c)/iu` test moves after URL parsing and the protocol, host and credential checks, and applies to `url.pathname`. Once those checks pass, the path is the only remaining component that can select a file. `src/domain/javascript/javascriptStaticAnalysisHelpers.ts` already applies the same rule to the part before `?` or `#`. - `tests/boundary/browser/cdpElectronProvider.test.ts`: lists and inspects a regular file page through the provider for each of the four suffixes from the issue. - `tests/boundary/filesystem/electronFileScope.test.ts`: on POSIX, refuses `%5C` in the path even when it decodes to an existing file name containing a backslash. There `fileURLToPath` decodes `%5C` without complaint, so this pins the guard that moved; it is skipped on Windows, where `fileURLToPath` itself refuses encoded separators in the path. - Not included: the encoded-separator checks in JavaScript module and source-map path resolution, which belong to other owners. No documentation change: the target boundary already describes the rule as rejecting encoded path separators. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Scope decision: not applicable (ordinary fix within the existing Electron target authorization). ## Contract and boundary impact - Semantic owner and earliest changed stage: `resolveAuthorizedElectronFile` in `src/browser/ElectronFileScope.ts`, behind `authorizedElectronFile`, which the Electron provider uses for targets, frames, scripts, resources and workers, and the V8 Inspector runtime scope uses for file locations. - Contribution scope fit and linked maintainer decision: not applicable. - CLI and MCP/tool-catalog contract: schemas unchanged. A file URL whose path names a regular file or ASAR member is authorized regardless of encoded separators in its query or fragment. - Provider, bridge, target-format, or platform compatibility: CDP Electron provider and V8 Inspector file scope on every platform. - Evidence, artifact, provenance, or reconstruction contract: unchanged; `file_path` is still the canonical path. - Target selection, authority, upstream behavior, and cleanup details (if applicable): authorization still requires a hostless file URL without credentials whose path names a regular file or an ASAR member, and still refuses encoded separators in the path. Admitted pages continue through the existing CDP attachment path unchanged. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: 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: `CdpElectronProvider URL suffixes` in `tests/boundary/browser/cdpElectronProvider.test.ts` (four cases) and `refuses an encoded backslash that names an existing POSIX file` in `tests/boundary/filesystem/electronFileScope.test.ts`. - Base reproduction or other evidence: source-derived. On the base revision `resolveAuthorizedElectronFile` returns `undefined` at the whole-string test for each suffix, so `listTargets` counts the page under `excluded.unsupported_url` and the new provider test's `targets` expectation fails. The issue reports the same exclusion and the `target_not_allowed` refusal through the built CLI against a simulated CDP discovery endpoint. The POSIX path test passes on both revisions and guards the moved check. - User-visible CLI/MCP output (if applicable): by reading, the issue's seven-target reproduction now lists all seven targets with `excluded.unsupported_url: 0` instead of three targets and `unsupported_url: 4`; not replayed here. - Remaining proof gaps: no real Electron application; the fake CDP browser supplies discovery and inspection replies. 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 - No local test, build or typecheck commands were run; verification is source-derived and CI executes the test suite. The repository pre-commit hook ran `oxlint --fix` and `oxfmt` on the staged files without changes to the committed content. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Only file URLs with encoded separators confined to the query or fragment change outcome. - Real Hopper/Ghidra, browser, or OS coverage: none run. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the path that selects a file is checked exactly as before; `fileURLToPath` ignores the query and fragment, so they never reach `stat` or ASAR resolution. ## Author readiness Human owner: @viniciusdsandrade - [ ] 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 - [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-11-01 21:47:13 +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#7347
No description provided.