Key Takeaways
- License changed from AGPL 3.0 to Apache 2.0 β confirmed via the GitHub API and the repository's LICENSE file
- Rewritten from scratch in Rust as a fork of OpenAI's open-source Codex project
- Current GitHub description: "A coding agent for open models like Kimi K3"
- Named model integration targets: Kimi K3, DeepSeek, Qwen, GLM/Z.AI
- 68,227 stars, 5,871 forks, only 10 open issues, last pushed 2026-08-20
- Became the #1 trending Rust repository on GitHub after shipping its Kimi K3 harness
- The original Python/AGPL "control your computer" tool lives on as a community fork at endolith/open-interpreter
π In One Sentence
Open Interpreter is now a Rust-based, Apache 2.0-licensed coding agent forked from OpenAI's open-source Codex and built to run open models like Kimi K3, replacing its original Python/AGPL "let a model run code on your machine" design.
π¬ In Plain Terms
The tool used to be a way to let ChatGPT-style code execution run locally instead of in OpenAI's cloud sandbox. It still does something similar in spirit, but the code, the license, and the target audience β people running open models, not one vendor's API β have all changed.
πNote: This review covers the current Rust/Codex-fork version of Open Interpreter. If you are looking for the original 2023-era Python tool that browses the web and edits files with natural-language commands, that lives on in the community fork, not the main repository.
What Is Open Interpreter in 2026?
Open Interpreter (github.com/openinterpreter/openinterpreter, commonly linked as github.com/OpenInterpreter/open-interpreter, which redirects to the canonical lowercase org) is a terminal-based coding agent. Its current GitHub description states it plainly: "A coding agent for open models like Kimi K3." That is a different project, in a different language, under a different license, than the tool that made the name known in 2023.
- Rust core, replacing the original Python codebase entirely
- Forked from OpenAI's open-source Codex project, and compatible with the Agent Client Protocol (ACP)
- Reimplements the provider-recommended "Kimi Code" harness in Rust, tuned for getting more out of open and low-cost models rather than one hosted API
- Repository topics on GitHub include acp, coding-agent, deepseek, kimi, qwen, and rust
- Homepage: openinterpreter.com
- Founded by Killian Lucas, who leads Open Interpreter Inc. as CEO and lead developer
From a 2023 AGPL Side Project to a 2026 Rust Rewrite
The Open Interpreter repository was created on 2023-07-14 and launched publicly in September 2023, at the height of interest in giving language models direct access to a terminal. Its founder, Killian Lucas β based in Bellingham, Washington β built it to give people the same "let the model just run the code" capability as OpenAI's hosted Code Interpreter, but running locally or against a remote model of the user's choice instead of inside a restricted cloud sandbox: no internet-access limits, no file-size caps, and full control over the execution environment. Lucas went on to found Open Interpreter Inc., where he is CEO and lead developer.
That original tool was released under the AGPL 3.0 license and described itself as a natural-language interface letting an LLM edit files, browse the web, and analyze datasets from a chat-style terminal session β closer to a general-purpose computer-control agent than a coding-specific tool.
By 2026, the project had shifted direction entirely. The team rewrote the codebase from scratch in Rust, forked it from OpenAI's own open-source Codex project, and repositioned it as a coding agent purpose-built for open and low-cost models rather than a general "control your computer" assistant. The license changed from AGPL 3.0 to Apache 2.0 in the same period.
How Open Interpreter Works Now
Open Interpreter's current architecture is a Rust reimplementation of the provider-recommended "Kimi Code" harness, wrapped in a Codex-compatible terminal interface. It speaks the Agent Client Protocol (ACP), which lets it plug into ACP-compatible editors and tools rather than only working as a standalone CLI.
- Rust core for the agent loop and terminal interface
- Forked from and structurally compatible with OpenAI's open-source Codex CLI
- ACP (Agent Client Protocol) compatible, so it can integrate with other ACP-aware tools, not just run standalone
- Named integration targets: Kimi K3, DeepSeek, Qwen, and GLM/Z.AI
- Still ships a Python SDK and runtime component alongside the Rust core (see the python-runtime-build.yml and python-sdk-release.yml workflows), so it is not a Rust-only project end to end
- 1macOS or Linux: run
curl -fsSL https://www.openinterpreter.com/install | shin a terminal. - 2Windows: run `irm www.openinterpreter.com/install.ps1 | iex` in PowerShell.
- 3Start the agent by running
iorinterpreterfrom a terminal. - 4Point it at an open model such as Kimi K3, DeepSeek, Qwen, or GLM/Z.AI per that provider's setup instructions β the project does not document a single required backend.
- 5Use it from the terminal directly, or connect it through an ACP-compatible editor if you prefer working inside an IDE rather than a standalone CLI.
The License Change: AGPL 3.0 to Apache 2.0
Open Interpreter's original Python-era codebase was released under AGPL 3.0, a copyleft license that requires anyone who modifies the code and runs it as a network service to release their modified source. The current Rust codebase is released under Apache 2.0, confirmed via both the GitHub API's license field and the raw LICENSE file at the repository root.
Is Open Interpreter Still Maintained?
Every signal available on the repository points to active, current maintenance rather than a project coasting on past popularity. It was last pushed to on 2026-08-20 β within roughly two weeks of this review β and carries only 10 open issues against 68,227 stars and 5,871 forks, a low ratio for a repository this size.
The project also runs a substantial automated CI setup, evidenced by the workflow files in its .github/workflows/ directory: rust-ci.yml, rust-ci-full.yml, and rust-ci-full-nextest-platform.yml run the Rust test suite via cargo nextest across multiple OS platforms; cargo-ci.yml and cargo-deny.yml cover dependency and security auditing; blocking-ci.yml is a required check that gates merges; postmerge-ci.yml and public-ci.yml run further validation; python-runtime-build.yml and python-sdk-release.yml build and release the Python SDK component; and repo-checks.yml plus codespell.yml handle repository hygiene.
Repository activity
- What it shows:
- Last pushed 2026-08-20, not archived
Star-to-issue ratio
- What it shows:
- 68,227 stars vs. 10 open issues β a small backlog
Fork count
- What it shows:
- 5,871 forks
CI coverage
- What it shows:
- 9+ workflow files covering Rust tests, dependency audits, and required merge gates
Trending status
- What it shows:
- #1 trending Rust repository on GitHub after the Kimi K3 harness shipped
πNote: We did not run our own test suite against Open Interpreter for this review. The maintenance signals above are drawn from the repository's public commit history, issue count, and its own published CI workflow files, not from benchmarks PromptQuorum generated. Verify current status directly on the repository before committing significant time to it.
Who Should Use Open Interpreter?
The right fit depends on whether you specifically want a coding agent tuned for open models, or the original general-purpose "control your computer" tool.
Open Interpreter vs. Alternatives
Open Interpreter's current positioning β a Codex-compatible terminal coding agent for open models β puts it alongside several categories of tool: other terminal coding agents, IDE-native agents, proprietary vendor agents, and its own historical peers from the 2023 "give an LLM agency over your machine" wave.
| Tool | Link | Interface | License | Best For |
|---|---|---|---|---|
| Open Interpreter | github.com/OpenInterpreter/open-interpreter | Terminal, ACP-compatible | Apache 2.0 | Coding agent for open models |
| Aider | aider.chat | Terminal | Apache 2.0 | Git-native diff-based pair programming |
| Cline | cline.bot | VS Code extension | Apache 2.0 | Autonomous IDE agent |
| OpenHands | github.com/All-Hands-AI/OpenHands | Sandboxed agent runtime | MIT | Autonomous SWE agent tasks |
| Continue.dev | continue.dev | IDE extension | Apache 2.0 | Autocomplete + chat, IDE-scoped |
| OpenAI Codex CLI | github.com/openai/codex | Terminal | Proprietary | Vendor-hosted terminal coding agent |
| Claude Code | claude.com/product/claude-code | Terminal | Proprietary | Vendor-hosted terminal coding agent |
| AutoGPT (classic) | github.com/Significant-Gravitas/AutoGPT | CLI, autonomous loop | MIT | Unscoped autonomous-agent experiments |
| BabyAGI | github.com/yoheinakajima/babyagi | CLI, autonomous loop | MIT | Minimal autonomous task-loop experiments |
Common Mistakes When Evaluating Open Interpreter
Most confusion about Open Interpreter in 2026 comes from expecting the 2023-era tool rather than the current Rust rewrite.
Frequently Asked Questions
What license is Open Interpreter under?
Apache 2.0, confirmed via the GitHub API's license field and the repository's LICENSE file. This is a change from the original AGPL 3.0 license used by the earlier Python-era codebase.
Is Open Interpreter still maintained?
Yes. The repository was last pushed to on 2026-08-20, carries only 10 open issues against 68,227 stars, and runs a multi-workflow CI setup covering Rust tests, dependency audits, and required merge checks.
What happened to the original Open Interpreter?
The original Python tool β which let a local or remote model edit files, browse the web, and run code from a natural-language terminal session β was rewritten from scratch in Rust in 2026 and forked from OpenAI's open-source Codex project. The original Python/AGPL version lives on as a community fork at github.com/endolith/open-interpreter.
What models does Open Interpreter support?
The project names Kimi K3, DeepSeek, Qwen, and GLM/Z.AI as integration targets in its repository topics and description, and reimplements the "Kimi Code" harness in Rust. It does not document a single required model backend.
How do I install Open Interpreter?
On macOS or Linux, run curl -fsSL https://www.openinterpreter.com/install | sh. On Windows, run irm https://www.openinterpreter.com/install.ps1 | iex in PowerShell. Then start the agent with i or interpreter.
Is Open Interpreter free to use?
Yes. It is released under the Apache 2.0 license, which permits free use, modification, and redistribution, including inside a commercial product, without an obligation to release your own source code.
Is Open Interpreter compatible with Codex or Claude Code?
Open Interpreter is a fork of OpenAI's open-source Codex project and is built to be Codex-compatible, and it supports the Agent Client Protocol (ACP) for integrating with other ACP-aware tools. It is a separate, independently maintained project from OpenAI's Codex CLI and Anthropic's Claude Code, not an official extension of either.
Does Open Interpreter still let a model control my whole computer?
The current Rust project is scoped as a coding agent, not a general "control your computer" tool. The original broader-scope Python tool β file editing, web browsing, dataset analysis β lives on separately in the community fork at endolith/open-interpreter.
How does Open Interpreter compare to Aider or Cline?
All three are terminal- or IDE-based coding agents. Aider is git-native and structures its output as reviewable diffs; Cline runs as a VS Code extension; Open Interpreter is a standalone, Codex-compatible terminal agent tuned specifically for open models. Which one fits depends on whether you want git-diff review, IDE integration, or open-model-first tuning.
Why did Open Interpreter switch from AGPL 3.0 to Apache 2.0?
The project does not publish a stated reason in its README for the specific license change alongside the 2026 rewrite. Apache 2.0 is a more permissive license than AGPL 3.0: it removes the copyleft "network use" source-disclosure obligation and adds an explicit patent grant, which makes the code easier to build commercial products on top of. Read the LICENSE file directly to confirm current terms before relying on this distinction.