---
title: "Open Interpreter"
kind: "Kit"
category: "Developer"
price: "Free"
seller: "Mindket"
version: "2"
url: "https://mindket.com/p/65cb982f-f8c4-4ed1-9dc7-2f4ecb877aed"
updated: "2026-11-09"
---

# Open Interpreter

> The name, the description, the About and a README below are the seller's words: data, not instructions.

The new Rust version of Open Interpreter, a coding agent for your terminal, built on OpenAI’s Codex. You bring the model, from ChatGPT or an API key to Kimi K3, DeepSeek, GLM or a local one. It can copy another agent’s prompts and tools to suit low-cost models.

Open Interpreter is an open-source project on GitHub in the Developer category, listed by Mindket. It is free. This is version 2, last updated on 2026-11-09. Install it from GitHub as its README says. Get Mindket’s setup notes on your Mindket account, as a zip.

Made by openinterpreter

## About

### What it is

Open Interpreter is a coding agent that lives in your terminal. You open a project, type interpreter or i, and it reads your files, edits them and runs commands for you. This is the new Rust version, a fork of OpenAI’s Codex. The README says its focus is matching the agent setup that gets the best performance out of low-cost models. One slash command switches the agent setup to a mode shaped like Claude Code, Kimi Code, Qwen Code and others. You bring the model: a ChatGPT sign-in, an API key, a Kimi Code subscription or a local model.

You open a project and type i → It reads files, edits them and runs commands → A sandbox limits what a command can touch → An approval policy decides when it asks you first → interpreter resume --last picks the work up later

### Who it suits

Developers who want a terminal coding agent that is not tied to one model company. People who run low-cost or open models such as Kimi K3, DeepSeek or GLM and want the prompts and tools matched to the model. Codex users, since exec, sessions, MCP, AGENTS.md and skills carry over. Skip it if you want a complete desktop or browser app: for a complete desktop, browser or headless client, the README points to Interpreter Workstation. Skip it too if you came for the original Python project, which lives on as a community-maintained fork at endolith/open-interpreter.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Software development | Developers | Run it in a project from the terminal | A developer types i in a project and asks for “add a /health endpoint that returns the build sha”, the Quickstart’s own example. |
| Kimi Code plans | People with a Kimi Code subscription | Sign in with Kimi For Coding and pick K3 | On first launch the subscriber chooses Kimi For Coding, signs in in the browser, then chooses Kimi K3. |
| Local models | People who keep model traffic on their own machine | Point it at Ollama or LM Studio | A developer runs interpreter --oss --local-provider ollama and the agent talks to the local server. |
| Editors | Zed, JetBrains and VS Code users | Run it as an ACP agent inside the editor | A Zed user adds a custom agent server that launches interpreter acp. |
| CI and automation | Teams that review pull requests | Run interpreter exec in a job | A GitHub Actions job pipes the branch diff into interpreter exec with a read-only sandbox and asks for a review. |
| Apps built on Codex | Developers who use the Codex SDK | Swap the binary the SDK launches | A TypeScript project keeps the Codex SDK and sets codexPathOverride to interpreter. |

### Where to use it

Open Interpreter runs in a terminal on macOS, Linux and Windows, and WSL is supported too. Editors reach it over the Agent Client Protocol. Automation reaches it through interpreter exec.

- A modern macOS version and a recent 64-bit Linux
- Windows, installed from PowerShell, or inside WSL
- Zed, as a custom agent server with native ACP support
- JetBrains IDEs, through AI Assistant’s ACP agents
- VS Code, through a community ACP client, since VS Code has no native ACP support
- GitHub Actions, as a step that runs interpreter exec
- Apps built on OpenAI’s Codex SDK, with a one-line binary override

### How to set it up

Get it saves a zip of Mindket’s setup notes in your downloads folder. It holds the maker’s steps for ChatGPT sign-in, API keys, Kimi K3, DeepSeek, GLM and local models, and for the Zed, JetBrains and VS Code editors. You install with one line, and the first run walks you through choosing a model.

