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 #6820] [CLOSED] fix(cli): reject an empty desktop application path #7419

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6820
Author: @amyanger
Created: 10/23/2026
Status: ❌ Closed

Base: main ← Head: fix/6757-empty-desktop-path

📝 Commits (1)

  • 2a4f498 fix(cli): reject an empty desktop application path

📊 Changes

2 files changed (+28 additions, -1 deletions)

View changed files

📝 src/cli/desktopApplicationCommands.ts (+8 -1)
📝 tests/boundary/cli/desktopApplicationCli.test.ts (+20 -0)

📄 Description

Summary

Fixes #6757.

rea inspect-desktop-application "" silently inspected the current working directory and exited 0. The CLI made the empty path absolute before the service saw it, so the service's non-empty check never ran. The command now passes the empty path through unchanged, and the service rejects it with invalid_request.

Problem and expected behavior

src/cli/desktopApplicationCommands.ts called absoluteCallerPath(args.path). For "", that helper prefixes the working directory, so the selection became the working directory. The desktop inspection input schema (absoluteLocalPathStringSchema, src/domain/localPath.ts) requires a non-empty absolute path and rejects "", which is what MCP callers already get.

Invariant: CLI path anchoring may make a named path absolute, but must not turn a selection that names no file into a different, valid target.

Change and scope

The command now passes args.path === "" ? args.path : absoluteCallerPath(args.path), the same guard and comment that #5265 (1a945ce9f) added to analyze-javascript-application in src/cli/electronCommands.ts.

Not included:

  • Whitespace-only paths. " " is a real file name and becomes <cwd>/ , which fails as target_unavailable. It does not fall back to the working directory, and the precedent guards only "" as well.
  • Other commands. About 27 other CLI commands still call absoluteCallerPath(args.path) without an empty-path guard. They are outside this issue. A shared guard in absoluteCallerPath would be a separate change, since some callers may pass paths that are not user selections.
  • MCP. inspect_desktop_application over MCP never calls absoluteCallerPath and already rejects "".

Contract and boundary impact

  • Semantic owner and earliest changed stage: CLI argument anchoring in src/cli/desktopApplicationCommands.ts, before the service call.
  • Contribution scope fit and linked maintainer decision: not applicable, ordinary fix within an existing boundary.
  • CLI and MCP/tool-catalog contract: CLI only. An empty path now yields the existing typed invalid_request refusal instead of a successful inspection of the working directory. MCP is unchanged and already behaved this way.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: an empty selection no longer creates Evidence for the working directory.
  • Target selection, authority, upstream behavior, and cleanup details: the command no longer reads a directory the caller did not select.
  • Generated metadata, package, or installation impact: none.

Expected effects:

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

