openinterpreter/openinterpreter

Open Interpreter

A coding agent optimized for low-cost models. Blog post ↗

English • Español • 简体中文 • 日本語

[!NOTE]

Today: Kimi K3 is here. We have reimplemented the provider-recommended

Kimi Code harness in Rust, giving you

maximum K3 performance with a Codex-like interface.

Kimi Docs →

Installation

macOS and Linux:

curl -fsSL https://www.openinterpreter.com/install | sh

Windows:

irm https://www.openinterpreter.com/install.ps1 | iex

Then type i or interpreter in your terminal to start a session.

Harness Emulation

Open Interpreter is a fork of OpenAI's Codex, with a focus on emulating the agent harness that gets the best performance out of low-cost models.

Use /harness to switch the active harness:

> /harness
native
claude-code
claude-code-bare
zcode
kimi-code
kimi-cli
qwen-code
deepseek-tui
swe-agent
minimal

Read more in the harness docs and provider setup guides.

ACP compatible, Codex compatible

Open Interpreter works in ACP-compatible editors and clients. Configure the client to launch interpreter acp; see the ACP guide for examples.

Already building with OpenAI's Codex SDK? Keep the SDK and make a one-line binary override:

-const codex = new Codex();
+const codex = new Codex({ codexPathOverride: "interpreter" });

Open Interpreter speaks the same Codex exec protocol. See the SDK guide and run scripts/test-codex-sdk-compat.sh for a local, provider-free compatibility check.

Portable by default

Open Interpreter should fit into your existing agent setup instead of trapping it in an Open Interpreter-only format. The product goal is to prefer shared, tool-neutral standards and directories, keep user-authored data in readable files, and make moving to or from another compatible agent straightforward.

Today that includes repository AGENTS.md, shared .agents/skills directories, MCP, ACP, and the Codex exec protocol. Product-specific storage under ~/.openinterpreter is reserved for configuration and runtime state that does not yet have a practical shared standard. Legacy product-specific skill directories remain readable for compatibility, but new skills belong in .agents/skills or ~/.agents/skills.

See the portability guide for the current boundary and the rules for evolving it.

Computer Use

Open Interpreter ships with a QA skill that lets any model operate and test interfaces. It can drive web apps in a real browser with agent-browser, or operate and test native apps with trycua.

Features

• Runs commands inside native sandboxing on macOS, Linux, and Windows.
• Switches providers and models from the TUI with /model.
• Runs any selected OpenAI-compatible provider through Chat Completions with

interpreter --chat-completions or interpreter exec --chat-completions.

• Inspects or switches Rust-native model harnesses with /harness.
• Tests web and native apps through the built-in QA skill.
• Runs as an Agent Client Protocol agent for editors with interpreter acp.
• Reuses shared AGENTS.md instructions and .agents/skills directories.
• Keeps product-only config and session state local under ~/.openinterpreter.
• Supports exec, MCP, skills, hooks, permissions, and AGENTS.md.

Documentation

• Terminal docs
• Quickstart
• Install guide
• Configuration
• CLI reference
• Harnesses
• Model provider guides
• Kimi K3
• DeepSeek
• Z.AI, GLM, and ZCode
• Agent Client Protocol
• Codex SDK
• Portability
• Sandbox & approvals
• Branding a distribution fork

Provider and model membership is generated, not maintained as Rust lists. From codex-rs, refresh all hosted providers with python3 scripts/write_provider_catalog.py, or repeat --provider to update only selected provider entries. Live model sources require the provider credentials documented in the provider docs.

[!NOTE]

This is the new Rust version of Open Interpreter, based on Codex. Looking for the original Python project? It lives on as a community-maintained fork at endolith/open-interpreter.

License

Apache-2.0