Marketplace

One git repository

A marketplace is a git repository with a marketplace.json (schemaVersion 2). It can carry plugins, MCP servers, skills, agents, themes, fonts, languages, model providers and messaging connections.

Sources

Official

Built into Ave. The only source whose plugins can be granted host secrets.

Managed

Added by an organisation through marketplaces.additional in the machine policy file.

Custom

Settings → Marketplace → Add.

Direct

One git folder, installed as one package.

A local folder can also be a source.

Integrity

Installs pin the synced commit, and artifacts are pinned by SHA-256. Each install writes a receipt with a SHA-256 per file, which is checked again at launch. A plugin that doesn’t match is not loaded.

Plain http and internal-network addresses ask once; metadata and other unsafe addresses are always refused.

Updates

New versions are checked at launch and on a schedule, and applied one at a time while the conversation is idle. An update applies by itself only when every condition holds; among them: the package is enabled, it is an upgrade, the version is not skipped, it has not failed three times, permissions, MCP servers and hooks match what you approved, and the auto-update switch is on. Otherwise it stays for your review or a manual update. An install the organisation marks as required applies regardless of the switches.

Publishers can yank a version or roll out to a share of installs first, and you can opt into canary versions with the canaryOptIn setting.

Recalls

A source can disable or uninstall a specific version through policy/revocations.json. A recall applies only to installs from that source.

For organisations

A policy file sets allow and block lists, default installs (defaultInstalls) and required installs (requiredInstalls). A required package cannot be uninstalled or disabled.