chore: generate Codex, Cursor, and Antigravity plugin manifests#124
Conversation
Generated via the plugin-dev multi-format generator from
.claude-plugin/plugin.json (source of truth):
- .codex-plugin/plugin.json — Codex runtime manifest
- .cursor-plugin/plugin.json — Cursor runtime manifest
- plugin.json — Antigravity root manifest
- hooks.json — Antigravity root hooks (mirrors hooks/hooks.json with
${CLAUDE_PLUGIN_ROOT}/ rewritten to ./)
No MCP servers are declared, so no .mcp.json was generated.
release-please-config.json's extra-files for the root ask-plugin
package now include all three new version-bearing manifests, so their
$.version stays synced with .claude-plugin/plugin.json on release.
|
Warning Review limit reached
Next review available in: 45 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Up to standards ✅🟢 Issues
|
Greptile SummaryThis PR adds generated plugin manifests for more runtimes.
Confidence Score: 4/5The new runtime manifests are mostly straightforward, but the Antigravity hook path can break outside the plugin root.
hooks.json, .cursor-plugin/plugin.json Important Files Changed
Prompt To Fix All With AIFix the following 2 code review issues. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 2
hooks.json:10
**Hook Path Depends On Cwd**
When the hook runner starts commands from a user's workspace instead of the installed plugin root, `node "./hooks/fetch-hint.mjs"` resolves against that workspace. Node then cannot find the plugin's `hooks/fetch-hint.mjs`, so the WebFetch PreToolUse hint hook fails before the script can run.
### Issue 2 of 2
.cursor-plugin/plugin.json:5
**Cursor Manifest Lacks Capability Metadata**
The Cursor manifest only carries display metadata, while the Codex manifest declares the plugin capability as `Skill`. If Cursor's loader uses manifest-declared capabilities to register provided skills, this file can load as a metadata-only plugin and leave Ask's skills unavailable in Cursor.
Reviews (1): Last reviewed commit: "chore: generate Codex, Cursor, and Antig..." | Re-trigger Greptile |
Deploying ask with
|
| Latest commit: |
60091a1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://28bbb0a6.ask-6im.pages.dev |
| Branch Preview URL: | https://chore-multi-runtime-plugin-m.ask-6im.pages.dev |
There was a problem hiding this comment.
1 issue found across 5 files
Architecture diagram
sequenceDiagram
participant SOT as Source of Truth (.claude-plugin/plugin.json)
participant Gen as Multi-Format Generator
participant CP as Codex Plugin (.codex-plugin/plugin.json)
participant CursorP as Cursor Plugin (.cursor-plugin/plugin.json)
participant AGP as Antigravity Plugin (plugin.json)
participant AGH as Antigravity Hooks (hooks.json)
participant RP as Release Please Config (release-please-config.json)
participant Client as Agent Client (Codex/Cursor/Antigravity)
Note over SOT,RP: Manifest Generation Flow
SOT->>Gen: read plugin metadata (name, version, description, author, etc.)
Gen->>Gen: transform to Codex format (interface.displayName, category, etc.)
Gen->>CP: write .codex-plugin/plugin.json
Gen->>Gen: transform to Cursor format (displayName, tags, etc.)
Gen->>CursorP: write .cursor-plugin/plugin.json
Gen->>Gen: transform to Antigravity root format (no interface block)
Gen->>AGP: write plugin.json
Gen->>Gen: rewrite path references (${CLAUDE_PLUGIN_ROOT}/ → ./)
Gen->>AGH: write hooks.json (mirror of hooks/hooks.json with rewritten paths)
Gen->>RP: register extra-files entries for version syncing
Note over CP,AGP: Runtime Loading Flow
Client->>CP: load manifest (Codex runtime)
Client->>CursorP: load manifest (Cursor runtime)
Client->>AGP: load manifest (Antigravity runtime)
Client->>AGH: load hooks (Antigravity runtime)
alt Version Update Triggered
RP->>RP: on release, bump $.version in all manifests
RP->>CP: sync version to 0.4.11
RP->>CursorP: sync version to 0.4.11
RP->>AGP: sync version to 0.4.11
end
Note over Client: Plugin loaded with capabilities metadata
Client->>Client: initialize plugin based on manifest
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Deploying ask-registry with
|
| Latest commit: |
60091a1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d7a7f4ad.ask-registry.pages.dev |
| Branch Preview URL: | https://chore-multi-runtime-plugin-m.ask-registry.pages.dev |



Summary
Generated via the plugin-dev plugin's multi-format generator, using
.claude-plugin/plugin.jsonas the source of truth. Adds runtime manifests for theaskplugin so it loads in Codex, Cursor, and Antigravity in addition to Claude Code.Changes
.codex-plugin/plugin.json— new Codex runtime manifest.cursor-plugin/plugin.json— new Cursor runtime manifestplugin.json— new Antigravity root manifesthooks.json— new Antigravity root hooks (mirrorshooks/hooks.json, with${CLAUDE_PLUGIN_ROOT}/rewritten to./)release-please-config.json— added the three new version-bearing manifests to the rootask-pluginpackage'sextra-files, so their$.versionstays synced with.claude-plugin/plugin.jsonon releaseNo MCP servers are declared for this plugin, so no
.mcp.jsonwas generated.Test Plan
.claude-plugin/plugin.jsonrelease-please-config.jsonextra-files wiring includes all three new manifestsRelated Issues
None — no linked issue for this chore.
Summary by cubic
Generated runtime manifests for the
askplugin so it loads in Codex, Cursor, and Antigravity, and synced their versions viarelease-please..codex-plugin/plugin.jsonand.cursor-plugin/plugin.json.plugin.jsonandhooks.json(mirrorshooks/hooks.jsonwith path rewrite).release-please-config.jsonto keep new manifests’$.versionaligned with.claude-plugin/plugin.json.Written for commit 60091a1. Summary will update on new commits.