Evidence and regression coverage

  • Tests added or updated: tests/boundary/cli/desktopApplicationCli.test.ts, "rejects an empty path instead of inspecting the working directory". It runs the compiled CLI with "" from a temporary working directory that is itself a valid inspection target (it contains resources/app.asar), and expects exit 1 with code: "invalid_request" and category: "invalid_input". It follows the test #5265 added.
  • Base reproduction (executed): on base 1635eadfc with the new test, npm run test:focused -- tests/boundary/cli/desktopApplicationCli.test.ts gives 1 failed, 3 passed, with expected 0 to be 1 on the exit code. Because the temporary directory is a valid target, the base failure is the reported bug, not an unrelated error.
  • Mutation: the fix is one conditional. Reverting it restores the base code, which fails the new test as shown above.
  • User-visible CLI output (executed, from a temporary directory containing resources/app.asar, node scripts/rea.mjs inspect-desktop-application "" --json):
    • Base: exit 0, {"evidence_id":"ev_9da6b7ce...","subject":{"name":"desk",...,"local_path":"<the working directory>"...
    • Branch: exit 1, {"code":"invalid_request","category":"invalid_input","message":"Analysis input is invalid. Check the arguments and try again.",.... The details list path failing minimum: 1 and the absolute-path format.
  • Remaining proof gaps: not run on Windows. The schema rejects "" on every platform, and the guard runs before any platform-specific path handling.

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

All commands ran on macOS arm64 with Node v24.22.1, base 1635eadfc (newest upstream main commit with green CI). Both changed files are identical on that commit and on the current main tip.

  • npm run test:focused -- tests/boundary/cli/desktopApplicationCli.test.ts: 4 tests passed.
  • npm run check:fast: passed.
  • npm run test:changed -- --base 1635eadfc: 3 files, 18 tests passed. This command selects only source-level projects, so the CLI boundary file is covered by the test:focused run above.
  • npm run check: exit 0.
  • Independent review (separate worktree, read-only on the checkout) confirmed the service's rejection, the MCP behavior, whitespace handling and the base failure. It found no doc, fixture or golden that relies on "" meaning the working directory.
  • /code-review (high) on the uncommitted diff reported three findings, all about scope rather than correctness:
    • About 20 other CLI commands pass args.path to absoluteCallerPath without the guard, and a guard inside the helper would fix them all. Verified, not changed. The helper has 55 calls in 36 files, and 18 of them are outside src/cli (for example BinaryTargetResolver, SafeOutputTree, RizinCommand, WasmGlueAdapter). Changing it would change what "" means on those paths too, which needs its own tracing and tests. This PR keeps the per-command guard from #5265.
    • Option paths such as --binary "" in il2cppCommands.ts and capture_path in webNetworkCaptureCommands.ts have the same conversion. Not changed: outside #6757.
    • The guard now exists in three places (electronCommands.ts twice, and this command). Noted. A shared helper guard would remove the copies; that belongs with the first point.
  • Real provider: not applicable. The change is in the CLI argument layer, exercised above through the compiled public CLI.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. A caller that relied on "" meaning the working directory can pass ., which the issue shows selects the same directory.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: the command no longer reads a directory the caller did not name.

Author readiness

Human owner: @amyanger

  • 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/6820 **Author:** [@amyanger](https://github.com/amyanger) **Created:** 10/23/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/6757-empty-desktop-path` --- ### 📝 Commits (1) - [`2a4f498`](https://github.com/morluto/rea/commit/2a4f498fd89d53624d60c74b66b9d9d6ed7d51d0) fix(cli): reject an empty desktop application path ### 📊 Changes **2 files changed** (+28 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `src/cli/desktopApplicationCommands.ts` (+8 -1) 📝 `tests/boundary/cli/desktopApplicationCli.test.ts` (+20 -0) </details> ### 📄 Description ## Summary Fixes #6757. `rea inspect-desktop-application ""` silently inspected the current working directory and exited 0. The CLI made the empty path absolute before the service saw it, so the service's non-empty check never ran. The command now passes the empty path through unchanged, and the service rejects it with `invalid_request`. ## Problem and expected behavior `src/cli/desktopApplicationCommands.ts` called `absoluteCallerPath(args.path)`. For `""`, that helper prefixes the working directory, so the selection became the working directory. The desktop inspection input schema (`absoluteLocalPathStringSchema`, `src/domain/localPath.ts`) requires a non-empty absolute path and rejects `""`, which is what MCP callers already get. Invariant: CLI path anchoring may make a named path absolute, but must not turn a selection that names no file into a different, valid target. ## Change and scope The command now passes `args.path === "" ? args.path : absoluteCallerPath(args.path)`, the same guard and comment that #5265 (`1a945ce9f`) added to `analyze-javascript-application` in `src/cli/electronCommands.ts`. Not included: - Whitespace-only paths. `" "` is a real file name and becomes `<cwd>/ `, which fails as `target_unavailable`. It does not fall back to the working directory, and the precedent guards only `""` as well. - Other commands. About 27 other CLI commands still call `absoluteCallerPath(args.path)` without an empty-path guard. They are outside this issue. A shared guard in `absoluteCallerPath` would be a separate change, since some callers may pass paths that are not user selections. - MCP. `inspect_desktop_application` over MCP never calls `absoluteCallerPath` and already rejects `""`. ## Contract and boundary impact - Semantic owner and earliest changed stage: CLI argument anchoring in `src/cli/desktopApplicationCommands.ts`, before the service call. - Contribution scope fit and linked maintainer decision: not applicable, ordinary fix within an existing boundary. - CLI and MCP/tool-catalog contract: CLI only. An empty path now yields the existing typed `invalid_request` refusal instead of a successful inspection of the working directory. MCP is unchanged and already behaved this way. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: an empty selection no longer creates Evidence for the working directory. - Target selection, authority, upstream behavior, and cleanup details: the command no longer reads a directory the caller did not select. - Generated metadata, package, or installation impact: none. 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 or updated: `tests/boundary/cli/desktopApplicationCli.test.ts`, "rejects an empty path instead of inspecting the working directory". It runs the compiled CLI with `""` from a temporary working directory that is itself a valid inspection target (it contains `resources/app.asar`), and expects exit 1 with `code: "invalid_request"` and `category: "invalid_input"`. It follows the test #5265 added. - Base reproduction (executed): on base `1635eadfc` with the new test, `npm run test:focused -- tests/boundary/cli/desktopApplicationCli.test.ts` gives 1 failed, 3 passed, with `expected 0 to be 1` on the exit code. Because the temporary directory is a valid target, the base failure is the reported bug, not an unrelated error. - Mutation: the fix is one conditional. Reverting it restores the base code, which fails the new test as shown above. - User-visible CLI output (executed, from a temporary directory containing `resources/app.asar`, `node scripts/rea.mjs inspect-desktop-application "" --json`): - Base: exit 0, `{"evidence_id":"ev_9da6b7ce...","subject":{"name":"desk",...,"local_path":"<the working directory>"...` - Branch: exit 1, `{"code":"invalid_request","category":"invalid_input","message":"Analysis input is invalid. Check the arguments and try again.",...`. The details list `path` failing `minimum: 1` and the absolute-path format. - Remaining proof gaps: not run on Windows. The schema rejects `""` on every platform, and the guard runs before any platform-specific path handling. 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 All commands ran on macOS arm64 with Node v24.22.1, base `1635eadfc` (newest upstream main commit with green CI). Both changed files are identical on that commit and on the current main tip. - `npm run test:focused -- tests/boundary/cli/desktopApplicationCli.test.ts`: 4 tests passed. - `npm run check:fast`: passed. - `npm run test:changed -- --base 1635eadfc`: 3 files, 18 tests passed. This command selects only source-level projects, so the CLI boundary file is covered by the `test:focused` run above. - `npm run check`: exit 0. - Independent review (separate worktree, read-only on the checkout) confirmed the service's rejection, the MCP behavior, whitespace handling and the base failure. It found no doc, fixture or golden that relies on `""` meaning the working directory. - `/code-review` (high) on the uncommitted diff reported three findings, all about scope rather than correctness: - About 20 other CLI commands pass `args.path` to `absoluteCallerPath` without the guard, and a guard inside the helper would fix them all. Verified, not changed. The helper has 55 calls in 36 files, and 18 of them are outside `src/cli` (for example `BinaryTargetResolver`, `SafeOutputTree`, `RizinCommand`, `WasmGlueAdapter`). Changing it would change what `""` means on those paths too, which needs its own tracing and tests. This PR keeps the per-command guard from #5265. - Option paths such as `--binary ""` in `il2cppCommands.ts` and `capture_path` in `webNetworkCaptureCommands.ts` have the same conversion. Not changed: outside #6757. - The guard now exists in three places (`electronCommands.ts` twice, and this command). Noted. A shared helper guard would remove the copies; that belongs with the first point. - Real provider: not applicable. The change is in the CLI argument layer, exercised above through the compiled public CLI. ## Compatibility, safety, and release - Breaking changes or migration steps: none. A caller that relied on `""` meaning the working directory can pass `.`, which the issue shows selects the same directory. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. - Package or release metadata impact: none. - Security, privacy, process, or containment review: the command no longer reads a directory the caller did not name. ## Author readiness Human owner: @amyanger - [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. - [ ] 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:43 +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#7419
No description provided.