[GH-ISSUE #1257] Support OMP (oh-my-pi) in rea setup client integrations #453

New issue

Closed

opened 2026-10-15 18:25:11 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-15 18:25:11 +00:00

Owner

Originally created by @wlndysky on GitHub (Oct 9, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/1257

Feature request: add OMP to `rea setup` client integrations

What: Add OMP (oh-my-pi) (omp.sh) to the agents that rea setup can detect and configure.

Why: OMP is a terminal coding agent used by many binary and reverse-engineering developers — it ships with a built-in IDA Pro integration (headless idalib workers), binary analysis tooling, and a skills system, so its user base overlaps heavily with REA's target audience. REA's MCP tools are a natural fit for OMP-driven reverse-engineering workflows, and today OMP is the one agent in my toolchain that rea setup cannot register automatically.

Integration details (verified on Windows 11, rea-agents 6.1.0):

User-level MCP config: ~/.omp/agent/mcp.json — plain JSON with a top-level mcpServers map. The canonical manual registration from docs/installation.md#mcp-registry works as-is; on Windows the npx shim is conventionally wrapped, the same shape rea setup itself writes for Codex:
```
"rea": {
  "type": "stdio",
  "command": "cmd",
  "args": ["/c", "npx", "-y", "rea-agents@6.1.0", "mcp"],
  "env": {}
}
```
(type and env are optional OMP-side fields; command: "npx" directly works on POSIX.)
Project-level config: <project>/.mcp.json is also loaded (mcp.enableProjectConfig), same mcpServers schema.
Detection marker: the ~/.omp directory (agent state lives under ~/.omp/agent/).
Skill support: OMP already discovers user skills from ~/.agents/skills, so the reverse-engineer-anything skill installed by rea setup is picked up natively — only the MCP registration step is missing.
Alternative: since REA is published in the official MCP Registry as io.github.morluto/rea, registry discovery may also be a viable path for OMP.
Verified working: with the registration above, a fresh OMP session completes the MCP initialize handshake (serverInfo: rea@6.1.0) and mounts all 138 REA tools.

Suggested client entry:

Field	Value
name	`omp`
displayName	`OMP`
configPath	`~/.omp/agent/mcp.json`
markerPath	`~/.omp`
format	`json`

Happy to test a build on Windows if you add it.

Originally created by @wlndysky on GitHub (Oct 9, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/1257 ## Feature request: add OMP to `rea setup` client integrations **What:** Add [OMP (oh-my-pi)](https://github.com/can1357/oh-my-pi) ([omp.sh](https://omp.sh)) to the agents that `rea setup` can detect and configure. **Why:** OMP is a terminal coding agent used by many binary and reverse-engineering developers — it ships with a built-in IDA Pro integration (headless idalib workers), binary analysis tooling, and a skills system, so its user base overlaps heavily with REA's target audience. REA's MCP tools are a natural fit for OMP-driven reverse-engineering workflows, and today OMP is the one agent in my toolchain that `rea setup` cannot register automatically. **Integration details (verified on Windows 11, rea-agents 6.1.0):** - **User-level MCP config:** `~/.omp/agent/mcp.json` — plain JSON with a top-level `mcpServers` map. The canonical manual registration from `docs/installation.md#mcp-registry` works as-is; on Windows the `npx` shim is conventionally wrapped, the same shape `rea setup` itself writes for Codex: ```json "rea": { "type": "stdio", "command": "cmd", "args": ["/c", "npx", "-y", "rea-agents@6.1.0", "mcp"], "env": {} } ``` (`type` and `env` are optional OMP-side fields; `command: "npx"` directly works on POSIX.) - **Project-level config:** `<project>/.mcp.json` is also loaded (`mcp.enableProjectConfig`), same `mcpServers` schema. - **Detection marker:** the `~/.omp` directory (agent state lives under `~/.omp/agent/`). - **Skill support:** OMP already discovers user skills from `~/.agents/skills`, so the `reverse-engineer-anything` skill installed by `rea setup` is picked up natively — only the MCP registration step is missing. - **Alternative:** since REA is published in the official MCP Registry as `io.github.morluto/rea`, registry discovery may also be a viable path for OMP. - **Verified working:** with the registration above, a fresh OMP session completes the MCP `initialize` handshake (`serverInfo: rea@6.1.0`) and mounts all 138 REA tools. **Suggested client entry:** | Field | Value | |---|---| | name | `omp` | | displayName | `OMP` | | configPath | `~/.omp/agent/mcp.json` | | markerPath | `~/.omp` | | format | `json` | Happy to test a build on Windows if you add it.

bsakaguchi

2026-10-15 18:25:11 +00:00

closed this issue
added the
area: setup

enhancement
labels

bsakaguchi commented

2026-10-15 18:25:11 +00:00

Author

Owner

@kaoru0822-kitauji commented on GitHub (Oct 9, 2026):

#1301 adds --client omp. It writes a type: "stdio" entry to ~/.omp/agent/mcp.json (or the PI_CONFIG_DIR / absolute PI_CODING_AGENT_DIR / OMP_PROFILE location, resolved the way OMP's dirs.ts does). It also removes rea from disabledServers if it's listed there. On Windows, setup writes the same cmd.exe /d /c npx … wrapper it uses for the other clients. If you can try npx -y rea-agents@<next> setup --client omp on Windows once it's released, that would confirm the live OMP session; I could only check the file shape against OMP's mcp-schema.json here.

@kaoru0822-kitauji commented on GitHub (Oct 9, 2026): #1301 adds `--client omp`. It writes a `type: "stdio"` entry to `~/.omp/agent/mcp.json` (or the `PI_CONFIG_DIR` / absolute `PI_CODING_AGENT_DIR` / `OMP_PROFILE` location, resolved the way OMP's `dirs.ts` does). It also removes `rea` from `disabledServers` if it's listed there. On Windows, setup writes the same `cmd.exe /d /c npx …` wrapper it uses for the other clients. If you can try `npx -y rea-agents@<next> setup --client omp` on Windows once it's released, that would confirm the live OMP session; I could only check the file shape against OMP's `mcp-schema.json` here.

bsakaguchi referenced this issue

2026-10-16 21:13:14 +00:00

[PR #453] [MERGED] feat(process): replace procfs sampling with event-backed process-tree capture #2000

bsakaguchi added

enhancement

and removed

enhancement

labels

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