-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Update README.md #1638
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
base: main
Are you sure you want to change the base?
Update README.md #1638
Conversation
Should we recommend usage of pipx/ uv tool install? |
I was thinking more of like "there are currently three versions of open Interpreter: main branch (status is...), Dev branch 1.0 (status is...) and oiv2 (status is...)" |
Doesn't matter to me. Whatever gives the smoothest experience. I used pipx before switching to pip install -e. Maybe describe both? |
@@ -13,15 +13,6 @@ | |||
<br><a href="https://0ggfznkwh4j.typeform.com/to/G21i9lJ2">Get early access to the desktop app</a> | <a href="https://docs.openinterpreter.com/">Documentation</a><br> | |||
</p> | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if this is 100% accurate, but this is what I was imagining:
> [!NOTE] | |
> There are currently three versions of Open Interpreter: | |
> - Open Interpreter 0.x Classic, in the `main` branch: Currently in maintenance mode. | |
> - Open Interpreter 1.0, in the `development` branch: An unfinished rewrite, currently abandoned. | |
> - Open Interpreter v2, at [Notnaton/oiv2](https://github.com/Notnaton/oiv2): Another rewrite, under development. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can remove oiv2 as it is just for experimentation.
Any good stuff from that will be merged into main branch.
I feel we should just continue the main branch, and close development branch as it has a lot of "beta" software from Anthropic.
The developer branch does have a lot of improvents also... We should consider moving some to main.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can remove oiv2 as it is just for experimentation.
Any good stuff from that will be merged into main branch.
OK
I feel we should just continue the main branch, and close development branch as it has a lot of "beta" software from Anthropic.
Yeah, probably not good to rely on one vendor's functionality. I remember you saying the development
codebase was overall better organized though? I've made changes to it, but using AI mostly, so I haven't taken the time to fully understood how the big picture works.
The developer branch does have a lot of improvents also... We should consider moving some to main.
Makes sense to me
Describe the changes you have made:
Reference any relevant issues (e.g. "Fixes #000"):
Pre-Submission Checklist (optional but appreciated):
docs/CONTRIBUTING.md
docs/ROADMAP.md
OS Tests (optional but appreciated):