Wow, this is an old topic:)
It’s possible that this may be added at some time in the future. The downside is that projects may become extremely large (they already tend to be big).
That doesn’t have to be the case - only so if we save the full undo history.
We could just save a history list of all effects that were applied along with the parameter settings used. That shouldn’t take up too much extra space.
Such a list could even be exported and used as the starting basis for a Macro 
Or for QA testing purposes on new alpha test builds and RCs 
Peter.
Gosh this is an old topic! It’s 2023 and I’m still searching for this same functionality. How big would the text file be? Not very big, I reckon. If it just saved the last 1000 edits, with an average description length of ~1000 characters per logged project step, that would lead to a project log file of ~1MB.
I do love Audacity, and I have huge respect for those who made it. Also, I would also love to see this feature!
Once all effects are converted to real time, this will be moot.
As for saving “the last 1000 edits”, just saving a text file describing each edit is useless without a history of the audio that was modified.
The brute force approach would be a user option to save the undo history with the project, but then projects could quickly explode to 10s or 100s of gigabytes.
Oh, no, I’m not interested in being able to undo - just reproduce a sequence of effects using the exact same settings, so a later recording can be matched to a previous one
I was on the way to create this new thread: Could History of actions in Projects also be saved over multiple Exits? when this thread was suggested to me by the UI. So I desisted from posting my question.
I have perused the entire thread. What emerges is this:
And this:
There could surely be a trade-off between the one scenario in which the project file size resulting from recording all the steps and intermediate files is huge; and another in which all steps are so faithfully recorded that if the master file is stored and the history of steps are applied, as a batch of commands sequentially, then the final file that emerges is identical to the earlier finished product.
In that case, what needs to be stored is the original file and a list of steps executable within Audacity using some programming language used in Audacity. Like in Nyquist prompts may be. Lisp?
I am not sure. But seems doable. With some good developers here I am enthusiastic. I was warned by the UI while I was posting my thoughts on this old thread that my action would push an old thread at the top of the threads.
I carefully considered and concluded that it would be better to continue with the present thread in which discussion has already proceeded to a good extent, rather than beginning a new one.
I apologise, Mr. Daulton, if my conclusion is incorrect. I will be ready to have my thoughts and the present post removed.
Yes…I really should have labeled the effects applied though…