openinterpreter /openinterpreter

A coding agent for open models like Kimi K3 and GLM 5.3

★ 68,889⑂ 5,947👁 452⑃ 783● 1,131▤ 78
RustApache-2.0Created 2023-07-14openinterpreter.com/
Download: Open Interpreter 0.0.61rust-v0.0.61 ↓0.0.612026-11-11
+3
Daily
+46
Weekly
68,889
stars
5,947
forks
452
watchers
783
prs
1,131
issues
78
releases

README

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:

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


Windows:

powershell
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:

text
 /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:

diff
-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.

Want a small browser UI over raw Open Interpreter? Start with the
local streaming web chat guide. For a complete
desktop, browser, or headless client, use
Interpreter Workstation.

 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 s

Top issues

Discussions

Latest release

Open Interpreter 0.0.61 rust-v0.0.61 2026-11-11
Open Interpreter 0.0.61

 Models

- No model-provider catalog or request-admission behavior changes are included
  in this release.

 Release

- Attest Linux Open Interpreter archives and their checksum manifest in the
  original tagged build.
- Verify that original build provenance before publishing existing artifacts.

Snapshot: 2026-11-16T09:23:14Z · Data license Apache-2.0 · JSON