morluto/rea

Fork 0

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

[GH-ISSUE #6015] Add puku-cli as a supported client in rea setup #3673

New issue

Closed

opened 2026-10-31 00:42:57 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-31 00:42:57 +00:00

Owner

Originally created by @mohammadirfan90 on GitHub (Oct 21, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/6015

Feature request: add puku-cli as a supported client

Summary

rea setup should recognize puku-cli as a supported agent so that running
rea setup --all-detected will register the REA MCP server, install the
reverse-engineer-anything skill, and produce the same managed configuration
that Claude Code, Codex, Cursor, etc., get today.

Motivation

puku-cli is an AI coding harness (MCP-aware, multi-model) used in the same
role as Claude Code or Codex for software-engineering work. Today, REA's
setup wizard does not list puku-cli among its supported clients (verified on
rea-agents 6.7.0; supported list at the time of writing: claude_code,
claude_desktop, codex, commandcode, cursor, copilot_cli, devin,
droid, dsh, gemini_cli, grok_bot, grok_build, hermes, kimi,
omp, opencode, pi, qoder, qwen_code, trae, vscode, windsurf,
workbuddy, zcode).

Users who want REA on puku-cli have to wire it up by hand:

Edit ~/.puku-cli/.mcp.json to add the rea server entry.
Copy skills/reverse-engineer-anything/ from the npm package into
~/.puku-cli/skills/reverse-engineer-anything/.

Both steps are documented in puku-cli's baseline skill-path rules
(puku-cli requires SKILL.md files to live under .puku-cli/skills/<name>/
or ~/.puku-cli/skills/<name>/).

This works, but it is a manual workaround every puku-cli user has to
discover. Adding puku-cli as a first-class client would make the standard
npx rea-agents setup flow work the same as it does for Claude Code,
including --all-detected, backups, and updates via rea update.

puku-cli specifics

Item	Value
MCP config path	`~/.puku-cli/.mcp.json` (project-level: `.puku-cli/.mcp.json`)
MCP config format	Same as Claude Code: top-level `mcpServers` map of `{command, args}`
Skill path	`~/.puku-cli/skills/<skill-name>/SKILL.md` (project-level: `.puku-cli/skills/<skill-name>/SKILL.md`)
Skill frontmatter	YAML frontmatter with `name`, `description`, optional `metadata`
References dir	`~/.puku-cli/skills/<skill-name>/references/*.md` (linked from SKILL.md)
Detection marker	Existence of `~/.puku-cli/` directory containing a `settings.json` or `puku-cli.json`

Example MCP entry (what `rea setup` should produce)

{
  "mcpServers": {
    "rea": {
      "command": "rea",
      "args": ["mcp"]
    }
  }
}

This matches the JSON shape REA already emits for claude_code /
vscode / cursor (mcpServers.<name>.command + .args).

Example skill install (what `rea setup` should produce)

~/.puku-cli/skills/reverse-engineer-anything/SKILL.md
~/.puku-cli/skills/reverse-engineer-anything/references/android-applications.md
~/.puku-cli/skills/reverse-engineer-anything/references/connection-and-recovery.md
~/.puku-cli/skills/reverse-engineer-anything/references/evidence-workflows.md
~/.puku-cli/skills/reverse-engineer-anything/references/javascript-applications.md
~/.puku-cli/skills/reverse-engineer-anything/references/native-and-artifacts.md
~/.puku-cli/skills/reverse-engineer-anything/references/runtime-observation.md

These are the literal files shipped in
node_modules/rea-agents/skills/reverse-engineer-anything/ of the
rea-agents npm package — no reformatting needed; puku-cli accepts the same
YAML-frontmatter SKILL.md format that Claude Code uses.

Proposed implementation

In the same place where the existing clients are registered inside the
rea-agents package, add a puku_cli entry roughly equivalent to the
claude_code entry, but pointing at puku-cli's paths:

configPath: ~/.puku-cli/.mcp.json
format: same JSON mcpServers schema as claude_code /
vscode / cursor (so the existing JSON writer should work as-is)
markerPath: ~/.puku-cli
Detection: ~/.puku-cli directory containing settings.json or
puku-cli.json
displayName: "Puku CLI"
Skill destination: ~/.puku-cli/skills/ (default; project-level is
optional, and puku-cli also accepts <repo>/.puku-cli/skills/)

Update docs/installation.md to list puku-cli in the Supported
agents section, with the two paths above.

Verified workaround

I've validated the manual workaround on Windows 11 / Node 24.11 with
rea-agents 6.7.0:

npm install --global rea-agents@latest (installs rea to PATH).

Add to ~/.puku-cli/.mcp.json:

{ "mcpServers": { "rea": { "command": "rea", "args": ["mcp"] } } }

Copy node_modules/rea-agents/skills/reverse-engineer-anything/* to
~/.puku-cli/skills/reverse-engineer-anything/.
Restart puku-cli. The 207 REA tools are exposed via MCP, and the
reverse-engineer-anything skill is loaded. REA's doctor reports
node/host healthy; native-engine checks remain opt-in.

Adding native support would just let users skip steps 2–3 and rely on the
uninstall/update flows.

Environment

puku-cli (latest)
Node.js v24.11.0
rea-agents 6.7.0 (Windows 11)

Originally created by @mohammadirfan90 on GitHub (Oct 21, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/6015 # Feature request: add puku-cli as a supported client ## Summary `rea setup` should recognize **puku-cli** as a supported agent so that running `rea setup --all-detected` will register the REA MCP server, install the `reverse-engineer-anything` skill, and produce the same managed configuration that Claude Code, Codex, Cursor, etc., get today. ## Motivation puku-cli is an AI coding harness (MCP-aware, multi-model) used in the same role as Claude Code or Codex for software-engineering work. Today, REA's setup wizard does not list puku-cli among its supported clients (verified on rea-agents 6.7.0; supported list at the time of writing: `claude_code`, `claude_desktop`, `codex`, `commandcode`, `cursor`, `copilot_cli`, `devin`, `droid`, `dsh`, `gemini_cli`, `grok_bot`, `grok_build`, `hermes`, `kimi`, `omp`, `opencode`, `pi`, `qoder`, `qwen_code`, `trae`, `vscode`, `windsurf`, `workbuddy`, `zcode`). Users who want REA on puku-cli have to wire it up by hand: 1. Edit `~/.puku-cli/.mcp.json` to add the `rea` server entry. 2. Copy `skills/reverse-engineer-anything/` from the npm package into `~/.puku-cli/skills/reverse-engineer-anything/`. Both steps are documented in puku-cli's baseline skill-path rules (`puku-cli` requires SKILL.md files to live under `.puku-cli/skills/<name>/` or `~/.puku-cli/skills/<name>/`). This works, but it is a manual workaround every puku-cli user has to discover. Adding puku-cli as a first-class client would make the standard `npx rea-agents setup` flow work the same as it does for Claude Code, including `--all-detected`, backups, and updates via `rea update`. ## puku-cli specifics | Item | Value | | ----------------- | -------------------------------------------------------------------- | | MCP config path | `~/.puku-cli/.mcp.json` (project-level: `.puku-cli/.mcp.json`) | | MCP config format | Same as Claude Code: top-level `mcpServers` map of `{command, args}` | | Skill path | `~/.puku-cli/skills/<skill-name>/SKILL.md` (project-level: `.puku-cli/skills/<skill-name>/SKILL.md`) | | Skill frontmatter | YAML frontmatter with `name`, `description`, optional `metadata` | | References dir | `~/.puku-cli/skills/<skill-name>/references/*.md` (linked from SKILL.md) | | Detection marker | Existence of `~/.puku-cli/` directory containing a `settings.json` or `puku-cli.json` | ### Example MCP entry (what `rea setup` should produce) ```json { "mcpServers": { "rea": { "command": "rea", "args": ["mcp"] } } } ``` This matches the JSON shape REA already emits for `claude_code` / `vscode` / `cursor` (`mcpServers.<name>.command` + `.args`). ### Example skill install (what `rea setup` should produce) ```text ~/.puku-cli/skills/reverse-engineer-anything/SKILL.md ~/.puku-cli/skills/reverse-engineer-anything/references/android-applications.md ~/.puku-cli/skills/reverse-engineer-anything/references/connection-and-recovery.md ~/.puku-cli/skills/reverse-engineer-anything/references/evidence-workflows.md ~/.puku-cli/skills/reverse-engineer-anything/references/javascript-applications.md ~/.puku-cli/skills/reverse-engineer-anything/references/native-and-artifacts.md ~/.puku-cli/skills/reverse-engineer-anything/references/runtime-observation.md ``` These are the literal files shipped in `node_modules/rea-agents/skills/reverse-engineer-anything/` of the rea-agents npm package — no reformatting needed; puku-cli accepts the same YAML-frontmatter SKILL.md format that Claude Code uses. ## Proposed implementation In the same place where the existing clients are registered inside the `rea-agents` package, add a `puku_cli` entry roughly equivalent to the `claude_code` entry, but pointing at puku-cli's paths: - `configPath`: `~/.puku-cli/.mcp.json` - `format`: same JSON `mcpServers` schema as `claude_code` / `vscode` / `cursor` (so the existing JSON writer should work as-is) - `markerPath`: `~/.puku-cli` - Detection: `~/.puku-cli` directory containing `settings.json` or `puku-cli.json` - `displayName`: "Puku CLI" - Skill destination: `~/.puku-cli/skills/` (default; project-level is optional, and puku-cli also accepts `<repo>/.puku-cli/skills/`) Update `docs/installation.md` to list `puku-cli` in the **Supported agents** section, with the two paths above. ## Verified workaround I've validated the manual workaround on Windows 11 / Node 24.11 with rea-agents 6.7.0: 1. `npm install --global rea-agents@latest` (installs `rea` to PATH). 2. Add to `~/.puku-cli/.mcp.json`: ```json { "mcpServers": { "rea": { "command": "rea", "args": ["mcp"] } } } ``` 3. Copy `node_modules/rea-agents/skills/reverse-engineer-anything/*` to `~/.puku-cli/skills/reverse-engineer-anything/`. 4. Restart puku-cli. The 207 REA tools are exposed via MCP, and the `reverse-engineer-anything` skill is loaded. REA's `doctor` reports node/host healthy; native-engine checks remain opt-in. Adding native support would just let users skip steps 2–3 and rely on the uninstall/update flows. ## Environment - puku-cli (latest) - Node.js v24.11.0 - rea-agents 6.7.0 (Windows 11)

bsakaguchi closed this issue

2026-10-31 00:42:57 +00:00

bsakaguchi referenced this issue

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

[GH-ISSUE #3796] [Tracker] Open feature requests by area (October 2026) #1471

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

No description provided.

Rows
Columns