4 ms·
Yes, I’m curious how they’re handling sandboxing for this effectively untrusted code.
by bodhi_mind 4y ago
Yes, I’m curious how they’re handling sandboxing for this effectively untrusted code.
- nmachado 4y agoYep - we do not expose any sort of prompting. We use the LLM only at specific parts of the process, and the user has no access to it.
- tough 4y agoDoesn't the user provide the input that's feed to that function calling the LLM tho? Prompt hacking is a bit like sql injection in my mind but we don't have ORM's yet
- nmachado 4y agoThis would be a concern if we are feeding the raw user input and feed it directly into an LLM. In our case, we are not simply a wrapper over an LLM. There are multiple parsing and rule-based steps done to the input schemas - we extract specific pieces from the schemas and convert them to our internal format before feeding it our models. Thus, it mitigates such malicious behavior.
- tough 4y agoThanks for the answer, I just found out about kor on twitter and made me think back of this thread, sharing in case it's of your interest https://eyurtsev.github.io/kor/ https://eyurtsev.github.io/kor/
- Nebyou 4y agoOur transformations are executed in a staging database/schema before deployment. We also have versioning and backtesting capabilities. In addition, you will have complete visibility of the code we produce before and after deployment.