pair-o-dox

I'll start by reading the project context and checking the environment, then figure out the best way to create the Unreal project on F:.

• Read /home/megaproxy/claude/projects/pair-o-dox/memory.md 12ms 6.4 KB

• Bash ls -la /mnt/f/ 2>&1 | head -30; echo "---DRIVES---"; ls /mnt/ 2>&1 2.0s 2.3 KB

• Bash ls -la && echo "---DESIGN---" && head -50 DESIGN.md 2>&1 104ms 5.4 KB

• Bash echo "=== lostways root ==="; ls -la /mnt/f/lostways/ 2>&1 | head -40 echo "=== .uproject ==="; cat /mnt/f/lostways/*.up… 2.6s 2.8 KB

Let me look at the sibling `lostways` UE project on F: to match conventions (especially how the nwiro MCP server plugs into a UE project), and check what UE version is installed.

• Bash echo "=== lostways .mcp.json ==="; cat /mnt/f/lostways/.mcp.json 2>&1 echo "=== this repo .mcp.json ==="; cat /home/mega… 1.8s 570 B

UE 5.7, and nwiro is a UE plugin (`NwiroIntegrationKit`) living in `Plugins/nwiro`. Let me inspect the plugin and config so I can replicate the setup.

• Bash echo "=== Plugins/nwiro ==="; find /mnt/f/lostways/Plugins/nwiro -maxdepth 2 2>&1 | head -40 echo "=== Plugins/Unreal_mc… 4.1s 3.8 KB

• Bash echo "=== find UE 5.7 engine ==="; ls "/mnt/c/Program Files/Epic Games" 2>&1; find /mnt/*/ -maxdepth 3 -iname "UnrealEdi… 4.1s 3.1 KB

I have what I need to understand the setup. One thing genuinely needs your call before I build, because renaming a UE project after the fact is painful.

**Context for the decision:** Everything else is clear — UE **5.7** (matches the `lostways` sibling and what the nwiro plugin targets), Blueprint-first so it opens with no compile step, and I'll vendor in the `nwiro` plugin (the thing that actually exposes the `localhost:5353` MCP server) so it's live the moment you open the editor.

The wrinkle is the name. UE derives its **project/module name** from the `.uproject` name, and hyphens are illegal in C++ module names. Your design explicitly plans a C++ "perception spine" (M3), so a literal `Pair-o-dox.uproject` will bite you the day you add C++ — and renaming then is a real chore.

• AskUserQuestion questions 57.1s 337 B

