How to build electron app for OS-Copilot

[powerstar0926]

Thanks for this wonderful repository.

I want to make electron app with all functionalities of OS-Copilot.
Now I made some changes in Friday-front and integrated it with OS-Copilot. It works well.
Users can login only when they input valid OpenAI API Key, then this key is set on .env file in OS-Copilot.
The point is this.
I want to build and publish this with downloadable electron app for mac.
Now friday-front runs quick-start.py file in OS-Copilot as if we run this with terminal, right?
So my electron app should involve all OS-Copilot files? And if someone download this app, all python environment should be configured automatically? I have no idea for this.
How to solve this problem.
Please help me.

Best Regards.

[Zichen Ding]

If your app is essentially a frontend interface for OS-Copilot, with the underlying implementation still being the OS-Copilot system, then theoretically, your environment should include all the necessary code and corresponding Python packages.

Additionally, I would like to know if the issue you previously had with the API has been resolved? If it has, I will go ahead and close that issue.

[powerstar0926]

Thanks for your response.

I am going to add new tool for the next time. Please close the previous issue.
Now I want to develop electron app for macOS with all functionalities of OS-Copilot.
All prompts should be entered on every user's app.
For example, If someone input this prompt : "Open new tab in firefox and go to github.com", new tab in firefox should be opened on their PC and go to github.com.
If we use OS-Copilot as backend, all commands will execute on server PC, right?

Now I made something and works well, but the point is we should use absolute path to quick_start.py of OS-Copilot.
So every users should change this path for their PC. Can we use relative path? For example, REACT_APP_PATH="../../OS-Copilot".
Or Can we use OS-Copilot as backend server? If someone input the prompt above, new tab in firefox on their PC should be opened.
Please help me how to solve this problem.

[Sakai]

Thanks for your kind attention :)

The primary goal of FRIDAY-front is to open up a possibility of convenient usage for OS-Copilot, so it would be just a wrapper for its inner application and will not be provided with abilities to execute system-level commands. Therefore, it might not be a good idea to put back end application on server side because OS-Copilot is doing more than just executing commands issued from remote LLM, such as storing tool data in local DB.

As for the second problem, since these two repositories are separated and their relative position cannot be supposed, we recommended using absolute path of OS-Copilot in document. However, if you are developing on application aiming at higher availability for general user, it would be OK to use relative path as it would finally be resolved to absolute one at runtime.

[powerstar0926]

Thanks for your response.

I have another plan for OS-Copilot.
I want to make a downloadable OS-Copilot app for mac so that users can simply download it and use it without installing modules and without python environment on their PC.
Is this possible?
If possible, please tell me how to implement this plan.

Thanks again.

[zywu]

Hi @powerstar0926 , we are not familiar with Mac app implementation, but I think it is doable, I have seen many startups building such an app for their agents.

You are more than welcome to make a PR after you finish it. You can join the discord server for instant communication, we are happy to see what we can help with your building! Maybe @ShiinaHiiragi can take a look at this one?