Publish and update
Upload your package in Creator Center, review its details, and submit for review. First-time publishers set up their identity before submitting.
Declare supported platforms
To publish, extension.json must declare a non-empty supportedHosts array containing web, desktop, or both. These values identify the product host: the desktop app remains desktop even when Electron renders its interface in a browser engine. Each MCP or Skill contribution may narrow supportedHosts to a subset of the extension’s platforms; omitting it inherits the top-level declaration. Every MCP listed in a Skill’s requiresMcp must be available on every platform that Skill supports. Web and Desktop each select the latest published release compatible with their own host, so they may use different versions.
1. Upload and check
ZIP limit: 5 MiB compressed, 20 MiB unpacked, 5 MiB per file, and 200 files. Place the manifest at the root. Preview checks structure, paths, Skill frontmatter, and MCP references; it does not execute code or verify service availability.
2. Set up your publisher identity
After preview, choose a display name and unique namespace. The namespace is permanent and must match the first part of your manifest ID. If taken, update the namespace and package ID, then upload again.
3. Submit and follow review
After submission, return to Creator Center and open your extension to see version statuses and review notes. Approved releases appear in the marketplace. Address rejection feedback and submit a new version number.
4. Update or withdraw
Upload new versions from the management page, keeping the same extension ID. Use numeric major.minor.patch versions such as 1.0.1; used versions cannot be overwritten. Withdrawal stops new distribution; it does not uninstall the extension from every user device.