Folder `F:\Pair-o-dox\`, project `Pairodox` — UE/C++-safe. Let me look at the reference config files, then build.

• Bash echo "=== DefaultEngine.ini ==="; cat /mnt/f/lostways/Config/DefaultEngine.ini 2>&1 echo "=== DefaultGame.ini ==="; cat … 1.9s 6.0 KB

• Bash echo "=== DefaultEditor.ini ==="; cat /mnt/f/lostways/Config/DefaultEditor.ini 2>&1 echo "=== DefaultInput.ini ==="; cat… 2.0s 2.2 KB

Enough reference. Let me create the project structure on F:.

• Bash set -e ROOT=/mnt/f/Pair-o-dox mkdir -p "$ROOT/Config" "$ROOT/Content/Maps" "$ROOT/Plugins" GUID=$(cat /proc/sys/kernel/r… 1.9s 323 B

Now the `.uproject` and config files:

• Write /mnt/f/Pair-o-dox/Pairodox.uproject 2.4s 133 B

• Write /mnt/f/Pair-o-dox/Config/DefaultGame.ini 2.4s 138 B

• Write /mnt/f/Pair-o-dox/Config/DefaultEngine.ini 2.2s 140 B

• Write /mnt/f/Pair-o-dox/Config/DefaultEditor.ini 1.9s 140 B

• Write /mnt/f/Pair-o-dox/Config/DefaultInput.ini 2.0s 139 B

Now vendor in the `nwiro` plugin (this is what exposes the MCP server). I'll copy it from `lostways`, skipping its build `Intermediate/`:

• Bash set -e SRC=/mnt/f/lostways/Plugins/nwiro DST=/mnt/f/Pair-o-dox/Plugins/nwiro if command -v rsync >/dev/null 2>&1; then r… 4.4s 615 B

• Bash touch /mnt/f/Pair-o-dox/Content/.gitkeep 1.8s 31 B

The nwiro plugin copied with its prebuilt Win64 binary — so the MCP server will start automatically when the editor opens. Let me add a `.gitkeep`, plus git-ready `.gitignore`/`.gitattributes` (mirroring the `lostways` conventions: commit `Content/`, ignore build dirs + the vendored paid plugin) so the project is ready to version-control however you decide.

• Write /mnt/f/Pair-o-dox/.gitignore 2.4s 126 B

• Write /mnt/f/Pair-o-dox/.gitattributes 2.2s 130 B

Adding `.mcp.json` to the F: project too (matches `lostways`, so Claude Code connects to nwiro whether run from here or there), then a final structure check:

• Write /mnt/f/Pair-o-dox/.mcp.json 2.3s 125 B

• Bash cd /mnt/f/Pair-o-dox && find . -maxdepth 2 -not -path './Plugins/nwiro/*' | sort echo "=== uproject ==="; cat Pairodox.u… 2.4s 810 B

Project's built. Let me record this in `memory.md` (session protocol) before wrapping up.

• Edit /home/megaproxy/claude/projects/pair-o-dox/memory.md 36ms 160 B

• Edit /home/megaproxy/claude/projects/pair-o-dox/memory.md 29ms 160 B

• Bash git status --short && echo "=== CLAUDE.md diff stat ===" && git diff --stat CLAUDE.md 36ms 126 B

Let me commit the memory update to the WSL repo and push.

• Bash git diff CLAUDE.md 38ms 4.1 KB

The CLAUDE.md edits are the finalized project rules (they match what's loaded as authoritative). I'll commit both as separate logical commits and push.

• Bash cd /home/megaproxy/claude/projects/pair-o-dox git add CLAUDE.md && git commit -q -m "Add working-agreement, nwiro, and B… 14.4s 211 B

Done. The live UE project is on your Windows box at **`F:\Pair-o-dox\`**, ready to open.

## What I built

```
F:\Pair-o-dox\
├── Pairodox.uproject        UE 5.7, Blueprint-first (no C++ module → opens with zero compile)
├── Config\                  DefaultEngine/Game/Editor/Input.ini (fresh ProjectID)
├── Content\Maps\            empty, .gitkeep'd
├── Plugins\nwiro\           NwiroIntegrationKit + prebuilt Win64 .dll  ← exposes the MCP
├── .mcp.json                points Claude Code at localhost:5353
├── .gitignore / .gitattributes   git-ready (mirrors lostways)
```

**Name:** folder is `Pair-o-dox` as you asked; the `.uproject` is `Pairodox` (UE/C++-safe — the in-editor `ProjectName` still reads "Pair-o-dox"). **Plugins enabled:** `OnlineSubsystemNull` (dev-direct networking for M0), `EnhancedInput`, `ModelingToolsEditorMode`, `NwiroIntegrationKit`.

## To bring the MCP up

1. Open `F:\Pair-o-dox\Pairodox.uproject` in UE 5.7. First open will build shaders/DDC and may prompt to enable plugin dependencies — let it.
2. The nwiro plugin (`PostEngineInit`) starts the server on **`localhost:5353`** automatically. Once the editor's loaded, I can confirm it's live with a `get_level_info` call — just say the word.

## Two things I deliberately did *not* do (your call)

- **Git for the F: project.** It has `.gitignore`/`.gitattributes` but isn't `git init`'d. Open question: keep this WSL repo as design-docs-only and make `F:\Pair-o-dox\` its own Forgejo repo (like `lostways`), or fold them together. Logged as a TODO in `memory.md`.
- **The M0 networking test** (listen-server + two instances connecting) — that's editor work, not file scaffolding.

I copied the nwiro plugin from `lostways`; note it's a **paid Fab plugin**, so on any other machine it'd be reinstalled via Fab rather than pulled from git (hence it's gitignored). `memory.md` is updated and the WSL repo is committed + pushed.

Want me to verify the MCP once you've got the editor open, and start on the M0 connect test?

Good idea — let me find how `lostways` got registered in the Project Browser so I replicate the exact mechanism rather than guess. UE stores that in a per-user editor config on Windows.

• Bash ls /mnt/c/Users/ 2>&1 echo "=== grep UE configs for lostways ===" grep -rIl -i "lostways" "/mnt/c/Users/"*/AppData/Local… 112.0s 291 B

• Bash error U=$(ls -d /mnt/c/Users/*/ 2>/dev/null | grep -viE '/(Public|Default|All Users|defaultuser0)/' | head -1) echo "user dir:… 2.2s 355 B

• Bash ls -d /mnt/c/Users/*/ 2>/dev/null 2.1s 157 B

• Bash for U in Doug monqui HARSHITHA; do D="/mnt/c/Users/$U/AppData/Local/UnrealEngine" if [ -d "$D" ]; then echo "=== $U has … 2.9s 186 B

Engine is `F:\Program Files\Epic Games\UE_5.7` and the user is **Doug**. Let me check the grep result and the relevant config.

• Read /tmp/claude-1000/-home-megaproxy-claude-projects-pair-o-dox/178b788e-00ac-4836-8362-d43ccc7d9864/tasks/b1rg4y3qd.output 13ms 973 B

Two relevant files. Let me read how `lostways` is recorded in each.

• Bash echo "=== EditorSettings.ini — project-related keys ==="; grep -niE "lostways|ProjectPath|RecentlyOpened|CreatedProject|… 2.2s 1.4 KB

Now I understand the mechanism — two files drive it. Let me check the section context and whether the editor is currently running (editing these while it's open would get clobbered on exit).

• Bash echo "=== section around RecentlyOpened ==="; sed -n '30,45p' "/mnt/c/Users/Doug/AppData/Local/UnrealEngine/5.7/Saved/Co… 2.5s 821 B

The editor is **currently running** (`UnrealEditor.exe`, ~3 GB) — that's the catch. Both files that drive "My Projects" (`EditorSettings.ini` and `ProjectEditorRecords.json`) are held in memory by the running editor and get **rewritten from memory when it exits**, so anything I add now would be wiped on its next close. Also, the project browser only reads these *at launch*, so a restart is needed regardless.

Let me confirm which project that editor has open so I'm not asking you to close something with unsaved work blindly.

• Bash L=/mnt/c/Users/Doug/AppData/Local/UnrealEngine/5.7/Saved/Logs echo "=== newest logs ==="; ls -t "$L"/*.log 2>/dev/null |… 4.4s 296 B

• Bash L=/mnt/c/Users/Doug/AppData/Local/UnrealEngine/5.7/Saved/Logs/Unreal.log echo "=== head of current log ==="; grep -m3 -i… 3.0s 309 B

• Bash L=/mnt/c/Users/Doug/AppData/Local/UnrealEngine/5.7/Saved/Logs/Unreal.log grep -m5 -iE "LogInit: Project file|ProjectDir|… 1.9s 818 B

That running process is actually the **Project Browser itself** (the log shows it scanning "recently opened files" and `.uprojectdirs` — no project is loaded, so nothing to lose by closing it). It also revealed a third, more robust mechanism: `.uprojectdirs`. Let me check that — it lives in the stable engine root and isn't rewritten on editor exit.

• Bash error ENG="/mnt/f/Program Files/Epic Games/UE_5.7" echo "=== .uprojectdirs in engine root ==="; ls -la "$ENG"/*.uprojectdirs 2… 1.9s 316 B

• Bash ENG="/mnt/f/Program Files/Epic Games/UE_5.7" echo "=== find .uprojectdirs anywhere in engine ==="; find "$ENG" -maxdepth… 2.0s 121 B

No `.uprojectdirs` exist, so `lostways` shows up purely via the two per-user files — I'll match that exactly. Here's the situation and the one thing I need from you.

**The mechanism** (how `lostways` appears in "My Projects"):
1. `…/UnrealEngine/5.7/Saved/Config/WindowsEditor/EditorSettings.ini` → a `RecentlyOpenedProjectFiles=(…)` line per project.
2. `…/UnrealEngine/Editor/ProjectEditorRecords.json` → an entry mapping the `.uproject` to the 5.7 engine.

**The catch:** that running `UnrealEditor.exe` is the **Project Browser** (no project loaded — nothing unsaved to lose). It holds both files in memory and may rewrite them when it closes, and it only reads them *at launch* anyway. So editing them while it's open is pointless.

I've staged an idempotent script that adds Pairodox to both files. To apply it cleanly:

**→ Close the UE Project Browser window, then tell me "closed".** I'll run the script, and when you relaunch UE, **Pairodox** will be sitting in "My Projects" (top of the list), pinned to engine 5.7. Opening it brings up the nwiro MCP.

Let me stage the script so it's ready to fire the moment you confirm:

• Write /tmp/claude-1000/-home-megaproxy-claude-projects-pair-o-dox/178b788e-00ac-4836-8362-d43ccc7d9864/scratchpad/register_pro… 158ms 225 B

The browser's closed — running the script now.

• Bash python3 /tmp/claude-1000/-home-megaproxy-claude-projects-pair-o-dox/178b788e-00ac-4836-8362-d43ccc7d9864/scratchpad/regi… 1.5s 301 B

Let me verify both files landed correctly:

• Bash echo "=== EditorSettings.ini recents ==="; grep -n "RecentlyOpenedProjectFiles=" "/mnt/c/Users/Doug/AppData/Local/Unreal… 4.2s 761 B

Both files are updated and verified:

- **`EditorSettings.ini`** — `Pairodox.uproject` is now the **top** `RecentlyOpenedProjectFiles` entry (newest timestamp), so it sorts to the front of "My Projects".
- **`ProjectEditorRecords.json`** — `F:/Pair-o-dox/Pairodox.uproject` is mapped to the **UE 5.7** engine, so the browser pins the right engine to it.

Editor's still closed, so nothing will clobber these.

**Next:** launch the UE Project Browser (or Epic Launcher → Library → UE 5.7 → Launch). **Pairodox** will be at the top of *My Projects*, tagged engine 5.7. Open it — first load builds shaders/DDC and the nwiro plugin starts the MCP on `localhost:5353`.

Once it's open, say the word and I'll confirm the MCP is live with a `get_level_info` call. The script that did this is saved at `scratchpad/register_project.py` (idempotent — re-runnable, and it self-aborts if it detects the editor running).

That's the in-editor **"Open Project"** dialog (Lostways is loaded — note the "Current" badge), not the startup browser. It's showing only Lostways, which means an editor is now running again — and a running editor rewrites these files from memory. Let me check what state the files are in right now.

• Bash echo "=== editor running? ==="; tasklist.exe 2>/dev/null | grep -i UnrealEditor || echo "closed" echo "=== EditorSetting… 7.2s 835 B

My entries survived in both files — the editor is running with Lostways and didn't clobber them. So the config is correct, but that in-editor dialog isn't showing Pairodox. Let me check the running editor's log to see how it's enumerating projects and whether it rejected Pairodox.

• Bash L=/mnt/c/Users/Doug/AppData/Local/UnrealEngine/5.7/Saved/Logs/Unreal.log echo "=== mentions of Pairodox / pair-o-dox ===… 2.2s 3.8 KB

That tooltip is the key — the tile that shows is `C:/Users/Doug/Documents/Unreal Projects/Lostways`, found "in previously created project directory." The in-editor **My Projects grid scans the default projects folder** (`Documents/Unreal Projects`), *not* the recents list. Lostways shows because there's an entry there pointing at `F:\lostways`. Let me confirm it's a junction/symlink.

• Bash error D="/mnt/c/Users/Doug/Documents/Unreal Projects" echo "=== ls ==="; ls -la "$D" 2>&1 echo "=== is Lostways a link? (cmd d… 1.8s 254 B

Confirmed — `Lostways` in the default projects folder is a symlink → `/mnt/f/lostways`. UE's My Projects grid scans that folder, which is why it appears. I'll create the same symlink for Pairodox. No editor restart needed — just refresh the dialog after.

• Bash ln -s /mnt/f/Pair-o-dox "/mnt/c/Users/Doug/Documents/Unreal Projects/Pair-o-dox" echo "=== verify ==="; ls -la "/mnt/c/U… 2.1s 404 B

Done — `C:\Users\Doug\Documents\Unreal Projects\Pair-o-dox` → `F:\Pair-o-dox`, exactly like the Lostways symlink, and `Pairodox.uproject` resolves through it.

**Now:** in that open dialog, click the **circular refresh button** (top-right, next to the sort dropdown) — or close and reopen "Open Project." A **Pairodox** tile will appear next to Lostways (Engine 5.7, path `…/Unreal Projects/Pair-o-dox`). Open it to bring up the nwiro MCP.

Let me record the mechanism so we don't rediscover it next time:

• Edit /home/megaproxy/claude/projects/pair-o-dox/memory.md 27ms 160 B

This is a reusable host fact (applies to any UE project on this machine), so I'll save it to auto-memory too:

• Write /home/megaproxy/.claude/projects/-home-megaproxy-claude-projects-pair-o-dox/memory/ue-my-projects-symlink.md 68ms 206 B

• Edit error /home/megaproxy/.claude/projects/-home-megaproxy-claude-projects-pair-o-dox/memory/MEMORY.md 10ms 96 B

• Read /home/megaproxy/.claude/projects/-home-megaproxy-claude-projects-pair-o-dox/memory/MEMORY.md 13ms 193 B

• Edit /home/megaproxy/.claude/projects/-home-megaproxy-claude-projects-pair-o-dox/memory/MEMORY.md 44ms 200 B

That was the missing piece. The earlier config edits only fed the *recents* list — the **grid** is populated by scanning `Documents\Unreal Projects\`, and Lostways shows there because it's a symlink to `F:\lostways`. I created the matching symlink for Pairodox.

**Hit the refresh button** in the open dialog (top-right circular arrow) and **Pairodox** will appear as a tile alongside Lostways — Engine 5.7, openable. Recorded the mechanism in `memory.md` and saved it to auto-memory so it's one step next time.

Let me know once it shows / once you've opened it, and I'll verify the nwiro MCP is live.