Companion to https://github.com/KittyCAD/text-to-cad/issues/4210. Export and other commands are available to ZDS right away, but if a user asks Zookeeper "export this model as a STEP" it will:
- Receive and process all the current project contents
- Connect to its own engine via websocket
- Execute that model, then export it to STEP and save it as a conversation attachment
- Return the STEP file as a part of its JSON-encoded reasoning messages
I'm prototyping if ZDS and other clients could be able to publish capabilities to Zookeeper using a update_client_command_schema with its command schema, then react to client_command_request messages from it by executing the command and replying with a client_command_response.
Export should be the first example, hidden behind a feature flag, to be published by ZDS, unless it turns out to be easier to just have all the commands get published 🙃.
Companion to https://github.com/KittyCAD/text-to-cad/issues/4210. Export and other commands are available to ZDS right away, but if a user asks Zookeeper "export this model as a STEP" it will:
I'm prototyping if ZDS and other clients could be able to publish capabilities to Zookeeper using a
update_client_command_schemawith its command schema, then react toclient_command_requestmessages from it by executing the command and replying with aclient_command_response.Export should be the first example, hidden behind a feature flag, to be published by ZDS, unless it turns out to be easier to just have all the commands get published 🙃.