Create and export in Plugin Studio. Install and run .boltplugin packages in the consumer PexarBolt app. For website submission, use the Studio MCP or standalone CLI plugin_submission workflow described below.
.boltplugin
plugin_submission
The developer platform is a separate repository, pexarbolt-developer-platform. It hosts a free plugin catalog, versioned MIT source, developer and review consoles, discussions, collaboration, and installation/update APIs.
pexarbolt-developer-platform
bolt-plugin package ./my-plugin ./my-plugin.boltplugin
The website accepts only .boltplugin packages containing editable source. Keep the host entry, implementation modules, schemas, projection and license notices in the package. If the runtime is compiled or bundled, include the original development project under source/, with build instructions and a lockfile. Add listing fields in listing.json, and complete the draft on the website. A runtime-only binary or a renamed .boltsubmission wrapper is not accepted.
source/
listing.json
.boltsubmission
Both standalone and Studio MCP expose plugin_package. Export the .boltplugin, then upload it in the developer console. Packaging does not submit, approve or publish a release. Legacy .boltsubmission exports remain useful for existing private archives but are not website upload files.
plugin_package
Sign in to the website and upload the exported .boltplugin in My plugins. For an existing plugin, use Upload a new version in its workspace. Complete publication-rights consent and submit for independent review there. Account settings manages your profile; publishing through the website does not require a developer token.
Plugins → Discover Plugins uses the public catalog and provides search, pagination, installation, and update checks. Sample previews are available on the website and in Studio. Only installations recorded as coming from the registry are checked for updates. Enabling and permissions continue through the existing PluginManager.
Set PEXARBOLT_PLUGIN_REGISTRY_URL to the deployed HTTPS origin. Development defaults to http://127.0.0.1:4310; packaged builds default to https://plugin.pexarbolt.ai. Override the environment variable when targeting another registry.
PEXARBOLT_PLUGIN_REGISTRY_URL
http://127.0.0.1:4310
https://plugin.pexarbolt.ai
Website install links use pexarbolt://install?registry=ORIGIN&release=UUID. The App accepts only the configured origin, fetches bounded metadata, checks compatibility, asks the user to confirm, downloads without redirects, verifies size and SHA-256, verifies package identity, and imports through the existing package validator. It never grants new permissions automatically. Firmware minimums are disclosed in the confirmation; negotiated device capabilities remain the final installation/runtime check.
pexarbolt://install?registry=ORIGIN&release=UUID
Anonymous installation-result reporting is opt-in. A one-use receipt is obtained only when selected. Download counts are separate from reported installs. Unlisted releases are installable by link after review and excluded from public discovery and normal update checks.
No firmware protocol changes are required: installed packages use the existing plugin contract and device transport. Web fixtures do not verify device behavior. Public deployment, real OAuth/email credentials, and a connected Dock require separate operator/hardware verification.
Every active registered user can upload and submit a release for review. Developer applications are no longer required. Uploads automatically check package structure, source, default configuration, sample state, runtime imports and supported sample interactions in an isolated browser worker. Read the returned findings and correct errors before submitting. See publishing. Consent, submission and publishing remain website actions.
Plugin detail pages show the .boltplugin download size, total unpacked package contents and an estimated resident Dock installation size. Source pages show the source download and every file's byte size. Sizes are computed from validated artifacts without running uploaded code, and existing releases are backfilled.
Dock installation is not the entire desktop package: host code and original source remain on the computer. The estimate includes the resident catalog, supplied 72px icon, native projection/assets and a 64KiB reserve for each device-direct data source plugin. It uses default settings; shared catalog/blobs, firmware filesystem allocation and runtime data can change actual usage. Transient live frames and system fonts are not persistent per-plugin installation bytes.