Publishing to the marketplace
Upload a plugin, install it into a project, then publish it, three separate steps behind three different methods and one review gate.
Getting a plugin's code onto disk, installing it into a project, and putting it in front of other people are three separate actions, each behind its own method. None of them run automatically for the others.
Upload
upload_plugin saves the plugin's catalog document: its manifest (computed by scanning the
package the way the manifest page describes), its plugin_type, label,
description, tags, and version. This is where you create a plugin's record or push a new version
of an existing one. From the dashboard this is the Plugins tab's editor Sheet
(Tab_plugins.vue), reached from a project's Plugins section.
Install
install_plugin puts the plugin's package into one project: npm-installs it into that project's
own node_modules, and records it in the project's app_plugins_purchased map. A plugin can be
installed into a project without ever being public, this is how you develop against your own
upload before anyone else can see it.
Publish
publish_plugin is the explicit, separate toggle that makes an already-uploaded plugin visible in
the marketplace catalog (visibility: 'public') or pulls it back to owner-only
(visibility: 'private'). In the dashboard this is the Marketplace Visibility toggle on a
plugin you own. Uploading or updating a plugin's code never publishes
it by itself.
The review gate
Going public runs publish_plugin through an approval check
(marketplace_module.review_and_notify_external), unless the uploading account is a trusted
publisher (the legacy Xuda system account, or a configured platform supervisor). The result lands
the plugin doc in one of three states, mirrored onto both publish_stat and the legacy stat
field: 3 approved and live, 6 rejected (with publish_reason set, and an appeal link built from
approval.appeal_token), or 1 still under review. A rejected or under-review plugin is forced
back to visibility: 'private'.
publish_plugin refuses to go public (code: -403) unless the account has an active Stripe
Connect seller account, the same gate the project marketplace listings use. A trusted publisher
(the platform's own first-party plugins) skips this too.
Consent, on the installing side
Before install_plugin writes anything, it calls install_consent.build_plugin_consent() and
requires a matching accepted consent (with a content_hash the server recomputes and checks) in
the request. That screen is built straight from the plugin's manifest, see
the manifest page for exactly what each file present adds to it, plus the
npm package id and version being installed, and whether the plugin depends on another one.
The plugin upload agreement
dist/xuda_plugin_upload_user_agreement.html is a standing legal document: uploading a plugin
grants Xuda a worldwide, royalty-free license to use, reproduce, distribute and display it, and the
uploader represents the plugin is their own work, free of malware, and warrants they will indemnify
Xuda over it. It sits alongside two related agreements in the same dist/ folder, an application
upload and revenue-sharing agreement and a sample proprietary license agreement, all served as
static files off the platform's dist/ path the way xuda-runtime-slim.js and other runtime
assets are.
The API surface
Of the plugin methods, only get_plugins and get_plugins_categories are public clearance,
browsing the catalog needs no account. upload_plugin, install_plugin, uninstall_plugin and
get_app_plugins are admin clearance, scoped to a project. publish_plugin and archive_plugin
are dashboard-only actions and are not part of the public API.
Get Install Consent
Returns the install consent screen for one marketplace AI agent or plugin: what it does, who wrote it, the liability text, and the content hash the install has to echo back.