openinterpreter/open-interpreter

Prefer upstream unless you specifically need this fork’s repository identity or pinned snapshot; there is no evidence here of added functionality, and it is slightly behind upstream.

Choose this fork only if the WebSocket service model is the point. If you want the current Open Interpreter feature set, fixes, and packaging, upstream is the better default; this fork is a narrow, stale deployment variant.

Choose the upstream project instead unless you explicitly need this older snapshot for reproducibility or historical comparison. This fork shows no added capabilities and is far behind upstream, so it is a poor default choice for new adoption.

Prefer upstream unless you need this exact old snapshot; this fork adds no visible capabilities and is materially behind, so it is a poor adoption target for most users.

Choose this fork if you want a more customized, experimental Open Interpreter variant with CLI/UI and docs changes. Choose upstream if you want the latest fixes, lower merge pain, or a more stable reference implementation.

Prefer this fork if you want a small, hands-on customization of Open Interpreter and are comfortable maintaining your own devcontainer and keeping up with upstream fixes. Prefer upstream if you want the most current, lowest-risk version with the full default developer experience.

Treat this as a stale mirror of Open Interpreter, not a feature-forward fork. Choose upstream unless you specifically need the older pinned state.

Choose this fork only if your goal is iOS-native experimentation. If you want the full, actively maintained Open Interpreter experience, upstream is the safer choice.