Add file upload/extension support in .yaml

[george-lhj]

Currently in the UI, I need to pass in files into the agents (.pkl and .txt) into the query in order to have the necessary context; so something like this.

We need to add functionality to be able to do this through the .yaml file so that we can directly go through the terminal and call all the agents sequentially without the need for the UI.

Not sure if this should be in POC0/1.

[psschwei]

For now, to handle passing files between agents we should create a working directory for each run (say, /tmp/weather-job/run_234r2342) and assume all agents can read/write in that directory.

[maximilien]

OK, taking this to complement issue #27. The proposal as we left it in December is to provide a working directly for agents. By convention and default, I propose the directory to be:

/<TMP>/bee-hive/<workflow_name>__ # the __ is there to prevent collision

We can also include a way to override this in the workflow.

LMK if you agree @psschwei and @developer-gliu and will close this and add that to the issue #27

[george-lhj]

the naming convention is fine w/me. But the overall issue for this still isn't solved for now I think.

Even when we create a tmp file holder location, we need to be able to actually upload these files and let it read as context for the agent. I've been looking for examples but there doesn't seem to have a single one (although Paul did find one that can successfully output a file for the answer through api that I got working). As a workaround for the demo, I have just been reading this files into the agent and using threading, but this isn't scalable

[george-lhj]

the naming convention is fine w/me. But the overall issue for this still isn't solved for now I think.

Even when we create a tmp file holder location, we need to be able to actually upload these files and let it read as context for the agent. I've been looking for examples but there doesn't seem to have a single one (although Paul did find one that can successfully output a file for the answer through api that I got working). As a workaround for the demo, I have just been reading this files into the agent and using threading, but this isn't scalable

saw on stack overflow that if you want to upload a file to OpenAI, you need to pass it in as a prompt and as text(as of March last year ). I'm not sure if that's still true. Since Bee is built on top and has mostly the same functionality, that means we would have to read these files in as text to the prompt, and use threading to keep track of all the context/prompts throughout the session.

[psschwei]

provide a working directly for agents [...] /<TMP>/bee-hive/<workflow_name>__ [...] LMK if you agree

that location is fine with me

we need to be able to actually upload these files and let it read as context for the agent. I've been looking for examples but there doesn't seem to have a single one

I believe this can be done via the UI, so it in theory should be possible... we may need to ask the framework team for guidance.

if you want to upload a file to OpenAI, you need to pass it in as a prompt and as text [...] Since Bee is built on top and has mostly the same functionality

@developer-gliu good to know and something we should keep in mind for the python version of the framework (cc @vabarbosa)

[planetf1]

The framework currently seems to use the /api/v1/files endpoint

I've not tried this myself

[maximilien]

OK. Let me see what I can do to add this to #27

[maximilien]

@george-lhj , can we close this?