diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json
index 65c9501d..b6bc5dfb 100644
--- a/.codex-plugin/plugin.json
+++ b/.codex-plugin/plugin.json
@@ -31,7 +31,7 @@
   "requires_local_executor": true,
   "interface": {
     "displayName": "Mergify",
-    "shortDescription": "Run and debug your merge queue, stacked pull requests, and Mergify configuration from the terminal.",
+    "shortDescription": "Run and debug your merge queue",
     "longDescription": "Mergify serializes merges through a queue that runs CI on temporary merge commits, so a pull request that only breaks in combination with another one gets caught before it reaches your default branch. These skills drive the Mergify CLI so an agent can work that queue with you.\n\nAsk why a pull request left the queue and get the engine's own dequeue reason, the checks that failed, and a link straight to the job log. Read the activity log for one pull request or for the whole repository. Validate a .mergify.yml against the schema before you commit it, or simulate what your rules would do on a real pull request. Set up merge protections such as dependencies between pull requests or scheduled freezes for a release window. Turn a branch of commits into a stack of one pull request per commit and keep them rebased.\n\nSix skills ship in the bundle: mergify-merge-queue, mergify-events, mergify-config, mergify-merge-protections, mergify-ci, and mergify-stack.\n\nIt runs on the Mergify CLI, a single static binary with no runtime to install, so it needs a local execution environment: Codex, or ChatGPT desktop with local execution. You need a GitHub repository with Mergify enabled. Install the CLI with 'brew install mergifyio/tap/mergify-cli', sign in once with 'mergify auth login' or set MERGIFY_TOKEN, then ask for what you want in plain language.",
     "developerName": "Mergify",
     "category": "Developer Tools",