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 #3968] feat(setup): add MiniMax Code client #5971

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

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/3968
Author: @hetaoBackend
Created: 10/15/2026
Status: 🔄 Open

Base: main ← Head: feat/minimax-code-client

📝 Commits (4)

  • eaa5b83 feat(setup): add MiniMax Code client
  • d6f979c fix(setup): align MiniMax Code client with review
  • 833d745 Merge remote-tracking branch 'origin/main' into feat/minimax-code-client
  • 3228033 fix(setup): address MiniMax Code client review nits

📊 Changes

6 files changed (+218 additions, -0 deletions)

View changed files

📝 docs/client-configuration.md (+15 -0)
📝 docs/installation.md (+3 -0)
📝 src/application/SupportedClients.ts (+16 -0)
📝 tests/boundary/filesystem/clientLifecycle.test.ts (+1 -0)
➕ tests/boundary/filesystem/minimaxCodeClientConfiguration.test.ts (+181 -0)
📝 tests/fixtures/clientEnvironment.ts (+2 -0)

📄 Description

Summary

Adds MiniMax Code (CLI mcode) as a setup client. npx rea-agents setup --client minimax_code registers REA's MCP server and installs the REA skill. Before this change, setup did not know about MiniMax Code and users had to register REA by hand.

No issue is linked. None exists; this is a small client addition that reuses the existing json format.

Problem and expected behavior

MiniMax Code reads a plain mcpServers JSON file and SKILL.md skill directories, but setup does not detect it. With this change, setup detects ~/.minimax, upserts mcpServers.rea into ~/.minimax/mcp.json (other servers and top-level keys are kept), and copies the skill to ~/.minimax/skills/reverse-engineer-anything. When MINIMAX_DATA_DIR (or, failing that, MAVIS_DATA_DIR) is set, setup uses that directory instead of ~/.minimax.

Change and scope

  • src/application/SupportedClients.ts: new minimax_code entry using the existing json format, same shape as WorkBuddy, placed between WorkBuddy and Grok Build. No new dialect. The data directory is MINIMAX_DATA_DIR, then MAVIS_DATA_DIR, then ~/.minimax, matching MiniMax Code's own resolution (getExplicitPublicDataDirEnv in packages/config/src/config.ts). An empty value counts as unset; values are not trimmed, like the Codex and Qoder helpers.
  • Paths come from MiniMax Code source: data dir ~/.minimax (packages/config/src/data-dir.ts), profile MCP file <dataDir>/mcp.json (packages/local-runtime-v2/src/service/mcp/runtime/local-mcp.service.ts), user skills <dataDir>/skills (packages/local-runtime/src/skills/roots.ts).
  • Docs: a row in the docs/installation.md client table, a note that minimax_code needs a release after 6.7.0, and a MiniMax Code section in docs/client-configuration.md.
  • Tests: MAVIS_DATA_DIR and MINIMAX_DATA_DIR are added to the fixture that clears client env, and minimax_code is added to the client order in the lifecycle test.
  • Not included: the project-level <workspace>/.mcp.json (left untouched, as for other clients), named profiles (~/.minimax-<profile>) and the legacy ~/.mavis directory. The last two are follow-ups.

Follow the contribution scope.
Unresolved scope, authority, side effects, or required verification block
integration. Link the required maintainer scope decision for new providers or
capabilities involving target execution, injection, mutation, or protection
recovery; ordinary fixes within existing boundaries may state "not applicable".
Draft PRs may leave the scope decision pending and the readiness and merge checklists
unchecked. Maintainers can help resolve open questions.

This is a setup client addition within existing boundaries. It adds no provider and no target interaction, so a maintainer scope decision is not applicable.

Contract and boundary impact

  • Semantic owner and earliest changed stage: setup client catalog (SupportedClients.ts).
  • Contribution scope fit and linked maintainer decision: setup client addition within existing boundaries; not applicable.
  • CLI and MCP/tool-catalog contract: adds one --client value, minimax_code. No tool changes.
  • Provider, bridge, target-format, or platform compatibility: none.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. Uninstall removes only the rea entry and the REA skill copy.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: the generated product catalog picks up the new client ID; no build outputs are committed. Installation docs gain one table row and a version note.

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.

Setup writes mcpServers.rea into MiniMax Code's mcp.json (with a mcp.json.rea.backup) and copies the REA skill into its skills directory.

Evidence and regression coverage

  • Tests added or updated: new tests/boundary/filesystem/minimaxCodeClientConfiguration.test.ts (8 tests) covers the default paths on Linux, macOS and Windows; the json format; MINIMAX_DATA_DIR before MAVIS_DATA_DIR before the home default, an empty value falling back, and the skill path under the override; upsert that keeps other servers; an existing file with no servers table; an empty file; and uninstall that removes only rea. clientLifecycle.test.ts includes minimax_code in its client order. tests/fixtures/clientEnvironment.ts clears both new variables.
  • Base reproduction or other evidence: executed. On main, minimax_code is not a known client ID, so setup cannot register REA for MiniMax Code. The evidence below was run on the updated head after merging current main.
  • User-visible CLI/MCP output (if applicable): rea setup --client minimax_code --yes plans configure_client:minimax_code targeting <HOME>/.minimax/mcp.json with backup <HOME>/.minimax/mcp.json.rea.backup, plus install_skill:minimax_code. rea doctor --client minimax_code --json then reports registration:minimax_code as healthy.
  • Remaining proof gaps: not yet checked in a running MiniMax Code session (loading the registration and making real REA tool calls). The /mcp reload advice and the MiniMax Code paths come from reading MiniMax Code source.

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.

Not an evidence-bearing change; these do not apply.

Validation performed

All on head 3228033 (current main merged in), Node 22.20.0, Linux (Debian 13).

  • npx vitest run tests/boundary/filesystem/minimaxCodeClientConfiguration.test.ts tests/boundary/filesystem/clientLifecycle.test.ts: 2 files, 70/70 passed.
  • npx vitest run tests/boundary/filesystem/productCatalog.test.ts tests/boundary/filesystem/documentationFacts.test.ts tests/conformance/readmeConsistency.test.ts tests/boundary/filesystem/workbuddyClientConfiguration.test.ts: passed (catalog and docs checks, including the client table).
  • npm run verify:test-discovery: "Discovered all 2106 test files exactly once."
  • npm run typecheck (tsc --noEmit): clean.
  • npx oxfmt --check .: clean.
  • npx oxlint: exit 0; the only output is existing max-depth warnings in scripts/ci/plan.mjs, none in changed files. npm run verify:module-boundaries: passed.
  • npm run build: passed.
  • Built CLI, temporary HOME with an existing ~/.minimax/mcp.json holding another server and a top-level key: rea setup --client minimax_code --yes exits 0, adds mcpServers.rea while keeping the other server and key, writes mcp.json.rea.backup, and installs skills/reverse-engineer-anything. rea doctor --client minimax_code --json reports registration:minimax_code healthy. The registered command answers MCP initialize (serverInfo rea).
  • Built CLI, empty temporary HOME with MINIMAX_DATA_DIR set: setup exits 0, writes mcp.json and skills/reverse-engineer-anything under that directory, and writes nothing under HOME.

Compatibility, safety, and release

  • Breaking changes or migration steps: none. Adds a client ID; existing clients are unchanged.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable. Path resolution is unit-tested for Linux, macOS and Windows; end-to-end setup ran on Linux only.
  • Package or release metadata impact: minimax_code is not in rea-agents@6.7.0 or earlier; docs/installation.md says it needs the first release after 6.7.0.
  • Security, privacy, process, or containment review: setup writes only MiniMax Code's user-level mcp.json (with a backup) and the skill directory, and preserves unrelated configuration. It does not touch project-level .mcp.json.

Author readiness

Human owner: @hetaoBackend

  • 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.

Follow-ups

  • Detect named profiles (~/.minimax-<profile>).
  • Detect the legacy ~/.mavis directory.

