@chrome mention loads plugin path but does not surface/load Chrome skill

Summary

In Codex Desktop, tagging or mentioning @chrome does not reliably load or show the Chrome skill. The user-facing behavior is that Codex keeps "loading plugins", but the @chrome skill itself does not appear/load.

Expected behavior

When a user mentions @chrome, Codex should load and surface the Chrome skill (chrome:Chrome) because the installed Chrome skill explicitly declares that it should be used for @chrome.

Actual behavior

User reports:

whenever I tag @chrome the skill doesn't load @chrome, it keeps loading plugins but the skill also doesn't show

This looks like a plugin/skill routing or mention-resolution issue: the Chrome plugin package exists, and the skill exists, but the @chrome mention does not appear to activate the matching skill in the UI/context.

Local environment evidence

• Codex Desktop app:
  • Bundle ID: com.openai.codex
  • Version: 26.513.20950
• Codex CLI:
  • codex-cli 0.130.0
• Chrome plugin package:
  • Manifest: ~/.codex/plugins/cache/openai-bundled/chrome/0.1.7/.codex-plugin/plugin.json
  • Manifest values:
    • name: chrome
    • version: 0.1.7
    • interface.displayName: Chrome
    • skills: ./skills/
• Chrome skill file exists:
  • ~/.codex/plugins/cache/openai-bundled/chrome/0.1.7/skills/chrome/SKILL.md
  • Frontmatter:
    • name: Chrome
    • description: Browser automation for the user's Chrome browser...
  • Relevant skill instructions:
    • Line 8: Use this skill when the user mentions @chrome.
    • Line 13: For bare or general @chrome requests, do not ask a clarification question... Proceed with browser automation in this skill using the chrome backend.

Reproduction steps

1. Use Codex Desktop with the Chrome plugin installed/enabled.
2. In a Codex thread, tag or mention @chrome, for example:
   • @chrome
   • @chrome open example.com
3. Observe that Codex/plugin loading starts, but the Chrome skill does not appear/load as the active skill.

Impact

Chrome-backed requests may fail to route to the skill that contains the required behavior and safety constraints for the Codex Chrome Extension. In particular, the skill says @chrome requests should use the Chrome backend and should not fall back to unrelated automation paths if extension communication fails.

Possible area to inspect

The issue may be in mention routing between the plugin identifier/display name (chrome / Chrome) and the generated skill identifier (chrome:Chrome), or in UI/plugin loading where the plugin loads but its bundled skill metadata is not surfaced for @chrome.