Thanks for your comment.
I'd like to add some reasoning behind this request:
That would be different from having some "usual" video capture of a coding session: that's a "fully locked" environment, too much detached from the actual experience. The video experience feels not "true", it doesn't create full involvement, and our brain understands and absorbs things with less simplicity when the experience is "detached". One has to be more involved, should be able to scroll up and down through the code in any moment during the "play" experience, should be able to create his own bookmarks and navigate through them, should be able to make little changes to the code and try them, just to figure out something unclear, and then continue, etc.
For example for teaching something, one could prepare a tutorial as a repository with a "recorded coding session" included, to teach how to use that library or that framework etc.
And for learning something new, one could download a recorded coding session and "play" it, with all the features that will be allowed in that kind of experience.
A feature that I would love to be included in such a tool would be the possibility for the recorder to record audio while recording the coding session, and that would be attached to the right points (e.g. a voice comment while writing some lines). And then the possibility to render it in subtitles to, so to enable subtitles in the "play" experience.
Another feature would be a live chat with the session creator, with the possibility to instantly live share the VS Code session with him/her. But that would probably be in the space of monetization possibilities (otherwise it'll be unlikely to find someone ready to reply on the other side), e.g. a learner could one-time pay for 30 minutes of a chat/call session, or make an annual subscription that allows several sessions, etc. And there could be a whole marketplace of free recorded coding sessions for any topic, where the authors could earn from these live on-demand chat/call sessions, and the author/maintainer of the service could keep a cut of that.
This is one of the uses, then there would be others in other fields.
For example, a tool to remind to oneself how something he has written works or should be used: a kind of narrated documentation of the code of projects, that is easier to produce while one is working on it, also with little storage requirements (because everything would be a small JSON) , except the audio files that can anyway be compressed a lot, especially because they're just voice and don't require it to be crystal-clear (I'd prefer small size for this use, something that would keep the whole thing in "some" megabytes).