plugin: ctx.model.transform editor.remove() is a silent no-op for the model catalog and model resolution (2.2.5) #63100

Description

A plugin using ctx.model.transform + editor.remove() to restrict a provider's models has no effect in 2.2.5: removed models still appear in GET /api/model and can still be selected and called via --model. There are no errors — the transform fires and the editor reflects the removals, but nothing propagates to the catalog or to model resolution.

This is the exact pattern recommended as the interim workaround for #49986 (comment) and mentioned again in #61601, so anyone following it gets silently non-functional filtering.

Expected: removing a model via the transform hides it from the catalog and makes explicit selection fail with Model unavailable, consistent with providers.<id>.models.<model>.disabled: true.

Plugins

Only the reproducing plugin itself (see steps). No other plugins.

OpenCode version

2.2.5 (macOS, arm64, shared background service; installed via homebrew)

Steps to reproduce

Prerequisite: any provider with ≥2 models (a custom openai-compatible provider in the user config works; no credentials needed for the catalog part).

1. In a scratch directory, save .opencode/plugins/model-filter.ts:

   import { Plugin } from "@opencode/plugin"
   
   const PROVIDER = "<provider-id>"   // e.g. a custom provider
   const KEEP = "<one-model-id-on-it>"
   
   export default Plugin.define({
     id: "model-filter",
     async setup(ctx) {
       await ctx.model.transform((editor) => {
         for (const model of editor.list(PROVIDER)) {
           if (model.id !== KEEP) editor.remove(PROVIDER, model.id)
         }
       })
     },
   })

2. Wait ~2s for the hot reload, then from that directory:

   opencode api get "/api/model?location%5Bdirectory%5D=$(pwd)"
   # → all of the provider's models are still listed
   
   opencode run --model <PROVIDER>/<a-removed-model> "Reply with exactly: OK"
   # → still succeeds

Evidence that the transform does run

Instrumenting the plugin with a file probe (plugin console.warn output does not appear in the server log):

12:09:59.189 transform registered
12:09:59.194 transform fired, removed 0, editor now lists 0      ← first pass, state still empty
12:09:59.217 transform fired, removed 16, editor now lists 3     ← second pass: removals applied

After the second firing the editor lists 3 models, yet GET /api/model for the same location returns 19, and explicit --model selection of a removed model succeeds. ctx.location inside the plugin matches the queried directory, so this does not look like a location mismatch.

Notes

• The two firings suggest the state rebuild pipeline re-runs transforms as documented, and the editor's own state converges correctly — the removals just never reach the registry that GET /api/model and model resolution read. From a quick source pass, ctx.model is built from host.model (packages/plugin/src/promise/adapter.ts), and State (packages/core/src/state.ts) re-runs registered transforms on rebuild, which matches the observed firings. I could not pin down where the two views diverge.
• The community plugin GaboEI/opencode-model-filters-v2 is built on the same hook and reports it working on 2.0.x, so this may be a regression in the 2.0 → 2.2.5 window.

References

• [FEATURE]: Add a native V2 replacement for provider model filtering #49986 — native replacement for V1 whitelist/blacklist; the bot's comment recommends this plugin pattern
• [FEATURE]: Model-level policies for per-model governance (model.use, or provider.use with provider/model resources) #61601 — model-level policies request; same recommendation
• provider.<id> whitelist/blacklist has no effect on the model picker (confirmed for both built-in opencode and openrouter providers) #61110 — user report that legacy whitelist has no effect