You may be out of luck, I'm afraid. Octo's local storage cache is a best-effort measure to rescue your programs from closed tabs. If you want your code to stick around for the long haul, your best bet is to save your code in a local text file or export a cartridge file.
Is there any more “developer like environment” hiding in the Octo repo somewhere? IE, I save my files on disk and the web browser auto-refreshes or at the very least I manually refresh it and my program is running the updated code from disk…
I could hack this together myself but wonder if anyone else has already done the work…
There are syntax definitions for a few text editors here https://github.com/JohnEarnest/Octo and you can use the command line mode if that suits you better.
Heh, possibly not for everyone, but behold (please don't judge my terrible Octo code, I'm trying, I'm trying):
Somebody has written an Emacs lisp CHIP-8 emulator so I can just work inside there where I'm most happy. Next steps would be to set up Flymake for on the fly compilation and error checking and then just hook it up to rebuild and rerun on every save, and seems like a nice productive environment. At the very least, I can't lose anything anymore.