Google Flow Music’s Spaces feature already let you build a custom instrument or effect by describing it in natural language. As of 6 October 2026, you can export that Space as a VST3 or AU plugin and run it inside your DAW.
That is a short announcement with a long implication.
What changed
The capability itself is not new — Spaces has been the “describe an effect and get an effect” surface inside Flow Music for a while. What is new is the boundary it crosses. Previously, a custom Space lived inside Google’s environment, which means it was usable for sketching and unusable for finishing a record. Now the output is a VST3/AU file, which is the format every serious DAW on every platform loads.
Google’s published example is from producer Khris Riddick-Tynes, who built a plugin called “No Chaser” — described as helping ensure his instrumentals and vocals are sharp and studio-quality regardless of where they were recorded. A corrective processing chain, in other words, tuned to the specific failure modes of his own sessions.
Why the format matters more than the generation
There is a widely-held and largely correct scepticism about prompt-built audio processing: a plugin described in a sentence is unlikely to beat a plugin that a DSP engineer spent three years on. For a compressor, an EQ, a reverb — the well-understood problems with excellent existing solutions — that scepticism is right.
But that is not where this is useful, and the Riddick-Tynes example quietly demonstrates why. “No Chaser” is not competing with anything. It is a chain specific to one producer’s recurring problem, of the kind that normally lives as a saved channel strip, a macro, or a mental checklist applied by hand on every session. The existing way to make that into a real plugin is to learn JUCE and spend weeks. The existing way to not make it is to rebuild it manually forever.
The interesting category, then, is the personal utility — the thing you need constantly and nobody will ever sell you because the market for it is one person. Three decades of Max/MSP, Reaktor, SynthEdit, Pure Data and FlowStone patches exist because that category is real and large. Each of those tools demanded that you learn its own paradigm first. Natural language removes the paradigm, and VST3 export removes the walled garden.
The questions the announcement does not answer
Several, and they decide whether this is useful or a demo.
Latency and CPU. No figures are published for what exported plugins cost. A plugin that works and eats a core is not usable on thirty tracks.
What the export actually contains. Whether it is compiled DSP, a wrapper calling a local model, or a wrapper calling a remote service is not stated — and that distinction determines whether your session still opens in five years, or offline, or on a studio machine with no network.
Licensing and distribution. Whether you can give an exported plugin to a collaborator, sell it, or ship it with a project is not addressed in the announcement.
Platform coverage. VST3 and AU are named. AAX — Pro Tools — is not, which matters for anyone working in a commercial post or mix room.
Those are not nitpicks. The difference between “a plugin” and “a remote call shaped like a plugin” is the difference between a tool and a subscription dependency sitting in the middle of your mix bus. Until Google says which it is, treat an exported Space as something you prototype with rather than something you commit a project to.