One turn, one undo
However many things the co-producer changed, its turn is a single step in your history. Undo it, redo it, or fork the project at that point and keep both.
Undo is a feature of trust
The co-producer can rewrite your drums, add a layer and change the key in one turn. If you do not like it, one press puts the project back exactly as it was. Not step by step. The whole turn. That is what makes it safe to ask.
An AI you cannot undo is an AI you have to be careful with. An AI you can undo in one press is one you can play with, and playing is how people learn.
However many things the co-producer changed, its turn is a single step in your history. Undo it, redo it, or fork the project at that point and keep both.
The assistant edits through the same operations the buttons use, so every change is visible on the grid and in the blocks. There is no rendered file to wonder about.
A project is a history of changes, yours and the assistant's. Nothing is overwritten. You can go back to any point, and fork from there.
Make it darker. Double the tempo. Turn the bassline into a countermelody. The worst case is one press away from where you were.
Undo, listen, redo, listen. The difference is the lesson, and the co-producer will tell you in a sentence what it was.
Fork the project at the turn you liked. Now you have two songs, and each one keeps its whole history.
A generator gives you audio. There is no undo because there is nothing to undo; there is only another generation. An assistant that controls a DAW makes dozens of edits through the DAW's own commands, and the DAW's undo takes them back one at a time, if it can tell them apart from yours.
Here, a turn is recorded as one unit before it is applied, and the reducer that applies it is the same one that applies your clicks. That is a design decision, not a feature bolted on, and it is why the undo button always means what it says.
Undo takes back the whole turn. If you liked part of it, undo, then ask for just that part, or make the change yourself; the co-producer will have told you what it did, so you know what to ask for.
Yes. Every change you make is one step in the same history. Undo and redo work the same way for you and for the assistant.
A copy of the project from a chosen point in its history. Fork before a risky idea, or after a turn you loved, and both versions keep growing separately.
No. The project is its whole history. You can step back to the first loop if you like.
Free to start, and every turn the assistant takes is one press from undone.