NeutrinoParticles Editor 2.0.16: AI Agents Can Now Drive the Editor

NeutrinoParticles Editor 2.0.16 is out, for Windows, Linux and macOS.

AI agents can now drive the editor

The editor ships with an embedded MCP server, so AI agents — Claude Code, Claude Desktop and other MCP clients — can work in it alongside you. An agent sees the interface as a tree of named elements and drives it the way a person would: clicks buttons, switches modes, picks from menus, sets values in any panel or dialog. It can open projects, create and edit effects, undo and redo, configure exporters and export effects. Every action it takes is a single undoable step, so anything you disagree with is one Ctrl+Z away.

Nothing happens behind your back. Signing in stays a human action. If an agent closes the editor with unsaved work, the usual prompt appears and the agent has to show it to you rather than answer it for you.

Agents also hit walls that we never see — something unreachable, confusing, or simply broken. When that happens, an agent can send a feedback report with screenshots straight to us. Only with your explicit consent, from a signed-in account, and carrying nothing beyond the editor version, your OS and the active renderer.

It is off by default. Turn it on in Editor Settings, or start the editor with --mcpServer. The server listens on 127.0.0.1 only — it is not reachable from outside your machine.

Colour codes for emitters

Once an effect has a lot of emitters, telling which timeline flag or which window belongs to which one gets hard. Right-click an emitter in the Emitters panel and pick Color Code: Auto Color picks a bright colour for you, keeping it as far as it can from the ones already in use, Custom Color opens a full colour picker. The colour then shows as a small flag next to the emitter's name and on its generator flags in the Timeline, so everything belonging to that emitter reads as one at a glance. Colours are saved with the effect.

A new value type: Particle Speed

Any 1D value can now read how fast a particle is moving, straight from the value type menu — no need to build it out of Particle Velocity and a "length" expression. It works on its own and as the X axis of a graph. Effects already using the "Over particle speed" graph keep working exactly as before, while getting simpler inside: every value reading the speed now shares one calculation instead of each carrying its own.

Fewer random crashes

The preview runs your effects on V8, the JavaScript engine behind Chrome, and it has been upgraded from a two-year-old version to the current one. That closes a rare crash that could take the editor down while you edited a value or an expression, and previews now behave even closer to what your effect will do in a real browser or game runtime. On Windows, international text APIs in preview scripts work as they do in a browser instead of closing the editor.

Beyond the engine, this release fixes crashes when adding a graph key by clicking on a curve, when pasting certain emitters, when several projects are open at once, and when files change on disk while a dialog or menu is open. The editor is also far less likely to shut itself down when a screen-capture tool or shell extension briefly holds its window busy — that pause is no longer mistaken for a freeze.

Crash reports from macOS and Linux now say what actually went wrong. They used to arrive missing the one log line that names the problem, which made them hard to act on. Nothing changes in how the editor behaves — it just means crashes get fixed faster.

Getting it

2.0.16 is on the downloads page, and the editor will offer it to you automatically. The full release notes list everything.

If something looks wrong, tell us — crash reports include the effect you were working on, which makes them far more useful.