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 #2309] [MERGED] feat(clients): register Factory Droid during setup #5154

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/2309
Author: @0xRafie
Created: 10/12/2026
Status: ✅ Merged
Merged: 10/13/2026
Merged by: @morluto

Base: main ← Head: feat/setup-factory-droid

📝 Commits (1)

  • 1c4e343 feat(clients): register Factory Droid during setup

📊 Changes

6 files changed (+191 additions, -1 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/references/connection-and-recovery.md (+1 -1)
📝 docs/client-configuration.md (+8 -0)
📝 docs/installation.md (+1 -0)
📝 src/application/SupportedClients.ts (+13 -0)
📝 tests/boundary/filesystem/clientLifecycle.test.ts (+1 -0)
➕ tests/boundary/filesystem/droidClientConfiguration.test.ts (+167 -0)

📄 Description

Summary

Registers Factory Droid (the droid CLI) as a supported client during npx rea-agents setup, following the Qoder registration (#1572). After this change, Droid users can install REA with one command: setup writes the rea MCP server into the user-level ~/.factory/mcp.json and installs the skill copy into ~/.factory/skills. No linked issue; I found no existing issue or PR for Droid support.

Problem and expected behavior

Factory Droid is not among the clients setup recognizes, so Droid users have to hand-edit ~/.factory/mcp.json and copy the skill themselves. Expected: after rea setup --client droid, mcpServers.rea exists in ~/.factory/mcp.json, the skill is installed under ~/.factory/skills/reverse-engineer-anything, doctor reports the registration as aligned, and uninstall removes exactly the rea entry and the skill copy.

Droid's configuration, per the official docs (MCP, skills):

  • User-level MCP servers live under the top-level mcpServers key of ~/.factory/mcp.json. A project-level .factory/mcp.json also exists; it is out of scope here.
  • Droid's own entries usually carry type (stdio or http), command, args, env and disabled. REA's existing json format writes command/args (plus env when needed) without type. With the real Droid CLI, such an entry is listed as a stdio server and connects (see Evidence).
  • Personal skills are discovered from ~/.factory/skills/<name>/SKILL.md.

Change and scope

  • SupportedClients: droid definition (display name "Factory Droid"): config path ~/.factory/mcp.json, marker ~/.factory, skills ~/.factory/skills, format json. No new dialect or code path.
  • Tests: new tests/boundary/filesystem/droidClientConfiguration.test.ts (6 cases); the clientLifecycle.test.ts expected detection list includes droid.
  • Docs: a row in the Supported agents table, a "Factory Droid" section in docs/client-configuration.md, and the client id in the skill's references/connection-and-recovery.md.
  • Intentionally out of scope: the project-level .factory/mcp.json, and a home-directory override variable (I found none documented by Factory, so none is honored).
  • The client id droid matches the CLI name; happy to rename it (for example factory_droid) if you prefer.

Contribution scope: a setup registration within existing boundaries, following the Qoder (#1572) and Qwen Code (#1415) registrations; maintainer scope decision not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: application-layer setup client registration (SupportedClients).
  • Contribution scope fit and linked maintainer decision: not applicable (see above).
  • CLI and MCP/tool-catalog contract: no tools added or changed; --client droid becomes a valid value.
  • Provider, bridge, target-format, or platform compatibility: adds the droid client, reusing the existing json configuration format.
  • Evidence, artifact, provenance, or reconstruction contract: not applicable.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): setup writes only mcpServers.rea; unrelated servers and Droid's top-level persistentPermissions are preserved. Uninstall removes only the rea entry and the skill copy.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none authored; generated catalogs stay CI-owned.

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.

The two checked effects are setup's existing behavior (reading and writing the client's MCP config with a backup), now applied to ~/.factory/mcp.json.

Evidence and regression coverage

  • Tests added or updated: droidClientConfiguration.test.ts covers config path resolution on linux/darwin/win32; the skill destination; an upsert that preserves an unrelated mcpServers entry and a Droid-shaped top-level persistentPermissions object; an idempotent re-run that reports unchanged with registration status aligned; creating mcpServers in an existing file without servers; an empty file; and uninstall removing only rea. clientLifecycle.test.ts now expects droid in the detected list.
  • Base reproduction or other evidence: end-to-end with the real Droid CLI 0.235.0 on macOS 26.7.1, in a throwaway HOME that contained only an empty .factory directory, using the CLI built from this branch:
    • rea setup --client droid --yes wrote mcpServers.rea = {"command": "<checkout>/scripts/rea.mjs", "args": ["mcp"]} (no type) and installed .factory/skills/reverse-engineer-anything.
    • rea doctor --json: the droid registration reports state: "aligned" and remediation: null. doctor itself exits 1 in such an empty HOME; it does the same in an empty HOME without .factory, so that status comes from the other unconfigured checks, not from this client.
    • droid mcp list: rea stdio connected [user].
    • rea uninstall removed the Droid registration and the skill copy; mcp.json became {"mcpServers": {}}.
  • User-visible CLI/MCP output (if applicable): setup, doctor and uninstall list "Factory Droid" / droid.
  • Remaining proof gaps: only macOS was run (path resolution for Linux and Windows is covered by the boundary test). The project-level .factory/mcp.json is not handled. The test fixture matches the real persistentPermissions shape by key and type only, with fake values.

For evidence-bearing changes: not applicable (setup registration; no Evidence contract change).

Validation performed

  • npx vitest run tests/boundary/filesystem/droidClientConfiguration.test.ts tests/boundary/filesystem/clientLifecycle.test.ts — 2 files, 59 tests passed
  • npm run check — passed (architecture guards across 1227 source files)
  • npm run check:fast — typecheck and lint passed
  • npm run verify:test-discovery — all 963 test files discovered exactly once
  • npm run docs:check — passed
  • npm run verify:package — passed (skill and its 6 references installed with Skills 1.7.2; setup planned-then-idempotent; 185 MCP tools)
  • npm pack --dry-run — passed (1473 files)
  • The end-to-end run under Evidence, with the real Droid CLI
  • Fetched https://docs.factory.com/harness/mcp and https://docs.factory.com/harness/skills (both HTTP 200); they document ~/.factory/mcp.json and ~/.factory/skills/<skill-name>/SKILL.md
  • Toolchain: Node 26.9.0 and npm 11.19.1 on main 0365454 (.nvmrc pins 24.18.0, so CI covers the pinned toolchain)

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. macOS 26.7.1 with Droid CLI 0.235.0 for the end-to-end run; config I/O is covered by filesystem boundary tests.
  • Package or release metadata impact: none.
  • Security, privacy, process, or containment review: setup writes only the rea entry into ~/.factory/mcp.json, preserving all unrelated content; no network access or process execution added.

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/2309 **Author:** [@0xRafie](https://github.com/0xRafie) **Created:** 10/12/2026 **Status:** ✅ Merged **Merged:** 10/13/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `feat/setup-factory-droid` --- ### 📝 Commits (1) - [`1c4e343`](https://github.com/morluto/rea/commit/1c4e34332cd5488de4cd98f485f67365026256f0) feat(clients): register Factory Droid during setup ### 📊 Changes **6 files changed** (+191 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md` (+1 -1) 📝 `docs/client-configuration.md` (+8 -0) 📝 `docs/installation.md` (+1 -0) 📝 `src/application/SupportedClients.ts` (+13 -0) 📝 `tests/boundary/filesystem/clientLifecycle.test.ts` (+1 -0) ➕ `tests/boundary/filesystem/droidClientConfiguration.test.ts` (+167 -0) </details> ### 📄 Description ## Summary Registers Factory Droid (the `droid` CLI) as a supported client during `npx rea-agents setup`, following the Qoder registration (#1572). After this change, Droid users can install REA with one command: setup writes the `rea` MCP server into the user-level `~/.factory/mcp.json` and installs the skill copy into `~/.factory/skills`. No linked issue; I found no existing issue or PR for Droid support. ## Problem and expected behavior Factory Droid is not among the clients setup recognizes, so Droid users have to hand-edit `~/.factory/mcp.json` and copy the skill themselves. Expected: after `rea setup --client droid`, `mcpServers.rea` exists in `~/.factory/mcp.json`, the skill is installed under `~/.factory/skills/reverse-engineer-anything`, `doctor` reports the registration as aligned, and uninstall removes exactly the `rea` entry and the skill copy. Droid's configuration, per the official docs ([MCP](https://docs.factory.com/harness/mcp), [skills](https://docs.factory.com/harness/skills)): - User-level MCP servers live under the top-level `mcpServers` key of `~/.factory/mcp.json`. A project-level `.factory/mcp.json` also exists; it is out of scope here. - Droid's own entries usually carry `type` (`stdio` or `http`), `command`, `args`, `env` and `disabled`. REA's existing `json` format writes `command`/`args` (plus `env` when needed) without `type`. With the real Droid CLI, such an entry is listed as a stdio server and connects (see Evidence). - Personal skills are discovered from `~/.factory/skills/<name>/SKILL.md`. ## Change and scope - `SupportedClients`: `droid` definition (display name "Factory Droid"): config path `~/.factory/mcp.json`, marker `~/.factory`, skills `~/.factory/skills`, format `json`. No new dialect or code path. - Tests: new `tests/boundary/filesystem/droidClientConfiguration.test.ts` (6 cases); the `clientLifecycle.test.ts` expected detection list includes `droid`. - Docs: a row in the Supported agents table, a "Factory Droid" section in `docs/client-configuration.md`, and the client id in the skill's `references/connection-and-recovery.md`. - Intentionally out of scope: the project-level `.factory/mcp.json`, and a home-directory override variable (I found none documented by Factory, so none is honored). - The client id `droid` matches the CLI name; happy to rename it (for example `factory_droid`) if you prefer. Contribution scope: a setup registration within existing boundaries, following the Qoder (#1572) and Qwen Code (#1415) registrations; maintainer scope decision not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: application-layer setup client registration (`SupportedClients`). - Contribution scope fit and linked maintainer decision: not applicable (see above). - CLI and MCP/tool-catalog contract: no tools added or changed; `--client droid` becomes a valid value. - Provider, bridge, target-format, or platform compatibility: adds the `droid` client, reusing the existing `json` configuration format. - Evidence, artifact, provenance, or reconstruction contract: not applicable. - Target selection, authority, upstream behavior, and cleanup details (if applicable): setup writes only `mcpServers.rea`; unrelated servers and Droid's top-level `persistentPermissions` are preserved. Uninstall removes only the `rea` entry and the skill copy. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none authored; generated catalogs stay CI-owned. 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. - [x] 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. The two checked effects are setup's existing behavior (reading and writing the client's MCP config with a backup), now applied to `~/.factory/mcp.json`. ## Evidence and regression coverage - Tests added or updated: `droidClientConfiguration.test.ts` covers config path resolution on linux/darwin/win32; the skill destination; an upsert that preserves an unrelated `mcpServers` entry and a Droid-shaped top-level `persistentPermissions` object; an idempotent re-run that reports `unchanged` with registration status `aligned`; creating `mcpServers` in an existing file without servers; an empty file; and uninstall removing only `rea`. `clientLifecycle.test.ts` now expects `droid` in the detected list. - Base reproduction or other evidence: end-to-end with the real Droid CLI 0.235.0 on macOS 26.7.1, in a throwaway `HOME` that contained only an empty `.factory` directory, using the CLI built from this branch: - `rea setup --client droid --yes` wrote `mcpServers.rea = {"command": "<checkout>/scripts/rea.mjs", "args": ["mcp"]}` (no `type`) and installed `.factory/skills/reverse-engineer-anything`. - `rea doctor --json`: the `droid` registration reports `state: "aligned"` and `remediation: null`. `doctor` itself exits 1 in such an empty `HOME`; it does the same in an empty `HOME` without `.factory`, so that status comes from the other unconfigured checks, not from this client. - `droid mcp list`: `rea stdio connected [user]`. - `rea uninstall` removed the Droid registration and the skill copy; `mcp.json` became `{"mcpServers": {}}`. - User-visible CLI/MCP output (if applicable): setup, doctor and uninstall list "Factory Droid" / `droid`. - Remaining proof gaps: only macOS was run (path resolution for Linux and Windows is covered by the boundary test). The project-level `.factory/mcp.json` is not handled. The test fixture matches the real `persistentPermissions` shape by key and type only, with fake values. For evidence-bearing changes: not applicable (setup registration; no Evidence contract change). ## Validation performed - `npx vitest run tests/boundary/filesystem/droidClientConfiguration.test.ts tests/boundary/filesystem/clientLifecycle.test.ts` — 2 files, 59 tests passed - `npm run check` — passed (architecture guards across 1227 source files) - `npm run check:fast` — typecheck and lint passed - `npm run verify:test-discovery` — all 963 test files discovered exactly once - `npm run docs:check` — passed - `npm run verify:package` — passed (skill and its 6 references installed with Skills 1.7.2; setup planned-then-idempotent; 185 MCP tools) - `npm pack --dry-run` — passed (1473 files) - The end-to-end run under Evidence, with the real Droid CLI - Fetched https://docs.factory.com/harness/mcp and https://docs.factory.com/harness/skills (both HTTP 200); they document `~/.factory/mcp.json` and `~/.factory/skills/<skill-name>/SKILL.md` - Toolchain: Node 26.9.0 and npm 11.19.1 on main `0365454` (`.nvmrc` pins 24.18.0, so CI covers the pinned toolchain) ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. macOS 26.7.1 with Droid CLI 0.235.0 for the end-to-end run; config I/O is covered by filesystem boundary tests. - Package or release metadata impact: none. - Security, privacy, process, or containment review: setup writes only the `rea` entry into `~/.factory/mcp.json`, preserving all unrelated content; no network access or process execution added. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 01:04:23 +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#5154
No description provided.