morluto/rea

Fork 0

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

[GH-ISSUE #2490] [Feature] Support CodeBuddy as a setup client #827

New issue

Open

opened 2026-10-15 18:28:48 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:28:48 +00:00

Owner

Originally created by @cainiao1992 on GitHub (Oct 13, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/2490

Before submitting

I searched the open and closed issues and pull requests for a related proposal.
I understand the contribution scope must be reviewed before integration; open questions are welcome here.
This request does not include credentials, private samples, or sensitive target data.

Area

MCP or agent integration

Current limitation

CodeBuddy is not among REA's supported setup clients, so CodeBuddy users must hand-edit the global ~/.codebuddy/mcp.json to add the rea MCP entry and copy the skill manually. rea setup, rea doctor, and rea uninstall are unaware of CodeBuddy, so the registration cannot be created, refreshed, or removed through the managed lifecycle.

Use cases

Run rea setup --client codebuddy (or plain rea setup with ~/.codebuddy present) and get the rea MCP server plus the bundled skill installed for CodeBuddy.
Have rea doctor report and rea uninstall remove the CodeBuddy registration like any other supported agent.

Desired outcome and success criteria

rea setup --client codebuddy writes mcpServers.rea into the global ~/.codebuddy/mcp.json (standard mcpServers JSON, stdio transport), preserving existing servers and top-level keys, and installs the bundled skill under ~/.codebuddy/skills. The documentation lists CodeBuddy in the supported-agents table.

Expected interaction with targets

No target interaction (documentation or usability only)

Target and scope details (optional)

Setup only writes the user's local CodeBuddy configuration file when the user opts in; no analysis provider or target-facing behavior changes.

Verification available so far

I have a prototype or observed results

Verification details (optional)

A working branch adds a codebuddy entry to SUPPORTED_CLIENT_DEFINITIONS (mirroring the Cursor json-dialect entry plus a skill path) with boundary tests for path resolution, upsert preserving unrelated entries, registration into existing/empty configs, and uninstall removing only rea. Targeted tests, doc-fact checks, and the generated product-catalog consistency check pass locally; setup --client codebuddy --yes was exercised end-to-end in an isolated HOME and produced the expected mcp.json and skill directory.

Alternatives considered

Hand-editing ~/.codebuddy/mcp.json (the current workaround) or wrapping the npx launch in an alias — both leave setup/doctor/uninstall unaware of the client and lose refresh and cleanup.

Possible direction

Add codebuddy to SUPPORTED_CLIENT_DEFINITIONS: configPath: [".codebuddy", "mcp.json"], markerPath: [".codebuddy"], skillPath: [".codebuddy", "skills"], format: "json". The --client allowlist, detection, registration, uninstall, and the generated product catalog all derive from this array, so no other CLI changes are needed.

References

CodeBuddy global MCP configuration uses the standard mcpServers schema in ~/.codebuddy/mcp.json.

Originally created by @cainiao1992 on GitHub (Oct 13, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/2490 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This request does not include credentials, private samples, or sensitive target data. ### Area MCP or agent integration ### Current limitation CodeBuddy is not among REA's supported setup clients, so CodeBuddy users must hand-edit the global `~/.codebuddy/mcp.json` to add the `rea` MCP entry and copy the skill manually. `rea setup`, `rea doctor`, and `rea uninstall` are unaware of CodeBuddy, so the registration cannot be created, refreshed, or removed through the managed lifecycle. ### Use cases - Run `rea setup --client codebuddy` (or plain `rea setup` with `~/.codebuddy` present) and get the `rea` MCP server plus the bundled skill installed for CodeBuddy. - Have `rea doctor` report and `rea uninstall` remove the CodeBuddy registration like any other supported agent. ### Desired outcome and success criteria `rea setup --client codebuddy` writes `mcpServers.rea` into the global `~/.codebuddy/mcp.json` (standard `mcpServers` JSON, stdio transport), preserving existing servers and top-level keys, and installs the bundled skill under `~/.codebuddy/skills`. The documentation lists CodeBuddy in the supported-agents table. ### Expected interaction with targets - No target interaction (documentation or usability only) ### Target and scope details (optional) Setup only writes the user's local CodeBuddy configuration file when the user opts in; no analysis provider or target-facing behavior changes. ### Verification available so far I have a prototype or observed results ### Verification details (optional) A working branch adds a `codebuddy` entry to `SUPPORTED_CLIENT_DEFINITIONS` (mirroring the Cursor `json`-dialect entry plus a skill path) with boundary tests for path resolution, upsert preserving unrelated entries, registration into existing/empty configs, and uninstall removing only `rea`. Targeted tests, doc-fact checks, and the generated product-catalog consistency check pass locally; `setup --client codebuddy --yes` was exercised end-to-end in an isolated HOME and produced the expected `mcp.json` and skill directory. ### Alternatives considered Hand-editing `~/.codebuddy/mcp.json` (the current workaround) or wrapping the npx launch in an alias — both leave setup/doctor/uninstall unaware of the client and lose refresh and cleanup. ### Possible direction Add `codebuddy` to `SUPPORTED_CLIENT_DEFINITIONS`: `configPath: [".codebuddy", "mcp.json"]`, `markerPath: [".codebuddy"]`, `skillPath: [".codebuddy", "skills"]`, `format: "json"`. The `--client` allowlist, detection, registration, uninstall, and the generated product catalog all derive from this array, so no other CLI changes are needed. ### References - CodeBuddy global MCP configuration uses the standard `mcpServers` schema in `~/.codebuddy/mcp.json`.

bsakaguchi added the

area: setup

enhancement

labels

2026-10-15 18:28:48 +00:00

bsakaguchi commented

2026-10-15 18:28:49 +00:00

Author

Owner

@Rickeal-Boss commented on GitHub (Oct 13, 2026):

By the way, please support WorkBuddy and WorkBuddy AI as a setup client. @morluto

@Rickeal-Boss commented on GitHub (Oct 13, 2026): By the way, please support WorkBuddy and WorkBuddy AI as a setup client. @morluto

bsakaguchi referenced this issue

2026-10-16 21:02:34 +00:00

[GH-ISSUE #2383] [Tracker] Audit analysis and debugging coverage for the TIOBE top 100 languages (October 2026) #794

bsakaguchi referenced this issue

2026-10-16 21:16:46 +00:00

[PR #848] [MERGED] feat(javascript): recover readable modules with Wakaru #2286

bsakaguchi added

enhancement

and removed

enhancement

labels

2026-10-31 00:29:43 +00:00