Runchat will automatically save a local copy of your work whenever you run a node. To work on multiple runchats, you will need to sign in and save to the cloud.
There are several ways to create a new runchat.
Note that creating a new runchat will overwrite any unsaved local changes you have made - so if you want to keep what you were working on remember to save it to the cloud.
Runchat will save your local changes whenever you make changes to a node. After you have saved the Runchat to the cloud, Runchat will also track version history by saving a new copy whenever you run a node.
If you click on the bookmark / save icon on the right, Runchat will expand the save menu. From here you can enter a name for your runchat to make it easier to find in your dashboard later. Click the tick icon to save your runchat to the cloud, or click the duplicate item to save a copy. Click the download icon to download a JSON file for working offline. If you have a Pro subscription you can toggle the privacy of the saved runchat using the Eye icon (see below) The Clock icon toggles the Save History sidebar for this runchat.
Once you have named and saved your runchat, a copy of your runchat will be saved to the cloud every time you run it. You can view all timestamped versions of your runchat by clicking the Clock icon in the save menu. Clicking on a time stamp will replace nodes in the editor with the state of the runchat at that time. You can add a custom label to each saved version to make it easier to return to particular states, and delete versions if you wish.
All saved runchats are public by default, meaning that if someone visits the url link to your runchat they will be able to see exactly how it was made. This is to encourage learning and sharing. You can make a runchat private and only visible to you by toggling the privacy setting (the eye icon) in the save menu. Private runchats can still be shared in libraries and used as nodes in other runchat.