codex - 💡(How to fix) Fix Support per-skill disable for plugin-contributed skills [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19268Fetched 2026-04-24 10:39:43
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
1
Author
Participants
Timeline (top)
labeled ×4unlabeled ×1

Code Example

[plugins."vercel@openai-curated"]
enabled = true
enabled_skills = ["agent-browser"]
RAW_BUFFERClick to expand / collapse

Some plugins contribute too many skills to the session-visible skill list.

For example, the vercel plugin adds a large number of vercel:* skills, but I only want to keep vercel:agent-browser. Right now the config appears to support only enabling/disabling the whole plugin, not selecting individual skills.

This creates two problems:

  1. unnecessary noise in the visible skill list
  2. pressure on the model-visible skill budget, which can trigger warnings like:

Some enabled skills were not included in the model-visible skills list for this session.

It would be helpful to support per-skill filtering for plugin-contributed skills, for example via an allowlist or denylist in config.

Example desired behavior:

[plugins."vercel@openai-curated"]
enabled = true
enabled_skills = ["agent-browser"]

This would let users keep the few skills they actually use without disabling the whole plugin.

extent analysis

TL;DR

Implementing per-skill filtering for plugin-contributed skills via an allowlist or denylist in the config could resolve the issue of unnecessary skills being added to the session-visible skill list.

Guidance

  • Introduce an enabled_skills configuration option for plugins to allow users to specify which skills to include.
  • Update the plugin loading logic to respect the enabled_skills configuration and only add the specified skills to the session-visible skill list.
  • Consider adding validation to ensure that the enabled_skills list only contains skills that are actually contributed by the plugin.
  • Document the new configuration option and its usage to help users understand how to filter skills for each plugin.

Example

[plugins."vercel@openai-curated"]
enabled = true
enabled_skills = ["agent-browser"]

This example shows how the desired configuration could be implemented to only include the vercel:agent-browser skill.

Notes

The implementation details may vary depending on the underlying plugin architecture and configuration parsing logic. This solution assumes that the plugin system is designed to be extensible and configurable.

Recommendation

Apply workaround by introducing the enabled_skills configuration option to allow users to filter skills for each plugin, as this provides a targeted solution to the problem without requiring significant changes to the plugin system.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Support per-skill disable for plugin-contributed skills [1 participants]