🔄 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/3968 **Author:** [@hetaoBackend](https://github.com/hetaoBackend) **Created:** 10/15/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `feat/minimax-code-client` --- ### 📝 Commits (4) - [`eaa5b83`](https://github.com/morluto/rea/commit/eaa5b837dff34272790f06d91998f2fd4e59fa0d) feat(setup): add MiniMax Code client - [`d6f979c`](https://github.com/morluto/rea/commit/d6f979cb268a42b7fccced6cf0eaa6b632d1d9d8) fix(setup): align MiniMax Code client with review - [`833d745`](https://github.com/morluto/rea/commit/833d745b29a7ba1fd9cb5123ad3f987ecd06952b) Merge remote-tracking branch 'origin/main' into feat/minimax-code-client - [`3228033`](https://github.com/morluto/rea/commit/3228033080b0175756a3feb58da58b3f55e6d3b5) fix(setup): address MiniMax Code client review nits ### 📊 Changes **6 files changed** (+218 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+15 -0) 📝 `docs/installation.md` (+3 -0) 📝 `src/application/SupportedClients.ts` (+16 -0) 📝 `tests/boundary/filesystem/clientLifecycle.test.ts` (+1 -0) ➕ `tests/boundary/filesystem/minimaxCodeClientConfiguration.test.ts` (+181 -0) 📝 `tests/fixtures/clientEnvironment.ts` (+2 -0) </details> ### 📄 Description ## Summary Adds [MiniMax Code](https://github.com/MiniMax-AI/minimax-code) (CLI `mcode`) as a setup client. `npx rea-agents setup --client minimax_code` registers REA's MCP server and installs the REA skill. Before this change, setup did not know about MiniMax Code and users had to register REA by hand. No issue is linked. None exists; this is a small client addition that reuses the existing `json` format. ## Problem and expected behavior MiniMax Code reads a plain `mcpServers` JSON file and `SKILL.md` skill directories, but setup does not detect it. With this change, setup detects `~/.minimax`, upserts `mcpServers.rea` into `~/.minimax/mcp.json` (other servers and top-level keys are kept), and copies the skill to `~/.minimax/skills/reverse-engineer-anything`. When `MINIMAX_DATA_DIR` (or, failing that, `MAVIS_DATA_DIR`) is set, setup uses that directory instead of `~/.minimax`. ## Change and scope - `src/application/SupportedClients.ts`: new `minimax_code` entry using the existing `json` format, same shape as WorkBuddy, placed between WorkBuddy and Grok Build. No new dialect. The data directory is `MINIMAX_DATA_DIR`, then `MAVIS_DATA_DIR`, then `~/.minimax`, matching MiniMax Code's own resolution (`getExplicitPublicDataDirEnv` in `packages/config/src/config.ts`). An empty value counts as unset; values are not trimmed, like the Codex and Qoder helpers. - Paths come from MiniMax Code source: data dir `~/.minimax` (`packages/config/src/data-dir.ts`), profile MCP file `<dataDir>/mcp.json` (`packages/local-runtime-v2/src/service/mcp/runtime/local-mcp.service.ts`), user skills `<dataDir>/skills` (`packages/local-runtime/src/skills/roots.ts`). - Docs: a row in the `docs/installation.md` client table, a note that `minimax_code` needs a release after 6.7.0, and a MiniMax Code section in `docs/client-configuration.md`. - Tests: `MAVIS_DATA_DIR` and `MINIMAX_DATA_DIR` are added to the fixture that clears client env, and `minimax_code` is added to the client order in the lifecycle test. - Not included: the project-level `<workspace>/.mcp.json` (left untouched, as for other clients), named profiles (`~/.minimax-<profile>`) and the legacy `~/.mavis` directory. The last two are follow-ups. Follow the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope). Unresolved scope, authority, side effects, or required verification block integration. Link the required maintainer scope decision for new providers or capabilities involving target execution, injection, mutation, or protection recovery; ordinary fixes within existing boundaries may state "not applicable". Draft PRs may leave the scope decision pending and the readiness and merge checklists unchecked. Maintainers can help resolve open questions. This is a setup client addition within existing boundaries. It adds no provider and no target interaction, so a maintainer scope decision is not applicable. ## Contract and boundary impact - Semantic owner and earliest changed stage: setup client catalog (`SupportedClients.ts`). - Contribution scope fit and linked maintainer decision: setup client addition within existing boundaries; not applicable. - CLI and MCP/tool-catalog contract: adds one `--client` value, `minimax_code`. No tool changes. - Provider, bridge, target-format, or platform compatibility: none. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. Uninstall removes only the `rea` entry and the REA skill copy. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: the generated product catalog picks up the new client ID; no build outputs are committed. Installation docs gain one table row and a version note. 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. - [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. Setup writes `mcpServers.rea` into MiniMax Code's `mcp.json` (with a `mcp.json.rea.backup`) and copies the REA skill into its `skills` directory. ## Evidence and regression coverage - Tests added or updated: new `tests/boundary/filesystem/minimaxCodeClientConfiguration.test.ts` (8 tests) covers the default paths on Linux, macOS and Windows; the `json` format; `MINIMAX_DATA_DIR` before `MAVIS_DATA_DIR` before the home default, an empty value falling back, and the skill path under the override; upsert that keeps other servers; an existing file with no servers table; an empty file; and uninstall that removes only `rea`. `clientLifecycle.test.ts` includes `minimax_code` in its client order. `tests/fixtures/clientEnvironment.ts` clears both new variables. - Base reproduction or other evidence: executed. On main, `minimax_code` is not a known client ID, so setup cannot register REA for MiniMax Code. The evidence below was run on the updated head after merging current main. - User-visible CLI/MCP output (if applicable): `rea setup --client minimax_code --yes` plans `configure_client:minimax_code` targeting `<HOME>/.minimax/mcp.json` with backup `<HOME>/.minimax/mcp.json.rea.backup`, plus `install_skill:minimax_code`. `rea doctor --client minimax_code --json` then reports `registration:minimax_code` as `healthy`. - Remaining proof gaps: not yet checked in a running MiniMax Code session (loading the registration and making real REA tool calls). The `/mcp reload` advice and the MiniMax Code paths come from reading MiniMax Code source. 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. Not an evidence-bearing change; these do not apply. ## Validation performed All on head 3228033 (current main merged in), Node 22.20.0, Linux (Debian 13). - `npx vitest run tests/boundary/filesystem/minimaxCodeClientConfiguration.test.ts tests/boundary/filesystem/clientLifecycle.test.ts`: 2 files, 70/70 passed. - `npx vitest run tests/boundary/filesystem/productCatalog.test.ts tests/boundary/filesystem/documentationFacts.test.ts tests/conformance/readmeConsistency.test.ts tests/boundary/filesystem/workbuddyClientConfiguration.test.ts`: passed (catalog and docs checks, including the client table). - `npm run verify:test-discovery`: "Discovered all 2106 test files exactly once." - `npm run typecheck` (`tsc --noEmit`): clean. - `npx oxfmt --check .`: clean. - `npx oxlint`: exit 0; the only output is existing `max-depth` warnings in `scripts/ci/plan.mjs`, none in changed files. `npm run verify:module-boundaries`: passed. - `npm run build`: passed. - Built CLI, temporary `HOME` with an existing `~/.minimax/mcp.json` holding another server and a top-level key: `rea setup --client minimax_code --yes` exits 0, adds `mcpServers.rea` while keeping the other server and key, writes `mcp.json.rea.backup`, and installs `skills/reverse-engineer-anything`. `rea doctor --client minimax_code --json` reports `registration:minimax_code` healthy. The registered command answers MCP `initialize` (`serverInfo` `rea`). - Built CLI, empty temporary `HOME` with `MINIMAX_DATA_DIR` set: setup exits 0, writes `mcp.json` and `skills/reverse-engineer-anything` under that directory, and writes nothing under `HOME`. ## Compatibility, safety, and release - Breaking changes or migration steps: none. Adds a client ID; existing clients are unchanged. - Real Hopper/Ghidra, browser, or OS coverage: not applicable. Path resolution is unit-tested for Linux, macOS and Windows; end-to-end setup ran on Linux only. - Package or release metadata impact: `minimax_code` is not in `rea-agents@6.7.0` or earlier; `docs/installation.md` says it needs the first release after 6.7.0. - Security, privacy, process, or containment review: setup writes only MiniMax Code's user-level `mcp.json` (with a backup) and the skill directory, and preserves unrelated configuration. It does not touch project-level `.mcp.json`. ## Author readiness <!-- The human owner completes these declarations before requesting review. The PR author is the owner by default. A different owner must explicitly accept ownership on this PR. AI agents must leave these declarations to a human to dictate to them or there could be catastrophic consequences for many users of REA. Draft PRs may leave them unchecked. These declarations record initial readiness when opening the PR for review; later pushes do not require a new human sign-off. Keep the description and validation evidence current as the work changes. See CONTRIBUTING.md#pull-request-ownership-and-readiness. --> Human owner: @hetaoBackend - [ ] 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. ## Follow-ups - Detect named profiles (`~/.minimax-<profile>`). - Detect the legacy `~/.mavis` directory. --- <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#5971
No description provided.