4 ms·
I don't see any reason for them to lock this down. The code runs in a Kubernetes sandboxed container which can't make network calls and has an execution time l
by simonw 3y ago
I don't see any reason for them to lock this down.
The code runs in a Kubernetes sandboxed container which can't make network calls and has an execution time limit, why should they care what kind of things I'm running on that CPU (that I'm already paying for with my subscription)?
The Code Interpreter sandbox runs entirely independently of the RAG mechanism, so sadly you can't use Interpreter to figure out how their RAG system works (I wish you could, it would make up for the lack of documentation.)