Sebastián Estévez

In the short term, adding OPENAI_API_KEY as an env variable (either in your terminal before starting langflow or using the dotenv component) should function as a workaround: 

By the way I was able to reproduce this same scenario with langflow v1.0.18 and the sequential crew component with memory enabled. The error message is the same except it...

Yeah more specifically crewai's memory feature tries to use embeddings from openai and expects the api key to be set via env var.

Thanks for the reply @cjnolet Yes, it's the python API using float32 (I checked and looks like double isn't supported). I'll take a stab at a minimum reproducible example. Is...

Hi @hemantvsn, welcome and thanks for filing this issue! Are you referring to parallel tool calls like here? https://platform.openai.com/docs/guides/function-calling/configuring-parallel-function-calling

Interesting, I'm having trouble finding information about multiple sequential tool calls in the same run in the official assistants API documentation so we may have to try things empirically. Do...

I'm a big fan of OI, we didn't start with it because it doesn't provide any sort of sandbox. That said if you're okay with the security implications / risks...

I like this idea, would you be interested in submitting a patch?