I have been polishing the Lopecode Tour for submission to Substrates 2026 workshop. Its a single-file self-serializing document/IDE environment. I presented this to FoC quite a while ago, but its been revised a lot. The major change is introduction of programmatic Agentic AI which critiques the notebook itself, lol. Its been quite helpful at finding grammar mistakes. There is a default demo endpoint for the AI which will allow gpt5-mini for free, subject to a rate limit, so you can try it. But also there have been zillions of glitch fixes and stabilizations, in particular the internal URL navigation works much better and the tour exploit this by popping open side panels to learn more about particular subjects. So the Tour is the initial map. Also I think I now have full coverage of Observable 1.0 syntax. I have support for import statements, including internal hyperlinking across them. Currently the tour sits at 2.9MB which I think is ok for a programming system. AI prompt tuning is ongoing, but it can now create new modules and write into them successfully. I use Lopecode's self serialization to open iframe clones of itself to do testing with AI in complex notebooks.

Nice! Getting better all the time! Minor bug report: it doesn't adapt to window resizing. I saved a local copy and opened it in a small browser window (Librewolf). Then I made the window full-screen, but the the rectangle used by Lopecode for rendering remained the same.

So gpt5-mini is good for checking grammar?

Have you got a link? Quite possibly by the "modern" keyword they might mean since native modules came about? The key tech is https://github.com/guybedford/es-module-shims which is transitively rewriting all the native statement "import" statements to the libraries internal "importShim" on the fly, with that in place you have total control over dependency resolution I fixed the resize thing. Thanks for testing it on Librewolf!

Thanks @Tom Larkworthy, resizing works fine now! All the TiddlyWiki discussions are in TiddlyWikis, so it's hard to give direct links. The issues are not about JavaScript (TW uses nothing else but JS scripts embedded in HTML), but with browser security features and restrictions on local file system access. Now that I think of it, what they want to do is save an edited file in-place, much like a document in a native app. What Lopecode offers is downloading a copy of the current state, so it's up to the user to manage different versions of the file. Maybe there is no more to it.

yeah filed https://github.com/tomlarkworthy/lopecode/issues/125. So that's a bug in the editor-5 component which has not been polished like the tour and is lagging the new navigation functionality, but yeah, its actually important to understand how things connect...