AI-first · multiplayer by design · data-oriented · ray-traced
Quickstart · Why Mirai · Docs · Contribute
Mirai is a native 3D engine and editor where people and AI agents build the same game, in the same scene, at the same time. Connect your favorite agent inside the editor, or connect it externally via MCP or JSON-RPC.
- Agents live in the editor. Claude, Codex or any ACP agent opens a chat next to the viewport. Several run at once, each one a figure next to what it is working on.
- Everything is an API. The editor serves JSON-RPC and MCP with the same methods a person uses: build scenes, edit materials, play, capture frames, etc.
- You stay in control. Each agent change is attributed and outlined in the scene. Accept it, revert it or retry it.
- Errors that teach. Invalid input never crashes the engine: it returns what failed and how to fix it, so an agent can correct itself.
- Multiplayer editing. Share your session and your team can join with an invitation code. Everyone sees everyone in the scene: people and their agents.
- Multiplayer games, first-party. Authoritative server, client prediction, rollback, lag compensation, delta replication and dedicated servers, with networked Play inside the editor.
- It sees what you see. An agent captures the editor with its UI or the game frame by frame, so you can point at a glitch instead of describing it.
- It plays the game itself. In its own copy of your Play, an agent presses actions, advances exact ticks and checks the result.
- It reads your game while you play. Entities, components, the player and what failed and why, live, without stopping you.
- Rewind. Every Play keeps its recent past. Pause, scrub back to the moment it went wrong, inspect or fix the world there and play on from that frame. Agents can jump to any tick too.
- A game is data and functions. Components and storages are flat structs; loop functions declare in their signature exactly what they read and write.
- ECS, not OOP. No classes, no inheritance trees, no virtual
Update()on every object
- All in Odin. One fast compiler, readable code, no header soup and no multi-hour engine rebuilds.
- Code reloads into the running editor. Change your game, build, and keep editing the same scene.
- One implementation of everything. No per-platform or per-API copies: one renderer for Vulkan and Metal, one Slang source for every shader.
- Ray-traced global illumination with hardware ray tracing on Vulkan and Metal and a software BVH fallback. Every bounce, in real time, with no baking.
- Traced reflections and glass, OpenPBR materials, physical light units, ACES 2.0 and HDR.
- Cluster LOD and GPU culling for dense scenes, streamed geometry and textures by distance.
- Physical atmosphere built in; volumetric fog, water, particles, decals and FSR frame generation as plugins.
First-party plugins that add nothing to your game until you use them: physics, destruction, ragdolls, motion-matching animation, AI minds with smart objects and navmesh, terrain, foliage, water, VFX, portals, cinematics, world streaming and more.
Anyone can write a plugin: it lives in its own repository and, listed in the plugin catalog, installs from the editor or from the command line. An agent can write one for you.
On Windows, Linux or macOS ARM64, from the engine root in bash (Git Bash on Windows):
./mirai edit demoThat builds and opens the editor with the included demo. To play it instead:
./mirai play demo. To make games without building the engine, grab the package for your
platform from the releases.
Building needs Odin dev-2026-11 and the platform's graphics driver; ./mirai doctor says what is
missing. ./mirai setup git, once per clone, makes git merge and diff scenes and other
documents. Platform setup, templates and commands are in
projects.
Mirai documents itself for humans and agents alike: each area has a skill in .agents/skills/
with a map from tasks to references.
| Area | Skill |
|---|---|
| Data core, generator, host | mirai-core |
| Editor | mirai-editor |
| Agent API (JSON-RPC, MCP) | mirai-agent-api |
| Rendering and RHI | mirai-rendering |
| Networking | mirai-networking |
| Physics and destruction | mirai-physics |
| Animation | mirai-animation |
| Abilities | mirai-abilities |
| Gameplay | mirai-gameplay |
| Plugins | mirai-plugins |
| World content (terrain, foliage, water, particles, navigation, AI) | mirai-world |
| UI | mirai-ui |
| Assets | mirai-assets |
| Importing | mirai-imports |
| Projects and build | mirai-projects |
| Standard library | mirai-std |
| Platform and audio | mirai-platform |
| Content-addressed store | mirai-store |
The layers and contracts are in ARCHITECTURE.md and the project rules in AGENTS.md.
Mirai is young and moves fast, so yes, there are bugs. If something breaks, looks wrong or is harder than it should be, open an issue with the steps to reproduce it — or send a pull request. Bug reports, fixes, plugins and demo scenes are all welcome, from humans and agents alike: CONTRIBUTING.md says how, and which models we do not accept code from.
Come say hi on Discord, follow @mirai3d on X for news, and if Mirai is useful to you, sponsor its development.
Dual-licensed under MIT or Apache-2.0, at your choice. Third-party material and its notices are in THIRD_PARTY_NOTICES.md.




