Files
IdeaSDK/docs/codex-skills-and-idea-plugins.md

42 lines
1.9 KiB
Markdown

# Codex Skills And IdeA Plugins
IdeA runtime plugins and Codex plugins are separate installation and discovery
systems.
An IdeA runtime plugin is described by `idea-plugin.json`. Installing it through
IdeA makes its IdeA runtime contributions available: menus, menu items, slash
commands, layouts, MCP servers and runtime services declared by the IdeA plugin
manifest.
A Codex plugin is described by `.codex-plugin/plugin.json`. Its `skills` entry
points Codex at skill directories such as `skills/*/SKILL.md`. This metadata is
for Codex plugin installation and skill discovery, not for IdeA runtime plugin
loading.
## Normative Behavior
- Installing or reloading an IdeA plugin does not automatically install a bundled
Codex plugin.
- Installing or reloading an IdeA plugin does not automatically make bundled
Codex skills available to agents in the current project.
- Installing or reloading an IdeA plugin does not automatically make bundled
Codex skills available to agents in other projects.
- No `idea-plugin.json` manifest field currently declares Codex skills for IdeA
agent assignment.
- Bundling `.codex-plugin/plugin.json` and `skills/*/SKILL.md` inside an IdeA
plugin package is allowed as distribution content, but it is inert for IdeA
runtime plugin loading unless a separate bridge explicitly consumes it.
## Required Mechanism
If a plugin needs Codex skills to be available to agents, install the Codex
plugin through the Codex plugin mechanism for the intended scope, then assign or
enable those skills for the relevant agents according to Codex/IdeA agent
configuration.
Do not rely on IdeA plugin installation as a cross-project skill propagation
mechanism. Cross-project skill availability needs an explicit product contract
covering scope, provenance, permissions, uninstall behavior, hot reload,
collisions and security. Until that bridge exists, document and perform Codex
skill installation separately from IdeA runtime plugin installation.