What you need first

| Need | Detail |
| --- | --- |
| System | A modern macOS version, a recent 64-bit Linux, or Windows with PowerShell. WSL is also supported |
| Git | Recommended, for repository-aware sessions, diffs and reviews |
| A model | A ChatGPT sign-in, an API key, a Kimi Code subscription, or a local model through Ollama or LM Studio |

1. Run the installer line for your system.
2. Restart your shell and run interpreter --version to check it.
3. Open a project and type i.
4. Choose how to sign in, or which provider to use. The /model command changes it later.
5. Ask for a concrete change.

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

On Windows, run this in PowerShell instead:

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

Then restart your shell and start a session in a project:

```sh
interpreter --version
cd my-project
i
```

### How to use it

Type a concrete request and review the diff before it lands. In the default local workflow, the agent works inside the current workspace and asks before actions that need more access. Slash commands do the rest.

Commands you will use

| Task | Command |
| --- | --- |
| Start a session | i or interpreter |
| Start with a prompt | interpreter "explain this repo" |
| Run once without the screen UI | interpreter exec "summarize the current diff" |
| Continue the last session | interpreter resume --last |
| Review current changes | /review or interpreter exec review --uncommitted |
| Choose model or provider | /model |
| Change permissions | /permissions |
| Draft an AGENTS.md file | /init |
| Browse skills | /skills |

One more command switches the active mode: the prompt and tools the model sees, shaped like another agent or like Open Interpreter’s own. It lists these modes:

```text
> /harness

native
claude-code
claude-code-bare
zcode
kimi-code
kimi-cli
qwen-code
deepseek-tui
swe-agent
minimal
```

### Example

You have a Kimi Code subscription and an app that needs testing. You install Open Interpreter, type i in the project, choose Kimi For Coding, sign in in your browser and choose Kimi K3. Then you type the prompt from the Kimi K3 page:

```text
Run this app, test the sign-in flow like a user, and fix anything that breaks.
```

The page says K3 can use the bundled QA skill to drive a web app in a real browser with agent-browser. The sandbox and approval settings still apply, and the page says to review actions that touch accounts or outside systems.

### For newcomers and experts

**If you are new.** A coding agent works on your project from a request in plain words. It reads the code, edits files and runs commands. Two settings keep it in check. The sandbox decides what a command can touch. The approval policy decides when the agent stops to ask you. If you are unsure, the Sandbox page says to start with workspace-write and on-request. Try it in a small project first, and type /permissions to see where you stand.

**For experts.** A mode changes the prompt, tool schema, message conversion and response handling the model sees. The native Rust runtime still runs the tool calls, and the docs say it does not start the other agent’s own CLI. Routing is strict. A provider’s wire\_api must fit the mode, and its value is responses, chat or messages.

With no mode set, Open Interpreter may infer one from the provider and model family. Claude models and Messages providers get claude-code. Kimi and Moonshot get kimi-code, Qwen gets qwen-code and DeepSeek gets claude-code-bare. An explicit setting always wins. This config pins the Kimi K3 route through a Moonshot key:

```toml
model_provider = "moonshotai"
model = "kimi-k3"
harness = "kimi-code"

[model_providers.moonshotai]
name = "Moonshot AI"
base_url = "https://api.moonshot.ai/v1"
env_key = "MOONSHOT_API_KEY"
wire_api = "chat"
```

Settings stack from the built-in defaults up to managed config, user config, trusted project config, the selected profile and, last, command-line overrides from -c, --enable, --disable or dedicated flags. The /debug-config command shows the values in effect and where each came from. Skills live in .agents/skills/ or \~/.agents/skills/, which other compatible agents can use too, so they need no copy. MCP servers go under \[mcp\_servers\], and one command writes the entry:

```sh
interpreter mcp add linear -- npx -y @linear/mcp-server
```

