Feature Idea: History Checkpoints

Describe your feature request

  • Within the history system, each file allows the user to save a checkpoint.

What problem(s) would this feature solve?

  • Would empower the user to quickly revert changes in a file without needing to paginate through every file save.
  • Would be a lightweight replacement for version control.

Explain what you were trying to do when you came across the problem leading to this feature request

  • As my app has gotten larger it has gotten more difficult to use the history feature since the file can have 100s of save points.
  • I would like the ability to quickly go back to my last known working file to feel more confident in being able to test out ideas within the file.
  • I don’t want to deal with setting up git or a version control right now

Honestly, it’s a pretty good idea to be able to favorite or save certain history checkpoints for easy restoration when needed, rather than searching through who knows how many just to find the correct one.


Make that 1000s, one file in one of my Repls has over 8k history points.


Do you mean to add the ability to set control points in the history of individual files, and not the whole project?

Could it look like this?


Exactly what I mean. Added some other thoughts in this X post also. Things like auto-checkpoints when you deploy and AI-generated change logs at each checkpoint.

1 Like

In that case, it’s really a good idea!

Twitter is banned in my country, so you could not write the contents of this post here :grin: