-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First thoughts on OpenDevinPowerShell #1
Comments
Thank you for the feedback. Will dig into some of the points as I review the errors. One thing with the workspace issue is I kept it blank for it to default to what is set in the OpenDevin/config.py as was running into Path issues using the Linux based default "./workspace". Will put a default to use windows paths. More thoughts to come as I get started today. Thank you and appreciate your work on this. |
@risingsunomi also how is this gonna work with the new version of OpenDevin as "CodeAct"? |
I will need to update this repo, if needed. Haven't touched it in a bit but will try to look this/next week. |
I have added updates to the install script but there is a major blocking issue with backend starting. This has to do with the OpenDevin backend. |
I'm really impressed by the changes made thus far!
I think that the terminal in OpenDevin should be set as PowerShell permanently for windows users.
Here are my first thoughts and impressions:
1- Needed to change my PowerShell execution policy to "Bypass"
2-
3- LLM_BASE_URL is missing from config.toml
4- Terminal is not in the Workspace area (which might be a good thing, I don't know if they changed it recently)
5- WORKSPACE_DIR was empty after installation even if I supplied the right directory
6- WORKSPACE_DIR needs to be written with forward slashes instead of the Windows default back slashes, like so "C:/Dev/OpenDevinPowerShell/opendevin_env/OpenDevin/workspace"
7- My working config.toml for LM Studio:
TEST 1
8- Project:
a simple webpage that says "hello world"
Creates:
hello_world.html
Terminal:
PowerShell:
The first time it wrote the HTML file was better, but it's a good example.
TEST 2
9- Tougher project to test terminal:
create a Python script that displays the math and the result for "2 + 2 =" and name the file "calcul.py"
Creates: calcul.py
Terminal:
Worked well execept for the coding error.
Corrected it as:
Terminal:
We are back to Bash.
So it called the file correctly at first but defaulted to "/usr/bin/python" afterwards.
A big thank you for helping the Windows community!
The text was updated successfully, but these errors were encountered: