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 #4427] feat(setup): add FutureOS client support #6234

New issue
Open
opened 2026-10-31 01:12:53 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 01:12:53 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4427
Author: @huichen
Created: 10/16/2026
Status: 🔄 Open

Base: main ← Head: feat/future-setup-client

📝 Commits (2)

  • 67100d6 feat(setup): add FutureOS client support
  • 19aaaa4 docs(future): document the per-call connection the FutureOS CLI group gives REA

📊 Changes

7 files changed (+407 additions, -2 deletions)

View changed files

📝 docs/client-configuration.md (+69 -0)
📝 docs/installation.md (+3 -0)
📝 src/application/ClientConfigurationDocument.ts (+59 -2)
📝 src/application/SetupClientConfiguration.ts (+12 -0)
📝 src/application/SupportedClients.ts (+24 -0)
📝 tests/boundary/filesystem/clientLifecycle.test.ts (+1 -0)
➕ tests/boundary/filesystem/futureClientConfiguration.test.ts (+239 -0)

📄 Description

Summary

Adds FutureOS as a supported setup client so rea setup, rea doctor and
rea uninstall can create, report and remove the rea MCP registration in the
FutureOS server list, instead of the user hand-editing ~/.future/mcp.json.

Fixes #4426.

Problem and expected behavior

FutureOS was not among REA's supported clients. Its server list is close to
reachable with an existing dialect but not actually compatible with any of them:
FutureOS reads a servers table, denies unknown fields at both the root and the
entry, parses strictly, and defaults enabled to true. Registering with the
shape REA writes for VS Code/OMP/Pi would add type: "stdio", which makes
FutureOS refuse the whole file — REA would report the registration as aligned
while FutureOS loaded no servers at all.

Expected behavior: rea setup --client future writes servers.rea into
$FUTURE_HOME/mcp.json (~/.future/mcp.json by default), preserving other
servers; rea doctor --client future reports it; rea uninstall removes only
REA's entry and leaves a backup.

Change and scope

  • SupportedClients.ts: a future/FutureOS definition whose home resolves
    FUTURE_HOME only when it is absolute, matching FutureOS's own resolver. An
    empty or relative override falls back to ~/.future; resolving a relative
    value against REA's working directory would write a file FutureOS never reads.
  • ClientConfigurationDocument.ts: a future dialect. servers as the table
    key, strict JSON.parse with the empty-file fallback (no comments, trailing
    commas or BOM), and an entry of command/args/env/enabled with no
    type. A file FutureOS would reject is refused with a repair instruction
    rather than certified as aligned.
  • SetupClientConfiguration.ts: cwd, a caller-owned working directory for the
    server process, survives a launcher refresh. enabled: false on REA's entry is
    reported as stale and re-enabled on the next setup, following ZCode's
    enable: false repair rather than preserving a disabled entry.

Not included: a skillPath for this client, so --skill keeps installing
into the shared ~/.agents/skills. That is deliberate and is the one open
decision (see below). No analysis-provider or target-facing change.

Scope decision requested. Which skill root REA should own for FutureOS — the
shared ~/.agents/skills, or the client's app root <future home>/agent/skills,
which FutureOS resolves first and which alone follows FUTURE_HOME. This is the
same question #4402 is deciding for
DeepSeek Harness, so one answer should cover both; this branch takes the shared
root because that is what works today and what kimi, pi, qwen_code, codex, omp
and grok_build do. The precedent for adding a client this way is
#3041 (WorkBuddy,
#3040) — that one was a plain
definition because WorkBuddy reuses the json dialect; the new dialect is the
part that needs review here.

Contract and boundary impact

  • Semantic owner and earliest changed stage: client identity remains owned by
    SUPPORTED_CLIENT_DEFINITIONS; the document shape is owned by
    parseClientConfiguration/serializeClientConfiguration, extended with one
    dialect. Earliest changed stage is setup planning (a new --client value and
    a new detection marker).
  • Contribution scope fit and linked maintainer decision: a setup client
    definition, already an established contribution shape. The skill-destination
    scope decision above is requested, and #4402 covers the same boundary.
  • CLI and MCP/tool-catalog contract: adds the future value to --client,
    --skill-client and doctor --client, derived from the definition array. No
    tool contract change.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details: writes one
    user-owned configuration file and (with --skill) a skill directory; no target
    execution, no process control. No quitBeforeSetup: FutureOS loads the list on
    demand per CLI call. Uninstall removes only REA's entry and keeps a backup.
  • Generated metadata: docs/public/product-catalog.json regenerated (one new
    setup_clients entry); skills/ untouched.

