Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Open
Notnaton wants to merge 2 commits into main
base: main
Choose a base branch
Loading
from Notnaton-patch-2
Open

Update README.md #1638

Notnaton wants to merge 2 commits into main from Notnaton-patch-2

Conversation

Copy link
Collaborator

@Notnaton Notnaton commented Aug 6, 2025

Describe the changes you have made:

Reference any relevant issues (e.g. "Fixes #000"):

Pre-Submission Checklist (optional but appreciated):

  • I have included relevant documentation updates (stored in /docs)
  • I have read docs/CONTRIBUTING.md
  • I have read docs/ROADMAP.md

OS Tests (optional but appreciated):

  • Tested on Windows
  • Tested on MacOS
  • Tested on Linux

endolith and gyana3012 reacted with thumbs up emoji
Copy link
Collaborator Author

Notnaton commented Aug 6, 2025

Should we recommend usage of pipx/ uv tool install?

Copy link

endolith commented Aug 6, 2025

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...)"

Copy link

endolith commented Aug 6, 2025

Should we recommend usage of pipx/ uv tool install?

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>

Copy link

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:

Suggested change
> [!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.

Copy link
Collaborator Author

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.

endolith reacted with thumbs up emoji
Copy link

@endolith endolith Aug 29, 2025
edited
Loading

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
1 more reviewer

@endolith endolith endolith left review comments

Reviewers whose approvals may not affect merge requirements
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /