Add a config flag to keep native/* models out of the Claude Desktop model list #767

Area

Proxy and routing

What are you trying to accomplish?

I use OpenCodex to route Claude Desktop through the proxy, and I want Claude Desktop's model list to contain only the proxy-routed models. Today the Claude Desktop config keeps getting native/* entries added back, which I do not want there: they bypass the proxy, so they are absent from the request log, from usage accounting, and from the routing rules I configured. Having both sets present also makes the model picker ambiguous — two entries that look equivalent but behave differently.

What prevents this today?

There is no way to opt out. show, export and apply all reinsert native/* models into the Claude Desktop configuration, and the only way I have found to keep them out is to patch the code locally. That patch is the single change I would most like to stop maintaining, because it has to be re-applied on every release.

What should OpenCodex do?

Honour a boolean configuration flag that suppresses native/* entries when writing the Claude Desktop model list. Everything else stays as it is; when the flag is absent or true, behaviour is unchanged, so this is backwards compatible.

The flag needs to be respected by every path that writes that list, not just one command — in my local patch the enforcement points are the desktop profile export and the CLI's Claude Desktop command.

Example usage or interface

In ~/.opencodex/config.json:

{
  "claudeCode": {
    "enabled": true,
    "desktopNativeModels": false,
    "authMode": "proxy"
  }
}

With desktopNativeModels: false:

$ ocx claude-desktop show
models routed through the proxy:
  <provider>/<model>          (proxy)
  ...
  (no native/* entries)

A dashboard toggle alongside the existing Claude switch would be a natural home for it too, but the config key alone would be enough for me.

Alternatives or workarounds

• Patching the package locally. What I do now: a small change adding the config key plus the two enforcement points. It works, but it is lost on every npm install -g and has to be re-applied and re-verified after each release.
• Editing the Claude Desktop config by hand after each sync. Does not hold, because the next show / export / apply puts the entries straight back.
• Disabling the Claude integration entirely. Removes the feature I actually want.

Additional context

I am happy to open a PR for this if the config key name and placement are agreeable — say the word on whether you would prefer claudeCode.desktopNativeModels or something else, and whether you would want the dashboard toggle in the same change or separately.

Checks

• I searched existing issues and documentation.
• This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
• I removed secrets and personal data.