Open Interpreter
A terminal coding agent for low-cost models, with switchable Rust harnesses plus ACP and Codex exec compatibility.
What does this agent do, and when should you use it?
Open Interpreter is a Rust-based terminal coding agent positioned to get stronger agent behavior from low-cost models. It is a fork of OpenAI Codex and lets users switch the active harness with /harness, including native, kimi-code, qwen-code, deepseek-tui, and claude-code. The agent runs commands in native sandboxing on macOS, Linux, and Windows, and supports exec, MCP, skills, hooks, permissions, and AGENTS.md. It can serve ACP-compatible editors and clients through interpreter acp, or replace the executable behind an existing Codex SDK integration through codexPathOverride. Product-specific configuration and runtime state live under ~/.openinterpreter, while repository instructions and skills can use AGENTS.md and .agents/skills.
After installation, i or interpreter starts a terminal session. In that session, /model changes the provider and model, while /harness selects a native or emulated harness; the listed harnesses include native, kimi-code, qwen-code, deepseek-tui, claude-code, and minimal. It executes commands in native sandboxing, reads repository AGENTS.md and shared .agents/skills directories, supports MCP, skills, hooks, and permissions, and stores product-only configuration and session state under ~/.openinterpreter. For ACP clients, it launches as interpreter acp. For an application already using the OpenAI Codex SDK, new Codex({ codexPathOverride: "interpreter" }) routes execution to Open Interpreter over the same Codex exec protocol. Its QA skill can test web applications with agent-browser or operate and test native applications with trycua.
- A developer using lower-cost hosted models for terminal coding can switch models and harnesses from one session.
- A team with an existing OpenAI Codex SDK integration can keep its SDK calls and set codexPathOverride to "interpreter".
- A developer using an ACP-compatible editor or client can configure it to launch interpreter acp.
- An engineering team testing a web or desktop application can use the included QA skill with agent-browser or trycua.
- A team standardizing repository instructions and reusable skills across compatible coding tools can retain AGENTS.md and .agents/skills.
What are this agent's strengths and limitations?
- Includes a Rust implementation of the provider-recommended Kimi Code harness behind a Codex-like interface.
- Lets one terminal agent switch among several named harness styles instead of fixing the workflow to one interface.
- Explicitly supports ACP and the Codex exec protocol; an existing Codex SDK integration has a documented one-line executable override.
- Runs commands in native sandboxing across macOS, Linux, and Windows, with documented web and native-app QA paths.
- Prefers shared conventions such as AGENTS.md, .agents/skills, and MCP instead of requiring new skills in a product-only directory.
- Live hosted-model sources require provider credentials, but the supplied material does not provide exact authentication configuration.
- The documented installation paths download and execute a remote shell or PowerShell script, which may conflict with restrictive installation policies.
- Web and native-app QA respectively use agent-browser and trycua, so those capabilities depend on the relevant tool path.
- This is a new Rust version distinct from the original Python project, which continues as the community-maintained endolith/open-interpreter fork; existing users need to assess that boundary.
How do you install or deploy this agent?
macOS or Linux: curl -fsSL https://www.openinterpreter.com/install | sh
Windows PowerShell: irm https://www.openinterpreter.com/install.ps1 | iex
Then run i or interpreter to start a session. The supplied material says live model sources for hosted providers require the credentials documented in the provider guides, but it does not specify the exact credential or configuration values.
How do you use this agent?
Run interpreter in a terminal, then use /model to choose a provider and model and /harness to inspect or switch harnesses. To use it as an ACP agent, launch interpreter acp and configure the ACP-compatible client to start that command. In a Codex SDK application, replace new Codex() with new Codex({ codexPathOverride: "interpreter" }). Run scripts/test-codex-sdk-compat.sh for a local compatibility check that does not require a provider.
How does this agent compare with similar options?
Compared with OpenAI Codex, this repository identifies itself as a Codex fork focused on emulating high-performing agent harnesses for low-cost models while retaining Codex exec protocol compatibility. The original Python Open Interpreter project continues as the community-maintained endolith/open-interpreter fork; this repository is the newer Rust version.