Skip to content

[codex] Pass plugin namespace into skill loading#28608

Merged
mzeng-openai merged 3 commits into
mainfrom
dev/mzeng/pass-plugin-skill-namespace
Jun 18, 2026
Merged

[codex] Pass plugin namespace into skill loading#28608
mzeng-openai merged 3 commits into
mainfrom
dev/mzeng/pass-plugin-skill-namespace

Conversation

@mzeng-openai

Copy link
Copy Markdown
Collaborator

What changed

  • retain the parsed plugin manifest namespace on loaded plugins
  • carry that namespace through PluginSkillRoot and SkillRoot
  • use the provided namespace when qualifying plugin skill names
  • include the namespace in the skills cache key

Why

Plugin loading has already parsed plugin.json, but skill parsing currently walks every SKILL.md ancestor and probes/reads the manifest again to reconstruct the same namespace. Passing the parsed namespace removes those repeated filesystem calls, which are particularly costly on remote filesystems.

Context: https://openai.slack.com/archives/C0ARA9GF5D4/p1781639496496439?thread_ts=1781202444.891669&cid=C0ARA9GF5D4

Impact

Plugin skill names remain unchanged. A regression test uses a deliberately different on-disk manifest name to verify that plugin roots use the provided parsed namespace.

Validation

  • just test -p codex-core-skills -p codex-core-plugins -p codex-plugin -p codex-utils-plugins (352 passed)
  • just fix -p codex-core-skills -p codex-core-plugins -p codex-plugin -p codex-utils-plugins
  • just fmt

@mzeng-openai mzeng-openai force-pushed the dev/mzeng/pass-plugin-skill-namespace branch from 3c13af5 to 8ccb4cf Compare June 18, 2026 05:01
@mzeng-openai mzeng-openai force-pushed the dev/mzeng/pass-plugin-skill-namespace branch from 8ccb4cf to bb0c68f Compare June 18, 2026 05:17
@mzeng-openai mzeng-openai merged commit c73296a into main Jun 18, 2026
57 of 63 checks passed
@mzeng-openai mzeng-openai deleted the dev/mzeng/pass-plugin-skill-namespace branch June 18, 2026 07:16
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants