cheatlabs/rea-runner repository overview

⁠CheatLabs REA Runner

A ready-to-run container for REA⁠ ([email protected]) with a pinned, checksum-verified Ghidra 12.1.4 and JDK 21. It exposes REA's MCP server over SSE (/sse, /message) on port 8765.

It is used by CheatLabs to let the AI find the memory anchors when a game build is not yet in the community profile vault. For single-player / offline games only.

⁠What's inside

• Ghidra 12.1.4 (headless), Temurin JDK 21, Node 22
• rea-agents 6.4.0, supergateway (stdio to SSE bridge)
• Runs as a non-root user. Not included: IDA and Hopper (commercial licences).

⁠Run

docker run --rm -p 127.0.0.1:8765:8765 \
  -v "/path/to/GameDir:/target:ro" \
  -v cheatlabs-rea-cache:/cache \
  cheatlabs/rea-runner:0.1.0

curl -N http://127.0.0.1:8765/sse    # first event: `endpoint`

Then add it to your CheatLabs client config.json:

{ "mcpServers": { "rea": { "command": "http://127.0.0.1:8765/sse" } } }

⁠Notes

• Mount only your game folder, read-only, at /target. Bind the port to 127.0.0.1.
• The first Ghidra analysis of an Unreal executable can take 30–90 minutes and 8–16 GB RAM.
• The image version (0.1.0, ...) is independent of the bundled rea-agents version.
• Experimental: not yet verified end-to-end against many games.

⁠Links

• Website: https://cheatlabs.de⁠
• Licenses: Ghidra (Apache-2.0), REA⁠, CheatLabs components as per the repo.