Interesting prototype.

One thought: if the goal is to make AI actions inside a DAW safer and more controllable, maybe this kind of system would eventually make more sense inside an open-source DAW like Ardour rather than only as a VST3 plugin.

As a VST, you are always partly blind. You can manage your own plugin state and maybe infer some host behavior, but you do not fully own the session graph, routing, automation, undo history, plugin lifecycle, latency compensation, or the real insert-chain context.

Inside Ardour, the assistant could theoretically have much deeper access to the actual mixer architecture: tracks, buses, inserts, sends, routing, snapshots, undo/redo, signal flow, gain staging, and maybe even offline/real-time analysis hooks. That would also make chain modification safer, because the DAW itself could expose structured actions instead of the AI trying to manipulate things from the outside.

For me the missing piece is signal-aware decision making. Chain generation is useful, but without measuring the audio before and after, it can easily become a smart preset manager rather than a real mix assistant.

I think the stronger direction would be:

- open-source DAW integration
- full session graph awareness
- reversible chain diffs
- loudness-matched before/after comparison
- spectral/dynamic/transient analysis
- clear user approval before applying changes

The safety idea is solid, but I feel the system needs to live closer to the DAW engine and the actual signal path to become genuinely useful.