[FEATURE]: Add option to disable models.dev fetch for corporate proxy environments

Feature hasn't been suggested before.

I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem

Users behind corporate proxies experience issues with OpenCode 1.x.x versions due to a network call made on startup to https://models.dev/api.json. This call happens unconditionally and does not respect HTTP_PROXY/HTTPS_PROXY environment variables since Bun's native fetch() doesn't automatically handle proxy configuration.

Version 0.15.31 worked fine because this fetch behavior was either not present or handled differently.

Current Behavior

In packages/opencode/src/provider/models.ts, the get() function always calls refresh() which makes a network request:

export async function get() {
  refresh()  // Always calls fetch to models.dev
  const file = Bun.file(filepath)
  const result = await file.json().catch(() => {})
  if (result) return result as Record<string, Provider>
  const json = await data()
  return JSON.parse(json) as Record<string, Provider>
}

The code does have fallback mechanisms (local cache + bundled data), but the fetch is attempted regardless.

Proposed Solution

Add a configuration option to disable network calls, e.g.:

{
  "offline": true
}

Or more granularly:

{
  "experimental": {
    "disable_models_fetch": true
  }
}

When enabled, OpenCode would skip the models.dev fetch and rely on:

Cached data at ~/.cache/opencode/models.json
Bundled model data (compiled via macro)

Workaround

Currently, users can whitelist models.dev in their corporate proxy, but this isn't always possible in restricted environments.

Environment

OpenCode version: 1.x.x (works in 0.15.31)
Issue: Corporate proxy blocking/timing out on models.dev fetch

This issue might be a duplicate of existing issues. Please check:

Support HTTP_PROXY & HTTPS_PROXY for millions of users who are behind fire walls in some regions and some organizations. #531: Support HTTP_PROXY & HTTPS_PROXY for users behind firewalls and corporate proxies
acp-command unhandled rejection #3989: acp-command unhandled rejection when http_proxy is set (similar crash behavior in 1.x.x)
socket connection error with ProxyChains from v1.0.0 #4284: Socket connection error with ProxyChains from v1.0.0 (proxy-related networking issues)
Stuck After Compaction With long calls to models.dev #3053: Stuck After Compaction with long calls to models.dev (related to models.dev fetch blocking)
Suppport for airgapped installation #2224: Support for airgapped installation (offline environment support)

Feel free to ignore if none of these address your specific case.

yep this is a good idea i was toying around with it

I think experimental.skip_models_fetch would be a better name. After all, we're not trying to disable the ability to fetch updated model lists (opencode models --refresh should keep working), we're just trying to skip the automatic fetching of the updated list.

We might be able to achieve this simply by not enabling the 60 minute model refresh timer when experimental.skip_models_fetch == true? Need to look into how viable that is, but it sounds like it could work.

在有网的机器访问https://[models.dev/api.json](https://models.dev/api.json)网站下载json 存放到上述目录下文件中之后可以正常启动opencode了

I looked into this and found out why OPENCODE_DISABLE_MODELS_FETCH doesn't work - I think it's basically broken by design?

The problem

In models.ts, the get() function does this:

export async function get() {
  refresh()  // flag stops this from fetching
  const result = await file.json().catch(() => {})
  if (result) return result  // but it still reads the cache...
  if (typeof data === "function") {
    return JSON.parse(await data())  // ...or falls back to baked-in data
  }
  // last resort: fetch
}

So even if you:

Set the flag
Delete the cache file
...it still loads models from a Bun macro that embeds models.dev at build time. The data is literally compiled into the binary. There's no escaping it.

Proposed fixes

Option A: Make the env var actually work (easy fix)
Just return empty when the flag is set:

export async function get() {
  if (Flag.OPENCODE_DISABLE_MODELS_FETCH) return {}
  // ... rest unchanged
}

Should I submit a PR to fix this? or is this intentional and a different solution should be added?

@thdxr

@thdxr @rekram1-node

Could you help to check this issue?
shuv1337#307

You might consider trying the OpenCode Sentinel project—it cuts all network access except to your LLM, so it works flawlessly in network-restricted environments👍👍.

Repo: https://github.com/oneoflzx/opencode-sentinel

I stumbled upon this issue with my own use case: I'm trying to sandbox opencode restricting it to only localhost Ollama for projects with personal data, but it fails because of the mandatory models.dev download. It would be nice to make it optional, or to skip it if the user provides a specific model to use.

Checking for solution details

OPENCODE_DISABLE_MODELS_FETCH flag solves this issue

fish: disable models.dev fetch in opencode-ollama

Navigation Menu

Repository navigation

[FEATURE]: Add option to disable models.dev fetch for corporate proxy environments #4959

Feature hasn't been suggested before.

Describe the enhancement you want to request

Problem

Current Behavior

Proposed Solution

Workaround

Environment

The problem

Proposed fixes

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[FEATURE]: Add option to disable models.dev fetch for corporate proxy environments #4959

Description

Feature hasn't been suggested before.

Describe the enhancement you want to request

Problem

Current Behavior

Proposed Solution

Workaround

Environment

Activity

github-actions commented on Dec 1, 2025

thdxr commented on Dec 2, 2025

ariane-emory commented on Dec 2, 2025

ariane-emory commented on Dec 4, 2025

BAMSHK commented on Jan 16, 2026

b3nw commented on Jan 17, 2026

The problem

Proposed fixes

junmediatek commented on Jan 18, 2026

OneOfLzx commented on Jan 22, 2026

haplo commented on Feb 3, 2026

jaepang commented on Feb 24, 2026

emvnuel commented on Mar 25, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions