[levpopov]

This is fantastic, thank you for your work! I'm excited to see this project combine a clean API in a popular language, with a fast online playground that requires no installation. Having played with OpenSCAD and CadQuery in the past, this feels like a big step forward.

Some suggestions (I'm sure you've already thought of most of these):

- It would be great to have notebook-like UI to isolate steps and allow faster partial rebuilds.

- live editing is great, but it'd be nice to automatically stop in-progress rebuild if another edit is made while it's computing. Right now it seems to always let a rebuild complete even if it's already out-of-date.

- Search on API/docs page would be really handy

- Face/vertex filtering API looks cleaner than CadQuery's, and I'm excited to try it out. In a lot of cases I would still really like to just be able to click on the model and get a reference in code. Even if it's just an index that would break if topology has changed. Auto-generating stable references/filters would be even better, when possible.

[sgenoud]

> - It would be great to have notebook-like UI to isolate steps and allow faster partial rebuilds.

Great idea, I have done something in that spirit integrating with natto.dev, but something more like a repl might be nice as well (https://natto.dev/@sgenoud/e2ade00d1fb4406abe78061e7f9a959b)

> - Search on API/docs page would be really handy

Good point, I use docusaurus, there is an algolia integration, I will look into it!

> Even if it's just an index that would break if topology has changed. Auto-generating stable references/filters would be even better, when possible.

Definitely the reference should be easy to implement, the stable one... less so.

I have tried to implement a filtering method inspired by cad query but which did not invent its own DSL. Always interested in feedback!