plugin dependency system where a plugin can depend on other plugins
What variant of Codex are you using?
App, IDE Extension, CLI
What feature would you like to see?
A plugin dependency system where a plugin can depend on other plugins. Installing the parent plugin would first install all the dependent plugins.
Additional information
Background
I use some plugins, skills, mcp servers in my day to day work. I am trying to encapsulate them all to create my own "setup" plugin which can be a one click solution to setup my stack on a vanilla codex installation. But to be a real one click stack setup plugin it needs to have the capability to install other plugins(that I use) as well.
Example
for example, if my setup plugin depends on the famous superpowers plugin. then installing the setup plugin will first install the superpowers plugin and then install itself. the end result is that both plugins are available after installing only one.
2 Comments
Plugin dependency systems are genuinely useful for composable AI workflows — being able to declare that skill X depends on skill Y means the orchestrator can install them together rather than requiring manual setup.
One thing to consider from a cost management perspective: plugin dependencies often mean more API calls in sequence, which can stack up quickly in token-based billing. A well-designed dependency system should let you preview the total cost before executing — something most current plugin systems skip entirely.
If you're building this, it might be worth adding a 'dry-run' mode that shows which plugins would load and what the estimated token overhead would be. That's the kind of cost visibility that turns a good plugin system into a great one.
Claude Code has implemented this, would be great to have parity: https://code.claude.com/docs/en/plugin-dependencies