Err, that's what the codebase already does? Not sure what you guys are saying here... when you start a looped live code edit, it writes the mem block, and then for the rest of the frames, it just writes the input. That's exactly how it currently works.
I looked back at the video and it was just me misunderstanding what happened in the stream. When I saw that big file I thought it was because it was the entire state recorded every frame. I was unaware recording just the input was going to make a large file that quickly.