Plugin runtime reach calculator
Free, runs in your browser · Catalog read
Pick the agent runtime your plugin supports today and the calculator ranks the runtimes other plugins in the HOL catalog add next, with the count and share behind each one. Of the 710 plugins that declare Claude Code, 367 (51.7%) also declare Codex, the most common next runtime. The figures come from 1,169 packaged plugins across 16 runtimes.
Calculator
Add Codex next. 367 of the 710 Claude Code plugins (51.7%) already declare it.
- 1Codex367 plugins · 51.7%
- 2Cursor184 plugins · 25.9%
- 3Antigravity CLI150 plugins · 21.1%
- 4OpenCode48 plugins · 6.8%
- 5Grok46 plugins · 6.5%
- 6Kimi Code31 plugins · 4.4%
- 7Copilot24 plugins · 3.4%
- 8OpenClaw11 plugins · 1.5%
Maintain a Claude Code plugin? The plugin converter writes the Codex and Gemini CLI manifests from the files you already have.
The next runtime for every runtime
For each of the 10 runtimes with at least 10 plugins, the runtime its plugins declare most often alongside it, and the one after that.
| Your runtime | Plugins | Most common next | In both | Runner-up |
|---|---|---|---|---|
| Claude Code | 710 | Codex | 367 (51.7%) | Cursor, 184 (25.9%) |
| Codex | 552 | Claude Code | 367 (66.5%) | Cursor, 124 (22.5%) |
| Cursor | 216 | Claude Code | 184 (85.2%) | Codex, 124 (57.4%) |
| Antigravity CLI | 183 | Claude Code | 150 (82%) | Codex, 102 (55.7%) |
| OpenCode | 95 | Claude Code | 48 (50.5%) | Codex, 28 (29.5%) |
| Grok | 61 | Claude Code | 46 (75.4%) | Cursor, 36 (59%) |
| DeepSeek Harness | 40 | Claude Code | 6 (15%) | OpenCode, 4 (10%) |
| Kimi Code | 33 | Claude Code | 31 (93.9%) | Codex, 23 (69.7%) |
| Copilot | 25 | Claude Code | 24 (96%) | Cursor, 13 (52%) |
| OpenClaw | 16 | Claude Code | 11 (68.8%) | Codex, 7 (43.8%) |
How the calculator counts
- It reads the same catalog snapshot as the runtime compatibility map: 1,169 packaged plugins, read on .
- For the runtime you pick, every other runtime is ranked by how many plugins declare both. The share is that count divided by the plugins that declare your runtime.
- Each figure stands for one pair. A plugin that declares three runtimes counts in three pairs, so shares never add up to a total and the calculator does not try.
- These are declarations, not install tests. They show where plugin authors aim, not where every plugin has been run.
- Only runtimes with at least 10 plugins can be picked as a starting point or appear in the graph.
Questions about runtime reach
Which runtime should a Claude Code plugin support next?
Of the 710 plugins that declare Claude Code, 367 (51.7%) also declare Codex, the most common next runtime. Cursor is next, at 184 plugins (25.9%).
Which runtime should a Codex plugin support next?
Of the 552 plugins that declare Codex, 367 (66.5%) also declare Claude Code, the most common next runtime. Cursor is next, at 124 plugins (22.5%).
Which runtime should a Cursor plugin support next?
Of the 216 plugins that declare Cursor, 184 (85.2%) also declare Claude Code, the most common next runtime. Codex is next, at 124 plugins (57.4%).
What does the share mean?
It is the part of the starting runtime’s plugins that also declare the other runtime. A high share means plugin authors who ship to your runtime usually ship there too, so users of that runtime expect to find plugins like yours.
Can I add the shares for two runtimes together?
No. A plugin can declare three or more runtimes, so the same plugin can sit in two pairs. The calculator reports each pair on its own and never adds pairs into a total.
Does a declared runtime mean the plugin was tested there?
No. The counts come from what each listing declares. HOL does not install every plugin in every runtime it names, so treat the figures as where authors aim their plugins, not as install results.
Ship to the next runtime
- Claude Code plugin converter: write the Codex and Gemini CLI manifests for a Claude Code plugin.
- Plugin pre-flight: check the packaging for Claude, Codex and Cursor before you submit.
- Runtime compatibility map: every pair of runtimes as a heatmap.
- Plugins that work in two runtimes: the best-scored plugins for each common pair.
- State of agent plugins: the monthly report on the catalog.