Skip to content

Rephrased Agent Architecture

Lead-facing. Other disciplines do not need this page. Engineers talk normally in their coding agent (Cursor, Claude Code, Codex, Antigravity, or another MCP-capable IDE); the agent is supposed to run the harness without anyone naming tools.

1. Design goals

  • Clone + /onboard is enough. No per-person agent profile.
  • After work: convention check → human compile → server-side review → human PIE → devlog → commit.
  • Advisory Git hooks remind; they never block.
  • Unreal MCP (5.8) is suggested editor reach. It does not replace Rephrased MCP.

2. Architecture overview

Engineer: "fix the overlap" / "what should I work on?" / "load Rune Showcase"
IDE (Cursor / Claude Code / Codex / Antigravity / other MCP)
    ├── Rephrased MCP (always)     wiki, convention_check, request_review, devlog
    └── Unreal MCP (editor open)   maps, assets, actors, PIE start/stop

Shared toolkit: tools/rephrased-mcp/. Shipped configs: .cursor/mcp.json and .claude/mcp.json (rephrased only). Other IDEs get the same JSON. Suggested unreal-mcp on port 6388 is added for editor tools.

3. Review gate

  1. convention_check — C++ diff vs UE conventions in AGENTS.md
  2. Compile — human, Development Editor | Win64
  3. request_review — Source/ C++, Config/ text, Content/ asset+map paths → team review server (Rephrased-design review LLM)
  4. PIE — human
  5. devlog — then commit

Hooks under scripts/git-hooks/ remind on commit/push (exit 0). Enable via MCP onboarding or scripts/Install-ReviewHook.ps1.

4. What engineers see vs what agents see

Engineers Agents (must call, unprompted)
Clone, /onboard, build, PIE onboarding
Speak in normal language wiki_query before doc-dependent decisions
convention_check then request_review before commit
devlog after meaningful C++ / systems work
Suggested Unreal MCP while the editor is running

Do not add a skill-name checklist to first-day docs. If a skill file exists on a lead machine, it is backup — MCP is the path.

5. Engineer daily loop

git clone <repo>
uv tool install tools/rephrased-mcp
# MCP config: .cursor/mcp.json, .claude/mcp.json, or paste the same block — then /onboard

git pull
# work in Source/ / Content/
# In chat: done / help me commit  →  agent runs the gate

6. Lead view

  1. Break milestones into tracked work items (team board / lead)
  2. Assign owners
  3. Review PRs into main
  4. Escalate blocks in Discord

7. Coding-agent fit

Agent Notes
Cursor .cursor/mcp.json
Claude Code .claude/mcp.json
Codex Same MCP JSON in Codex settings. AGENTS.md
Antigravity Same MCP JSON in Antigravity settings. AGENTS.md
Others Same MCP if the IDE can run it. Do not invent a second pipeline.

8. Status

  • [x] Local Rephrased MCP
  • [x] Onboarding (review key + git hooks)
  • [x] convention_check + request_review (Source/ + Config/ + Content/ paths)
  • [x] Advisory Git hooks
  • [x] Unreal MCP on 5.8 (port 6388), verified PIE start on Rune Showcase

Change history

  • 2026-08-14 — Gabriel Li — Review gate names the team review server, not a vendor model; harness list includes Codex and Antigravity; Unreal MCP labeled suggested.
  • 2026-08-13 — Gabriel Li — Invisible-harness rewrite; Unreal MCP + port 6388; review covers Content/Config; skills off the engineer path.
  • 2026-08-10 — Gabriel Li — English rewrite; aligned with shipped MCP toolkit and Source/-scoped review.
  • 2026-07-10 — Gabriel Li — V2 draft: shared pipeline (not profile-per-role), Claude Code agents sketch.
  • 2026-07-10 — Gabriel Li — Initial draft (profile-based architecture, deprecated).