Makes sense, these would be great feature additions then!

• background livebook runner i.e. run a livebook like a script
• save all rendered output / code evaluation / error logs etc to a cloned livemd file called ‘{livebook name}-log-{timestamp}.livemd’
• the new livemd file can be loaded into livebook app at later time to view how that runtime went

Livebook to me feels like a higher functioning iex session; perfect blend of gui + code. Imo this would take it to next level!

Oh, I understand it better now.

The issue in implementing what you have in mind right now is that there is no official way for executing a notebook programatically. We want to add APIs for deployed notebooks though. Then you could pass a log file as parameter to the notebook itself

The Livebook application is separate from the runtime your notebook runs on. Therefore, if you want to log anywhere, you can configure the Logger in your notebook to log wherever you want.