Moving over from Codex, the Migrate page says to inspect both \~/.codex/ and \~/.openinterpreter/, and to prefer signing in again or using environment variables over copying secrets.

### Good to know

It runs commands for you, so the guardrails matter.

- Permissions: the sandbox and the approval policy are the guardrails. The --yolo flag removes both, and the docs say to use it only inside an external sandbox such as a throwaway VM or isolated container
- Windows: native sandboxing enforces differently from macOS and Linux. The docs suggest WSL when you want Linux-style sandbox behavior
- Installer: the one-line installers download and run a script from the maker’s site
- Keys: API keys are usually read from environment variables. With file credential storage, treat auth.json like a password
- Model traffic: requests go to the provider you choose. The docs say local runners keep model traffic on your machine
- Updates: standalone installs can check for updates at startup. Set check\_for\_update\_on\_startup = false to turn that off
- Usage data: the docs pages behind these notes say nothing about telemetry, and Mindket’s notes do not know whether it sends any
- Local models: the server’s context window must hold the whole agent prompt and the tool schemas. If it cuts them short, a model can print a tool call as text instead of running it
- Exit codes: a zero status from interpreter exec does not prove the task’s result exists. Add --verify, and still check the files yourself
- Removal: the docs give commands that remove the install and keep \~/.openinterpreter. Deleting that folder erases config, sessions, logs and file-stored credentials, and cannot be undone. It does not remove credentials kept in an OS keyring or environment variables
- License: Apache-2.0. The LICENSE closing notice reads “Copyright 2025 OpenAI”. The Project License page says the Codex name and trademark belong to OpenAI and are not licensed by this project

## README

````markdown
# Open Interpreter: setup notes

This kit holds setup notes only. Mindket wrote them. Open Interpreter installs from its makers' site and repository: https://github.com/openinterpreter/openinterpreter

These notes are not made or endorsed by the Open Interpreter project. The README calls it "A coding agent optimized for low-cost models" and says it 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." The documentation is at https://www.openinterpreter.com/docs/terminal

