Install System requirements, building Cluewren from source, and connecting your coding agent.
Engines Plugin installation and configuration for Unity, Godot, and Unreal Engine.
First run Start a playtest session with your coding agent, submit requests, and inspect run artifacts.
Engines
Section titled “Engines”- Unity: Installing the package from git or disk, bridge connection, and engine conventions.
- Godot: Installing the addon in addons/, debugger relay, and node paths.
- Unreal Engine: Installing the plugin for C++ or Blueprint-only projects, socket architecture, and actor paths.
Guides
Section titled “Guides”- Writing requests: Request kinds, time limits and budgets, and report requirements.
- Decision model key: Configuring the TypeSafe API key in keys.env and what is sent to Jev.
How it works
Section titled “How it works”- Overview: What Cluewren is, audience, request kinds, and run artifacts.
- Architecture: Component coordination, bridge security, and child process isolation.
- Privacy: Local data boundaries, retained project memory, and outbound network traffic.
- Harness sandbox: Windows AppContainer isolation, execution limits, and plain child process fallback.
Reference
Section titled “Reference”- CLI: Command reference for connect, mcp, and run, along with exit codes.
- Harness kit: The Cluewren.Kit library, Game methods, movement controllers, and supporting types.