Every release,written down.
What changed in Mirven, and why, newest first.
-
0.18
Mirven Engine, and Godot projects
- New project type: Godot. Mirven plans, builds and checks Godot 4 games the same way it does Unity games.
- Mirven Engine: agents build, run, test and capture frames from the command line. Nobody opens the editor.
- Engine work runs on a separate, invisible desktop. In a 2 h 28 min test run it took focus from the user zero times.
- GPU work pauses while you play, and starts again when the PC is idle.
- Up to eight agents work in parallel, each in its own worktree. A shared import cache cuts import time by 67%.
- Choose how hard each model thinks, from Low to the highest level, per chat and per team role.
- One interface: the workspace was simplified into a single layout, with grouped menus and a layout made for 1920-wide screens.
-
0.17
Board: a visual workspace for every project
- Every project gets a Board that collects its screenshots and videos from playtests, jobs and uploads on one canvas.
- Frames, notes, arrows, search and filters by tag, date and decision. Compare two to four shots side by side.
- Decisions keep their reason and date, so you can see why a look was chosen weeks later.
- Large boards stay smooth to pan and zoom, even with thousands of cards.
-
0.16
Memory that shows its work
- Agent runs get memory chosen for the job, ranked by what the job is about, instead of the whole project history.
- A context receipt shows exactly which notes went to which run.
- Pin a note so it goes first, or exclude one so it never goes.
- Memory is never cut off mid-sentence: a note goes in whole or not at all.
- Tidy-up suggestions for duplicate and outdated notes, with undo. Nothing is deleted automatically.
-
0.15 updates
A calmer workspace, and your plan limits in view
- A second, denser workspace layout designed for large screens.
- Your Claude and Codex plan usage (five-hour and weekly) shown next to the queue.
- "Stop everything" now pauses the whole queue, and moving a job to the front no longer starts the queue by itself.
- A dropped provider session stops the queue instead of retrying the same job again and again.
-
0.15
Verifiable game production on your machine
- Studio readiness separates ready, missing and unknown: folder, Unity, providers and build.
- When the code under a merge candidate has changed, the merge queue runs its checks again. A cancelled or incomplete build never counts as a pass.
- Code review, build proof and your own play-test are kept as separate decisions.
- Each run gets its own permission for talking to Mirven, and it can be revoked.
- A usage ledger keeps retry history; unknown cost is never shown as zero.
-
0.14
The name Mirven
- The studio, its command line and its integrations all carry one name.
- Older installs keep working through thin compatibility shims.
-
0.13
The product pass
- A map of every job and how it relates to the others.
- Quick ask: a question about your project without opening a full session.
- A calendar of what ran, what shipped and what is planned.
-
0.12
Many agents, one plan
- Plans split into jobs that name their files; a job that names a running job's folder waits.
- A merge queue that replays each job on the latest version and runs its checks again when needed. The model review is not repeated.
- A resource guard that scales how many agents run with free memory, CPU and disk.
-
0.11
Contracts and proof
- Build jobs outside the quick lane state their acceptance criteria before work begins.
- Evidence is collected automatically, and a model that did not do the work can review it.
- An agent's claim and Mirven's own evidence are kept apart.