morluto/rea

Fork 0

mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00

[GH-ISSUE #7650] [Bug] Client configuration reference omits Cursor, Windsurf, and Command Code MCP entries #4575

New issue

Open

opened 2026-10-31 00:50:55 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:50:55 +00:00

Owner

Originally created by @coygeek on GitHub (Oct 28, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7650

Before submitting

I searched the open and closed issues for a related report.
I removed credentials, tokens, private paths, and sensitive target data.

Area

Documentation

Observed behavior

The client configuration reference provides no MCP configuration filename or REA entry key for Cursor, Windsurf, or Command Code. Searching the entire reference for their setup IDs returns no matches, although the installation guide lists all three as supported and directs readers to that reference for configuration paths.

I ran node scripts/rea.mjs setup --client <id> --dry-run --json for each ID in an isolated environment. All three succeeded and showed configuration targets. Applying setup with --skill=false --yes --json wrote valid JSON at each target, with REA under mcpServers.rea. The missing text concerns working integrations; this is not a demonstrated setup failure.

Reproduction

From the already-built baseline checkout, run:
```
grep -n -i -E 'cursor|windsurf|commandcode' docs/client-configuration.md
grep -n -i -E 'cursor|windsurf|commandcode|configuration paths' docs/installation.md
```
The first search returns no output and exits 1. The installation search finds their supported-client rows and the statement directing readers to the configuration reference.

With Node.js v24.22.1 first on PATH, run this isolated check. Its local package-tool fixtures prevent package acquisition; its temporary homes and written configurations are removed on exit.

python3 -I - <<'PYTHON'
import json, os, shutil, subprocess, tempfile
from pathlib import Path

node = shutil.which("node")
with tempfile.TemporaryDirectory(prefix="rea-reference-check-") as directory:
    base = Path(directory)
    (base / "bin").mkdir()
    (base / "temp").mkdir()
    for name in ("npx", "npm", "bun"):
        fixture = base / "bin" / name
        fixture.write_text("#!/bin/sh\nprintf '6.8.0\\n'\n")
        fixture.chmod(0o755)
    for client in ("cursor", "windsurf", "commandcode"):
        home = base / client
        home.mkdir()
        env = {"PATH": f"{base / 'bin'}:{Path(node).parent}:{os.defpath}",
               "HOME": str(home), "TMPDIR": str(base / "temp"),
               "npm_config_cache": str(home / "npm-cache")}
        for kind in ("CONFIG", "DATA", "CACHE", "STATE"):
            env[f"XDG_{kind}_HOME"] = str(home / kind.lower())
        def rea(*args):
            return json.loads(subprocess.check_output(
                [node, "scripts/rea.mjs", *args], env=env, text=True,
                timeout=90))
        plan = rea("setup", "--client", client, "--dry-run", "--json")
        action = next(a for a in plan["plannedActions"]
                      if a["kind"] == "configure_client")
        target = Path(action["target"])
        applied = rea("setup", "--client", client, "--skill=false",
                      "--yes", "--json")
        config = json.loads(target.read_text())
        print(client, plan["status"], applied["status"],
              target.relative_to(home),
              "mcpServers.rea:", "rea" in config.get("mcpServers", {}))
PYTHON

The documentation searches and the setup/readback checks reproduced the mismatch. The combined script was also run once separately and returned the output below.

Expected behavior

The linked client configuration reference should identify the configuration files and REA registration keys for these supported integrations, or point to instructions that do. Its launcher-recovery procedure asks readers to back up their client configuration and change only the runtime command while preserving the remaining entry. Naming the file and entry makes that procedure usable directly from the reference.

This expectation is based on the reference's stated purpose and the installation guide's link description; it does not imply that every supported client needs identical troubleshooting advice.

Impact and scope

P3: the demonstrated defect is missing configuration-reference text for three supported integrations. No failed native-client connection, incorrect manual edit, or inability to complete setup was observed.

The installation guide makes their IDs discoverable, but its table does not supply their MCP filenames or registration keys. A practical workaround is the documented setup dry run: its plan reveals the relevant filename without writing a configuration. The applied readback confirmed the entry key for each tested client.

REA version

Exact stdout from node scripts/rea.mjs --version:

6.8.0

Source baseline: 65f1c447344a423fa2785847dbcea1e9a9e2454a.

Runtime and platform

Node.js v24.22.1; Darwin 27.0.0; arm64. The existing built checkout was used. No native client session or analysis provider was launched.

Interface

Package or setup

Earliest failure stage

Unknown

Relevant output or evidence

The isolated script prints paths relative to each disposable home:

cursor planned ready .cursor/mcp.json mcpServers.rea: True
windsurf planned ready .codeium/windsurf/mcp_config.json mcpServers.rea: True
commandcode planned ready .commandcode/mcp.json mcpServers.rea: True

At the reported baseline:

docs/client-configuration.md:1-7 states the reference's purpose; lines 29-35 describe the manual launcher repair. A whole-file search finds none of the three client IDs.
docs/installation.md:620,622,627 lists these clients, and lines 648-649 promise configuration-path guidance in the linked reference. Other occurrences are a Cursor setup example and an unrelated cursor-navigation sentence, not per-client configuration details.
docs/client-verification.md:209-218 discusses running the Command Code verification lane and its account configuration directory, without identifying its MCP filename or REA key.
src/application/SupportedClients.ts:549-553,568-573,607-613 defines the tested setup destinations. The public CLI runs and JSON readback above establish that these definitions are reachable and used.

Additional context

Related closed #1522, open #7640, and open #4451 concern supported-client ID omissions in skill instructions. Updating those lists would not provide the missing configuration-reference entries reported here.

Antigravity has a similar omission at this baseline, but open #5145 already proposes text naming its MCP file and mcpServers.rea key. This report excludes that overlap. Merged #645 describes Command Code's path in its implementation discussion; that information is absent from the linked user reference.

Originally created by @coygeek on GitHub (Oct 28, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7650 ### Before submitting - [x] I searched the open and closed issues for a related report. - [x] I removed credentials, tokens, private paths, and sensitive target data. ### Area Documentation ### Observed behavior The client configuration reference provides no MCP configuration filename or REA entry key for Cursor, Windsurf, or Command Code. Searching the entire reference for their setup IDs returns no matches, although the installation guide lists all three as supported and directs readers to that reference for configuration paths. I ran `node scripts/rea.mjs setup --client <id> --dry-run --json` for each ID in an isolated environment. All three succeeded and showed configuration targets. Applying setup with `--skill=false --yes --json` wrote valid JSON at each target, with REA under `mcpServers.rea`. The missing text concerns working integrations; this is not a demonstrated setup failure. ### Reproduction 1. From the already-built baseline checkout, run: ```sh grep -n -i -E 'cursor|windsurf|commandcode' docs/client-configuration.md grep -n -i -E 'cursor|windsurf|commandcode|configuration paths' docs/installation.md ``` The first search returns no output and exits 1. The installation search finds their supported-client rows and the statement directing readers to the configuration reference. 2. With Node.js v24.22.1 first on PATH, run this isolated check. Its local package-tool fixtures prevent package acquisition; its temporary homes and written configurations are removed on exit. ```sh python3 -I - <<'PYTHON' import json, os, shutil, subprocess, tempfile from pathlib import Path node = shutil.which("node") with tempfile.TemporaryDirectory(prefix="rea-reference-check-") as directory: base = Path(directory) (base / "bin").mkdir() (base / "temp").mkdir() for name in ("npx", "npm", "bun"): fixture = base / "bin" / name fixture.write_text("#!/bin/sh\nprintf '6.8.0\\n'\n") fixture.chmod(0o755) for client in ("cursor", "windsurf", "commandcode"): home = base / client home.mkdir() env = {"PATH": f"{base / 'bin'}:{Path(node).parent}:{os.defpath}", "HOME": str(home), "TMPDIR": str(base / "temp"), "npm_config_cache": str(home / "npm-cache")} for kind in ("CONFIG", "DATA", "CACHE", "STATE"): env[f"XDG_{kind}_HOME"] = str(home / kind.lower()) def rea(*args): return json.loads(subprocess.check_output( [node, "scripts/rea.mjs", *args], env=env, text=True, timeout=90)) plan = rea("setup", "--client", client, "--dry-run", "--json") action = next(a for a in plan["plannedActions"] if a["kind"] == "configure_client") target = Path(action["target"]) applied = rea("setup", "--client", client, "--skill=false", "--yes", "--json") config = json.loads(target.read_text()) print(client, plan["status"], applied["status"], target.relative_to(home), "mcpServers.rea:", "rea" in config.get("mcpServers", {})) PYTHON ``` The documentation searches and the setup/readback checks reproduced the mismatch. The combined script was also run once separately and returned the output below. ### Expected behavior The linked client configuration reference should identify the configuration files and REA registration keys for these supported integrations, or point to instructions that do. Its launcher-recovery procedure asks readers to back up their client configuration and change only the runtime command while preserving the remaining entry. Naming the file and entry makes that procedure usable directly from the reference. This expectation is based on the reference's stated purpose and the installation guide's link description; it does not imply that every supported client needs identical troubleshooting advice. ### Impact and scope P3: the demonstrated defect is missing configuration-reference text for three supported integrations. No failed native-client connection, incorrect manual edit, or inability to complete setup was observed. The installation guide makes their IDs discoverable, but its table does not supply their MCP filenames or registration keys. A practical workaround is the documented setup dry run: its plan reveals the relevant filename without writing a configuration. The applied readback confirmed the entry key for each tested client. ### REA version Exact stdout from `node scripts/rea.mjs --version`: ```text 6.8.0 ``` Source baseline: `65f1c447344a423fa2785847dbcea1e9a9e2454a`. ### Runtime and platform Node.js v24.22.1; Darwin 27.0.0; arm64. The existing built checkout was used. No native client session or analysis provider was launched. ### Interface Package or setup ### Earliest failure stage Unknown ### Relevant output or evidence The isolated script prints paths relative to each disposable home: ```text cursor planned ready .cursor/mcp.json mcpServers.rea: True windsurf planned ready .codeium/windsurf/mcp_config.json mcpServers.rea: True commandcode planned ready .commandcode/mcp.json mcpServers.rea: True ``` At the reported baseline: - `docs/client-configuration.md:1-7` states the reference's purpose; lines 29-35 describe the manual launcher repair. A whole-file search finds none of the three client IDs. - `docs/installation.md:620,622,627` lists these clients, and lines 648-649 promise configuration-path guidance in the linked reference. Other occurrences are a Cursor setup example and an unrelated cursor-navigation sentence, not per-client configuration details. - `docs/client-verification.md:209-218` discusses running the Command Code verification lane and its account configuration directory, without identifying its MCP filename or REA key. - `src/application/SupportedClients.ts:549-553,568-573,607-613` defines the tested setup destinations. The public CLI runs and JSON readback above establish that these definitions are reachable and used. ### Additional context Related closed [#1522](https://github.com/morluto/rea/issues/1522), open [#7640](https://github.com/morluto/rea/issues/7640), and open [#4451](https://github.com/morluto/rea/pull/4451) concern supported-client ID omissions in skill instructions. Updating those lists would not provide the missing configuration-reference entries reported here. Antigravity has a similar omission at this baseline, but open [#5145](https://github.com/morluto/rea/pull/5145) already proposes text naming its MCP file and `mcpServers.rea` key. This report excludes that overlap. Merged [#645](https://github.com/morluto/rea/pull/645) describes Command Code's path in its implementation discussion; that information is absent from the linked user reference.

bsakaguchi referenced this issue

2026-10-31 01:13:34 +00:00

[PR #4587] [CLOSED] fix(process): handle disappearing symlinks during filesystem snapshot (#4575) #6324

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

No description provided.

Rows
Columns