Having ChatGPT write code that you immediately turn around and execute is a very risky proposition for all kinds of reasons, the least of which are crashing at runtime or failing to compile. If you're having it produce code in a Turing-complete language, you've opened yourself up to the worst kind of prompt injection attacks.

A much safer approach would be to have it produce a JSON object that is interpreted by the wrapping code. This allows you to inspect the interpreting code and provide guarantees about what can and cannot be done by users.

But neither execution model solves my main point: someone still has to write the interpreter (or the library functions if you go the dangerous route). Someone has to think ahead and guess what the user is going to try to do and provide APIs that allow that. And that work is most of the work: our existing intent recognition models are actually not bad at all at their job, the failings these voice assistants have are almost all to do with predicting the ways in which users will try to interact with the system.