Expected effects (known 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/filesystem/futureClientConfiguration.test.ts
    (location rules including relative/empty FUTURE_HOME, the exact entry shape,
    preserved cwd and sibling servers, disabled-entry staleness and repair,
    uninstall, marker detection, and the documents FutureOS rejects). The detection
    list in clientLifecycle.test.ts gains the client.

  • Base reproduction or other evidence: on the base revision, FutureOS is not a
    supported client (rea setup --client future is rejected as an unsupported
    agent integration) and no dialect produces a loadable entry, which the
    rejection tests below pin down.

  • User-visible CLI/MCP output: see validation below.

  • Remaining proof gaps: no full FutureOS agent session has driven a REA tool; no
    Windows run; npm run check:pr was not run.

  • 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

  • npm run check:fast — passed (typecheck, lint, pre-push check).
  • npm run docs:check — passed, including the generated product catalog and
    documentation fact checks.
  • npm run build:cached — passed.
  • All 35 client/setup boundary and acceptance suites with the product-catalog
    check — 567 tests passed.
  • rea setup --client future --yes in an isolated HOME — wrote
    {"servers":{"rea":{"command":"…/rea.mjs","args":["mcp"],"enabled":true}}}.
  • future mcp list with FUTURE_HOME pointed at that home — named the entry;
    future mcp tools rea returned REA's advertised 207-tool catalog;
    future mcp call rea list_documents reached REA and returned REA's own
    target_unavailable payload.
  • rea doctor --client future — registration:future healthy;
    rea setup --all-detected --dry-run — detected the client.
  • rea uninstall — removed only the rea entry, left mcp.json.rea.backup,
    and future mcp list then reported no configured servers.
  • The real FutureOS CLI was also used to establish the contract: it refused a
    root key other than servers, an entry key outside the five, a comment, a
    trailing comma and a BOM, and treated an empty file as "no servers
    configured".

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; no provider path
    changes. macOS 15 (arm64) only.
  • Package or release metadata impact: the client is not in the published
    rea-agents@6.5.0 package, so the supported-agents note records that it needs
    a later release.
  • Security, privacy, process, or containment review: writes one user config file
    (mode 0600, atomic, with a backup) and refuses files FutureOS itself would
    reject instead of overwriting them.

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/4427 **Author:** [@huichen](https://github.com/huichen) **Created:** 10/16/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/future-setup-client` --- ### 📝 Commits (2) - [`67100d6`](https://github.com/morluto/rea/commit/67100d6db8ff39a98524e3b9f51f46aabe5e3d6a) feat(setup): add FutureOS client support - [`19aaaa4`](https://github.com/morluto/rea/commit/19aaaa4ae8db3025aa81b225b81763815abc56af) docs(future): document the per-call connection the FutureOS CLI group gives REA ### 📊 Changes **7 files changed** (+407 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+69 -0) 📝 `docs/installation.md` (+3 -0) 📝 `src/application/ClientConfigurationDocument.ts` (+59 -2) 📝 `src/application/SetupClientConfiguration.ts` (+12 -0) 📝 `src/application/SupportedClients.ts` (+24 -0) 📝 `tests/boundary/filesystem/clientLifecycle.test.ts` (+1 -0) ➕ `tests/boundary/filesystem/futureClientConfiguration.test.ts` (+239 -0) </details> ### 📄 Description ## Summary Adds FutureOS as a supported setup client so `rea setup`, `rea doctor` and `rea uninstall` can create, report and remove the `rea` MCP registration in the FutureOS server list, instead of the user hand-editing `~/.future/mcp.json`. Fixes #4426. ## Problem and expected behavior FutureOS was not among REA's supported clients. Its server list is close to reachable with an existing dialect but not actually compatible with any of them: FutureOS reads a `servers` table, denies unknown fields at both the root and the entry, parses strictly, and defaults `enabled` to true. Registering with the shape REA writes for VS Code/OMP/Pi would add `type: "stdio"`, which makes FutureOS refuse the whole file — REA would report the registration as `aligned` while FutureOS loaded no servers at all. Expected behavior: `rea setup --client future` writes `servers.rea` into `$FUTURE_HOME/mcp.json` (`~/.future/mcp.json` by default), preserving other servers; `rea doctor --client future` reports it; `rea uninstall` removes only REA's entry and leaves a backup. ## Change and scope - `SupportedClients.ts`: a `future`/`FutureOS` definition whose home resolves `FUTURE_HOME` only when it is absolute, matching FutureOS's own resolver. An empty or relative override falls back to `~/.future`; resolving a relative value against REA's working directory would write a file FutureOS never reads. - `ClientConfigurationDocument.ts`: a `future` dialect. `servers` as the table key, strict `JSON.parse` with the empty-file fallback (no comments, trailing commas or BOM), and an entry of `command`/`args`/`env`/`enabled` with no `type`. A file FutureOS would reject is refused with a repair instruction rather than certified as aligned. - `SetupClientConfiguration.ts`: `cwd`, a caller-owned working directory for the server process, survives a launcher refresh. `enabled: false` on REA's entry is reported as stale and re-enabled on the next setup, following ZCode's `enable: false` repair rather than preserving a disabled entry. **Not included:** a `skillPath` for this client, so `--skill` keeps installing into the shared `~/.agents/skills`. That is deliberate and is the one open decision (see below). No analysis-provider or target-facing change. **Scope decision requested.** Which skill root REA should own for FutureOS — the shared `~/.agents/skills`, or the client's app root `<future home>/agent/skills`, which FutureOS resolves first and which alone follows `FUTURE_HOME`. This is the same question [#4402](https://github.com/morluto/rea/issues/4402) is deciding for DeepSeek Harness, so one answer should cover both; this branch takes the shared root because that is what works today and what kimi, pi, qwen_code, codex, omp and grok_build do. The precedent for adding a client this way is [#3041](https://github.com/morluto/rea/pull/3041) (WorkBuddy, [#3040](https://github.com/morluto/rea/issues/3040)) — that one was a plain definition because WorkBuddy reuses the `json` dialect; the new dialect is the part that needs review here. ## Contract and boundary impact - Semantic owner and earliest changed stage: client identity remains owned by `SUPPORTED_CLIENT_DEFINITIONS`; the document shape is owned by `parseClientConfiguration`/`serializeClientConfiguration`, extended with one dialect. Earliest changed stage is setup planning (a new `--client` value and a new detection marker). - Contribution scope fit and linked maintainer decision: a setup client definition, already an established contribution shape. The skill-destination scope decision above is requested, and #4402 covers the same boundary. - CLI and MCP/tool-catalog contract: adds the `future` value to `--client`, `--skill-client` and `doctor --client`, derived from the definition array. No tool contract change. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details: writes one user-owned configuration file and (with `--skill`) a skill directory; no target execution, no process control. No `quitBeforeSetup`: FutureOS loads the list on demand per CLI call. Uninstall removes only REA's entry and keeps a backup. - Generated metadata: `docs/public/product-catalog.json` regenerated (one new `setup_clients` entry); `skills/` untouched. Expected effects (known effects). - [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. ## Evidence and regression coverage - Tests added or updated: `tests/boundary/filesystem/futureClientConfiguration.test.ts` (location rules including relative/empty `FUTURE_HOME`, the exact entry shape, preserved `cwd` and sibling servers, disabled-entry staleness and repair, uninstall, marker detection, and the documents FutureOS rejects). The detection list in `clientLifecycle.test.ts` gains the client. - Base reproduction or other evidence: on the base revision, FutureOS is not a supported client (`rea setup --client future` is rejected as an unsupported agent integration) and no dialect produces a loadable entry, which the rejection tests below pin down. - User-visible CLI/MCP output: see validation below. - Remaining proof gaps: no full FutureOS agent session has driven a REA tool; no Windows run; `npm run check:pr` was not run. - [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 - `npm run check:fast` — passed (typecheck, lint, pre-push check). - `npm run docs:check` — passed, including the generated product catalog and documentation fact checks. - `npm run build:cached` — passed. - All 35 client/setup boundary and acceptance suites with the product-catalog check — 567 tests passed. - `rea setup --client future --yes` in an isolated `HOME` — wrote `{"servers":{"rea":{"command":"…/rea.mjs","args":["mcp"],"enabled":true}}}`. - `future mcp list` with `FUTURE_HOME` pointed at that home — named the entry; `future mcp tools rea` returned REA's advertised 207-tool catalog; `future mcp call rea list_documents` reached REA and returned REA's own `target_unavailable` payload. - `rea doctor --client future` — `registration:future` healthy; `rea setup --all-detected --dry-run` — detected the client. - `rea uninstall` — removed only the `rea` entry, left `mcp.json.rea.backup`, and `future mcp list` then reported no configured servers. - The real FutureOS CLI was also used to establish the contract: it refused a root key other than `servers`, an entry key outside the five, a comment, a trailing comma and a BOM, and treated an empty file as "no servers configured". ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; no provider path changes. macOS 15 (arm64) only. - Package or release metadata impact: the client is not in the published `rea-agents@6.5.0` package, so the supported-agents note records that it needs a later release. - Security, privacy, process, or containment review: writes one user config file (mode 0600, atomic, with a backup) and refuses files FutureOS itself would reject instead of overwriting them. ## 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`. - [ ] 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. --- <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#6234
No description provided.