[zachdive]

That's more of an example to address the point. We've find our users often use this feature in our onshape/fusion extensions in complex assemblies. Being able to select faces and edges as context in addition to prompts can be quite a powerful interface in more complex projects where users need to adjust tolerances or edit multiple objects to prevent interference

[tapia]

I understand the goal, but describing complex geometries with specific tolerances with natural language is much more complex than creating the geometry programmatically. There are geometries that I could not clearly describe with words, but it's clear the operations I need to do to create them. But who knows, maybe I'll be proven wrong.

[zachdive]

I largely agree with you. It's case by case and the ideal ux imho is to have both.