To be legally binding and enforceable, they must be explicitly and individually approved by the user. Even when signing in as a guest/without an account, using the app creates a license agreement, so the clickwrap flow must legally capture this specific assent to protect the underlying engine's IP.

Regarding the needs a text-based interface, I totally agree with you! Most of the time you can create models directly within the terminal or with a simple script. That's why we actually provide a CLI that allows you to build and run models. You can initialize models, add blocks with parameters, connect ports, validate the graph, and trigger code generation all from the terminal. Nevertheless, we think the GUI is useful to review the model and inspect it graphically