[PR #4326] [CLOSED] docs(setup): avoid npm launchers for concurrent MCP sessions #6173

New issue

Closed

opened 2026-10-31 01:12:25 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 01:12:25 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/4326
Author: @leeguooooo
Created: 10/16/2026
Status: ❌ Closed

Base: main ← Head: docs/direct-mcp-launcher

📝 Commits (1)

3e93180 docs(setup): 说明多会话直接启动以减少 npm 驻留

📊 Changes

1 file changed (+15 additions, -0 deletions)

View changed files

📝 docs/installation.md (+15 -0)

📄 Description

npx keeps an npm launcher alongside every REA MCP process. The existing global installation can avoid it, but the guide does not explain that rea setup must be rerun directly and affected clients restarted. Add that path and explain its update behavior. Documentation only; no launcher or session semantics change.

Verified with REA 6.5.0 on macOS arm64 / Node 24.18.0: isolated-home setup wrote the installed entrypoint plus mcp; three alternating initialize/list-tools runs had identical catalogs. Direct launch removed one npm process and about 37 MiB of retained JS heap per connection. This does not remove REA's own per-connection memory.

Measurement limits

Fresh processes with cached packages; filesystem caches were not flushed. Median completed startup/list time: 3,735 → 2,221 ms; process-family CPU: 2,554 → 1,737 ms; sampled peak family RSS: 485 → 402 MiB. Short-idle family footprint after diagnostic GC: 535 → 389 MiB. Samples are host-dependent, not a long-running memory or physical-RAM saving guarantee. Agent token usage was not measured; catalog bytes were unchanged. No external analysis engine was exercised.

Validation: npm run docs:check passed, including five README consistency tests. npm run check also passed.

Author readiness

Human owner: @leeguooooo

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.

_{🔄 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/4326 **Author:** [@leeguooooo](https://github.com/leeguooooo) **Created:** 10/16/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/direct-mcp-launcher` --- ### 📝 Commits (1) - [`3e93180`](https://github.com/morluto/rea/commit/3e9318044b7894dec307f7d1372b87e5d1388b14) docs(setup): 说明多会话直接启动以减少 npm 驻留 ### 📊 Changes **1 file changed** (+15 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+15 -0) </details> ### 📄 Description `npx` keeps an npm launcher alongside every REA MCP process. The existing global installation can avoid it, but the guide does not explain that `rea setup` must be rerun directly and affected clients restarted. Add that path and explain its update behavior. Documentation only; no launcher or session semantics change. Verified with REA 6.5.0 on macOS arm64 / Node 24.18.0: isolated-home setup wrote the installed entrypoint plus `mcp`; three alternating initialize/list-tools runs had identical catalogs. Direct launch removed one npm process and about 37 MiB of retained JS heap per connection. This does not remove REA's own per-connection memory. <details> <summary>Measurement limits</summary> Fresh processes with cached packages; filesystem caches were not flushed. Median completed startup/list time: 3,735 → 2,221 ms; process-family CPU: 2,554 → 1,737 ms; sampled peak family RSS: 485 → 402 MiB. Short-idle family footprint after diagnostic GC: 535 → 389 MiB. Samples are host-dependent, not a long-running memory or physical-RAM saving guarantee. Agent token usage was not measured; catalog bytes were unchanged. No external analysis engine was exercised. </details> Validation: `npm run docs:check` passed, including five README consistency tests. `npm run check` also passed. ## Author readiness Human owner: @leeguooooo - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-31 01:12:25 +00:00

closed this issue
added the
pull-request
label

bsakaguchi referenced this issue

2026-11-01 21:45:58 +00:00

[PR #6173] [MERGED] fix(process): capture MCP process scenarios with the server environment #7183

No milestone

No project

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#6173

No description provided.

Rows
Columns