Models

Use /model to choose provider, model, harness, and model-specific controls. The footer shows the active selection.

Shell Overrides

interpreter -m gpt-5.1-codex "review this module"
interpreter --oss "use my local open source provider"

Config Defaults

model_provider = "openai"
model = "gpt-5.1-codex"
model_reasoning_effort = "medium"
model_reasoning_summary = "auto"
model_verbosity = "medium"

Where Model Metadata Comes From

Open Interpreter does not keep one hand-written Rust list of every model. Metadata is layered:

The model manager asks the active provider for models, then uses bundled data when it can identify the provider by Anthropic identity, base URL, provider name, or auth env var. This lets proxy configurations still inherit useful metadata when they clearly point at a known provider.

Capability Metadata

Model metadata can control:

• picker visibility;
• display name and description;
• context window;
• input modalities such as text and image;
• whether the model is supported by the API;
• supported request parameters;
• reasoning control shape;
• web/search support;
• parallel tool-call support.

Reasoning is not a single boolean in the UI. The protocol has these control shapes:

Reasoning Effort

When a model exposes effort controls, Open Interpreter uses these values:

Harnesses may map these values to provider-specific fields. For example, kimi-cli maps minimal and low to low reasoning, medium to medium, and high or xhigh to high.

Unsupported models hide, ignore, or reject reasoning controls depending on provider behavior.

Input Modalities

The canonical input modality tags are:

Attach images:

interpreter -i screenshot.png "what is wrong here?"

Legacy payloads that omit modality metadata default conservatively to text and image support for compatibility, but generated provider entries should specify the real modalities when known.

Local Models

Open Interpreter has two built-in local OSS providers:

Start the local service before Open Interpreter, then launch the provider directly:

interpreter --oss --local-provider ollama
interpreter --oss --local-provider lmstudio

--oss without --local-provider uses your saved oss_provider or opens a picker that shows whether each default local endpoint is responding.

For a server on another host or port, set its full OpenAI-compatible /v1 base URL before launching Open Interpreter:

CODEX_OSS_BASE_URL=http://192.168.1.20:1234/v1 \
  interpreter --oss --local-provider lmstudio -m qwen/qwen3-coder-next

Use --local-provider ollama for a remote Ollama server. Do not create a separate model_providers entry just to change the address of either built-in local provider; CODEX_OSS_BASE_URL is the supported override.

Model metadata warnings

Model metadata for ... not found means the local server returned a model ID that is not in Open Interpreter's compatibility catalog. It does not by itself mean the server connection failed. Confirm the exact ID exposed by the server, pass that same value with -m, and update Open Interpreter so you have the latest catalog. Open Interpreter can continue with fallback metadata, but some model-specific controls or behavior may be unavailable.

Provider Families And Harness Defaults

Some model families get a default harness when no explicit harness is set:

See Harness for the wire-api compatibility matrix and Model providers for provider-specific setup guides.