How to disable remote plugin skill suggestion?

[jeiea]

After upgrading to 0.133.0, I started seeing much broader remote plugin/skill discovery during normal coding sessions. I tried setting tool_suggest = false under [features] in config.toml, and codex features list confirms it is disabled, but it does not seem to stop the broader discovery/search surface I am seeing.

› $draft

  Draft dashapi-publish-ver...  [App] Synthetic draft description
  Draft dashapi-publish-ver...  [App] Synthetic draft description
  Draft dashapi-publish-ver...  [App] Synthetic draft description
  DraftKings                    [App] Sports Scores: NFL NBA MLB NHL
  draft-pr                      [Skill] 유저에게 PR 초안 폼을 띄웁니다
  Bed-and-Breakfast.it          [App] Book Italian stays direct

Is there a supported way to disable remote plugin/skill discovery while keeping local/project/installed tools and skills available? In particular, I am looking for a setting that excludes remote marketplace/plugin/skill candidates from default sessions without turning off apps, plugins, or useful local/deferred tool discovery entirely.

[hoodrichpirobo]

I think there are two different surfaces being mixed together here.

[features].tool_suggest = false disables the model-side install-suggestion tools, i.e. the path where Codex can suggest/request installing a missing plugin or connector during a turn. It does not necessarily mean “hide every remote app/plugin/skill candidate from the composer autocomplete UI”.

The broader $... suggestions look more like plugin/app catalog discovery. For that, I do not see a documented fine-grained setting that means:

keep local/project/installed skills and plugins
keep local/deferred tool discovery
but exclude all remote marketplace/app/skill candidates

The closest coarse workaround is to disable remote plugin catalog support while leaving plugins themselves enabled:

[features]
plugins = true
tool_search = true
tool_suggest = false
remote_plugin = false

Then restart Codex or start a fresh session.

That should be understood as a workaround, not a precise “remote suggestions only” setting. It may also affect remote plugin install/update/share behavior, because it disables the remote plugin feature more broadly.

For individual noisy suggestions, the supported per-item mechanism appears to be [tool_suggest].disabled_tools, for example:

[tool_suggest]
disabled_tools = [
  { type = "plugin", id = "slack@openai-curated" },
  { type = "plugin", id = "github@openai-curated-remote" },
  { type = "connector", id = "connector_googlecalendar" },
]

But this is per plugin/connector, not a global “no remote marketplace candidates” switch.

So my current answer would be:

No, I do not think there is currently a supported user-facing config option that disables only remote plugin/app/skill discovery while keeping local/project/installed discovery fully enabled.

tool_suggest=false is narrower than that; it disables install suggestion tools, not necessarily composer/catalog autocomplete.

The closest available workaround is remote_plugin=false, plus tool_suggest=false if you also do not want install suggestions. If specific entries keep appearing, disable them individually under [tool_suggest].disabled_tools.

A cleaner product/API shape would be one of these:

1. A user config such as:
   remote_plugin_discovery = false

2. A tool_suggest option that makes discoverables a strict allowlist.

3. Composer/plugin-list callers using a local-only filter by default, for example plugin/list with marketplaceKinds=["local"], or plugin/installed for mention/autocomplete surfaces that should only show installed/local plugins.

Right now, the requested behavior seems to require a new setting or a change in the composer discovery path.