[Feature]: Support uploading/downloading file through front-end

[xingyaoww]

What problem or use case are you trying to solve?

Support uploading and downloading files through the front end. This will allow the agent to perform data analytics tasks by looking at user-uploaded content (e.g., CSV, excel, or even a zip file, etc.).

Describe the UX of the solution you'd like

• Support uploading the files to workspace by simply dragging files to the workspace in UI or adding a button for uploading.
• Support downloading file (not sure what's the best way to do it).
• Maybe support the ability to move file (but it may confuses the agent)

Do you have thoughts on the technical implementation?

Describe alternatives you've considered

Having user directly modify the mounted workspace folder on their disk - this is probably not a good user experience as the user need to switch back-and-forth.

Additional context

[amanape]

For the technical implementation, it may be worth exploring the Clipboard API, FileReader, and drag event listeners as a starting point. It may be as straightforward as extending the backend endpoints to accept filename and content to update workspace.

It is also worth noting that the implementation may also slightly depend on the target platform, which is currently self-hosted. It will require additional considerations if OpenDevin were, for example, accessible online via URL.

[xingyaoww]

Currently, our Sandbox abstraction has a copy_to method (https://github.com/OpenDevin/OpenDevin/blob/main/opendevin/sandbox/sandbox.py#L33), which we could leverage to implement this uploading feature.

We may need to support copying from [inside the container] to the [host] to be able to download from workspace.

If OpenDevin were hosted via URL, as long as the sandbox supports this copy_to method, the whole upload/downloading thing should work out-of-box?

[amanape]

We may need to support copying from [inside the container] to the [host] to be able to download from workspace.

I was actually referring to extending files.py based on a quick trace from how the current frontend file explorer. But I'm not all too familiar with the backend implementation to know how the agent will be aware of this change, so I may be lacking.

If OpenDevin were hosted via URL, as long as the sandbox supports this copy_to method, the whole upload/downloading thing should work out-of-box?

I meant the actual APIs that would be utilized on the frontend. If I remember correctly, it requires less permissions/effort to copy/paste/drag to an Electron application compared to a Safari browser. But that was a while back.