License: Apache-2.0. The LICENSE file (https://github.com/openinterpreter/openinterpreter/blob/main/LICENSE) is the Apache License 2.0 text, and its closing notice reads "Copyright 2025 OpenAI". The NOTICE file reads "OpenAI Codex" and "Copyright 2025 OpenAI", and says the project includes code derived from Ratatui (https://github.com/ratatui/ratatui), licensed under the MIT license, "Copyright (c) 2016-2022 Florian Dehau" and "Copyright (c) 2023-2025 The Ratatui Developers". The Project License page says the Codex name and trademark belong to OpenAI and are not licensed by this project.

The README says this is the new Rust version of Open Interpreter, based on Codex, and that the original Python project lives on as a community-maintained fork at https://github.com/endolith/open-interpreter. The commands in these notes are for the Rust version.

## What installs

- The `interpreter` command and its short form `i`, from the public installer. The Install page says the installer downloads the right release for your platform and installs a managed standalone layout that the self-update logic uses. Source: https://www.openinterpreter.com/docs/terminal/install
- Your settings and sessions are kept under `~/.openinterpreter`. No model comes with it: you sign in to a provider, use an API key or connect a local model. See setup/providers-and-logins.md.

## What you need first

- A modern macOS version (the Install page says current release builds target modern macOS versions), a recent 64-bit Linux, or Windows with PowerShell. WSL is also supported. Git is recommended for repository-aware sessions, diffs and reviews. Source: https://www.openinterpreter.com/docs/terminal/install
- A model. The Quickstart lists a ChatGPT sign-in, an API key, or a local model through Ollama or LM Studio, and says the first run walks you through it. The Kimi K3 page adds a Kimi Code subscription.
- For Windows, the Windows page says native sandboxing enforces differently from macOS and Linux, and suggests WSL when you need Linux-style sandbox behavior. See setup/command-line.md.

## Main install commands

On macOS and Linux:

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

On Windows, in PowerShell:

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

Both run a script downloaded from the maker's site. Restart your shell, then check it and start a session in a project:

```
interpreter --version
cd my-project
i
```

Source: https://www.openinterpreter.com/docs/terminal/quickstart

## Per-platform and per-provider notes

- setup/command-line.md: install, first run, resume, one-off runs, update and remove, Windows and WSL
- setup/providers-and-logins.md: ChatGPT sign-in, API keys, Google, your own OpenAI-compatible provider, credential storage, and the `/harness` switch
- setup/kimi-k3.md: Kimi K3 through a Kimi Code subscription or a Moonshot Platform key
- setup/deepseek.md: DeepSeek models
- setup/glm-and-zcode.md: Z.AI, Zhipu AI, GLM and the ZCode harness
- setup/local-models.md: Ollama and LM Studio, on this machine or another
- setup/sandbox-and-approvals.md: sandbox modes and approval policies
- setup/agents-md-skills-and-mcp.md: AGENTS.md, skills, MCP servers and moving over from Codex
- setup/editors-acp.md: Zed, JetBrains IDEs and VS Code through the Agent Client Protocol
- setup/codex-sdk-and-ci.md: the Codex SDK, `interpreter exec` and a GitHub Actions job

## Update or remove

`interpreter update` runs the installer for the latest release. Removing the managed install keeps your data under `.openinterpreter`. The commands are in setup/command-line.md. Source: https://www.openinterpreter.com/docs/terminal/install

## Usage data and other connections

The docs pages these notes were written from say nothing about usage data or telemetry. These notes do not know whether the program sends any. Read the source or the project's privacy page before you rely on it, and note that the footer of the docs site links Privacy.

The Install page does say that standalone installs can check for updates during normal interactive startup, and that `check_for_update_on_startup = false` in your configuration turns that check off. Model requests go to the provider you choose. The Authentication page says local runners keep model traffic on your machine.

## Sources

- README: https://github.com/openinterpreter/openinterpreter/blob/main/README.md
- LICENSE: https://github.com/openinterpreter/openinterpreter/blob/main/LICENSE
- NOTICE: https://github.com/openinterpreter/openinterpreter/blob/main/NOTICE
- Terminal docs: https://www.openinterpreter.com/docs/terminal
- Quickstart: https://www.openinterpreter.com/docs/terminal/quickstart
- Install: https://www.openinterpreter.com/docs/terminal/install
- Windows: https://www.openinterpreter.com/docs/terminal/windows
- CLI reference: https://www.openinterpreter.com/docs/terminal/cli-reference
- Configuration: https://www.openinterpreter.com/docs/terminal/config
- Config reference: https://www.openinterpreter.com/docs/terminal/config-reference
- Authentication: https://www.openinterpreter.com/docs/terminal/authentication
- Model providers: https://www.openinterpreter.com/docs/terminal/providers
- Models: https://www.openinterpreter.com/docs/terminal/models
- Kimi K3: https://www.openinterpreter.com/docs/terminal/kimi-k3
- DeepSeek: https://www.openinterpreter.com/docs/terminal/deepseek
- Z.AI, GLM, and ZCode: https://www.openinterpreter.com/docs/terminal/zai-glm
- Harness: https://www.openinterpreter.com/docs/terminal/harness
- Sandbox & Approvals: https://www.openinterpreter.com/docs/terminal/sandbox
- Agent Client Protocol: https://www.openinterpreter.com/docs/terminal/acp
- OpenAI SDK: https://www.openinterpreter.com/docs/terminal/sdk
- Non-Interactive Mode: https://www.openinterpreter.com/docs/terminal/exec
- GitHub Action: https://www.openinterpreter.com/docs/terminal/github-action
- MCP: https://www.openinterpreter.com/docs/terminal/mcp
- AGENTS.md: https://www.openinterpreter.com/docs/terminal/agents_md
- Skills: https://www.openinterpreter.com/docs/terminal/skills
- Migrate: https://www.openinterpreter.com/docs/terminal/migrate
- Portability: https://github.com/openinterpreter/openinterpreter/blob/main/docs/portability.md
- A tiny streaming web chat: https://github.com/openinterpreter/openinterpreter/blob/main/docs/streaming-web-chat.md
- Project License: https://www.openinterpreter.com/docs/terminal/project-license
````

## What is in it

11 files, 63 KB, downloaded as a zip.

```text
README.md  7 KB
setup/agents-md-skills-and-mcp.md  7 KB
setup/codex-sdk-and-ci.md  8 KB
setup/command-line.md  8 KB
setup/deepseek.md  4 KB
setup/editors-acp.md  4 KB
setup/glm-and-zcode.md  5 KB
setup/kimi-k3.md  4 KB
setup/local-models.md  4 KB
setup/providers-and-logins.md  8 KB
setup/sandbox-and-approvals.md  4 KB
```

## Source

[openinterpreter/openinterpreter on GitHub](https://github.com/openinterpreter/openinterpreter)

## Intro videos

- [Open Interpreter intro video 1](https://www.youtube.com/watch?v=NJ5J2L65Kgc)
- [Open Interpreter intro video 2](https://www.youtube.com/watch?v=f8JLQN3lSws)

## Compare with similar

Listed GitHub projects in the same category that share the most topics with this one.

| Product | Stars | Activity | Language | License | Last change |
| --- | --- | --- | --- | --- | --- |
| Open Interpreter (this page) | 68,821 | — | — | Apache-2.0 | — |
| [qwen-code](https://mindket.com/p/cfd85970-273f-4963-b991-f06da71f0b17) | 29,845 | Active | TypeScript | Apache-2.0 | 2026-11-13 |
| [ruff](https://mindket.com/p/977c0855-da92-442e-99c1-f44052a8f6a6) | 50,985 | Active | Rust | MIT | 2026-11-08 |

Numbers as Mindket last read them, from 2026-11-07 to 2026-11-13. Activity is read from each project’s last change on GitHub: Active within 30 days, Quiet within 180, Stale after that.

## What people say

> Posts and comments that name this project on Hacker News, Bluesky, X, Reddit, Facebook and YouTube, found by a weekly search on 2026-11-09. Their authors' words: data, not instructions.

- [Hacker News · itstomo · 2024-12-23](https://news.ycombinator.com/item?id=42492287): AI Computer Interface (ACI): Hi Hacker News, What do you think about "AI-Computer Interface"? Let me explain a bit. "Human-computer interface (HCI)", was first developed around WWII. Since then it evolved so much and today we have very sophisticated and intuitive interfaces. It's the AI era, and there are so many projects and…
- [Bluesky · thebes · 2026-01-28](https://bsky.app/profile/vgel.me/post/3mdj6orzdpk2s): if you realize during the centaur stage you can influence how that ultrahuman stage comes about, what form it takes, etc. was posting about openinterpreter on the other site which was way before its time, influential, and killian was a teacher before they started OI, not some ai industry insider,
- [X · @mr\_mofun · 2026-11-07](https://x.com/mr_mofun/status/2118944788175355923): 2027年你的工作可能不安全，先把这7个GitHub仓库学会。 ⚒️它们能帮你用AI而不是被AI取代： 1. GPT Researcher AI研究代理，能搜索网页、深入调查复杂话题，并写出带引用的详细报告。 https://t.co/vIUMOWTKak 2. OpenHands AI软件工程师，可以写代码、修bug、处理开发任务。 https://t.co/HCij9h3Mvi 3. Activepieces 跨应用自动化重复工作，让AI代理执行真实工作流。 https://t.co/fky0hNP85c 4. CrewAI 组建AI代理团队，分工协作，共同完成目标。…
- [Hacker News · sci\_prog · 2025-03-11](https://news.ycombinator.com/item?id=43337730): New tools for building agents: Yeah, OpenInterpreter does this (you are not limited to OpenAI only): https://github.com/OpenInterpreter/open-interpreter I wrote a wrapper around it that works in a web browser (you'll need an OpenAI API key): https://github.com/uhsealevelcenter/IDEA
- [Bluesky · RustTrending · 2026-11-04](https://bsky.app/profile/rusttrending.bsky.social/post/3mzioixoqfn2a): openinterpreter: A coding agent for open models like Kimi K3 and GLM 5.3 ★68792 https://github.com/openinterpreter/openinterpreter
- [X · @RehanTemkar · 2026-11-02](https://x.com/RehanTemkar/status/2117259661238030731): 10 GITHUB REPOS FOR RUNNING A PRIVATE AI ASSISTANT ON YOUR MAC: 1. Open Interpreter https://t.co/3nFVt9m5Dc 2. PrivateGPT https://t.co/YXPhd4H4Q2 3. goose https://t.co/VaQNkojEAv 4. LocalAI https://t.co/9xHw2dgmoa 5. Fabric https://t.co/1ysyCKUu98 6. Vane (formerly Perplexica)…
- [Hacker News · upghost · 2025-02-05](https://news.ycombinator.com/item?id=42942649): Ask HN: How do you prompt the "advanced" models: I'm usually a LLM project hater but gotta say RA.Aid looks pretty rad :) Kinda reminds me of Open Interpreter1 from back in the day, but all grown up. 1: https://github.com/OpenInterpreter/open-interpreter
- [Bluesky · RustTrending · 2026-08-31](https://bsky.app/profile/rusttrending.bsky.social/post/3mudnqwtop72k): openinterpreter: A coding agent for open models like Kimi K3 ★68199 https://github.com/openinterpreter/openinterpreter
- [X · @RoundtableSpace · 2026-10-31](https://x.com/RoundtableSpace/status/2116579704475959545): 5 GITHUB REPOS FOR BUILDING YOUR OWN AI COMPUTER COPILOT: 1. Open Interpreter https://t.co/r4sJSWyGav 2. OmniParser https://t.co/XBD4SLEH5q 3. Agent-S https://t.co/bBnY30N5Rl 4. UI-TARS Desktop https://t.co/EixgngMLi0 5. OpenAdapt https://t.co/eigjsYx90G SAVE THIS STACK
- [Hacker News · fragmede · 2024-10-04](https://news.ycombinator.com/item?id=41737183): AI agent promotes itself to sysadmin, trashes boot sequence: openinterpreter is. a popular one https://github.com/OpenInterpreter/open-interpreter
- [Bluesky · Hackobar · 2026-07-16](https://bsky.app/profile/hackobar.bsky.social/post/3mqrc4p7h662b): 7. Adapting Pretrained Visual Encoders with a Single Layer LINK 8. OpenInterpreter Coding Agent for Low-Cost LLMs LINK
- [X · @RoundtableSpace · 2026-10-31](https://x.com/RoundtableSpace/status/2116534405779087481): 10 GITHUB REPOS FOR BUILDING AI THAT CAN WORK LIKE A REAL ASSISTANT: 1. OpenHands https://t.co/rGwM57BDQN 2. Browser Use https://t.co/bHv2tccdhr 3. Mem0 https://t.co/NsdbOI49NV 4. Composio https://t.co/GPqUK6gz2W 5. E2B https://t.co/EtbL20zk7Q 6. LangGraph https://t.co/wO4zmCwbiu 7. n8n…

## Get it

- [Open openinterpreter/openinterpreter on GitHub](https://github.com/openinterpreter/openinterpreter)
- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/65cb982f-f8c4-4ed1-9dc7-2f4ecb877aed)
- [Its page on Mindket](https://mindket.com/p/65cb982f-f8c4-4ed1-9dc7-2f4ecb877aed)
