User Guide

Marketplace

The Marketplace is where extensions live in public. Install with a click, follow updates, and — if you've built one — submit it for review.

Browsing

Open the Marketplace from the sidebar. The search box matches name, description, and tags. The sort dropdown has four options: Trending, Most Popular, Newest, and Highest Rated.

The chips under the search row filter by category — All, Toys, Utilities, Integrations, each with a count. Tag chips sit to the right and stack with the category, so you can narrow to e.g. Toys + bluetooth. A Clear tags button appears once you pick any.

What's on a card

Icon, name, version, and category badge.
A short description, plus tags (the ones you're filtering by are highlighted).
Rating stars and review count, once an extension has been rated.
An install control, or a configure button if you already have it installed.

Installing

Click a card to open the detail page. You get the full description (links render), screenshots, the rating breakdown, and badges for things like Requires Bluetooth or Requires API Key. The primary action is a split button: the main option installs for all personas, and the dropdown lets you install to one specific persona instead.

If you already have it installed, the button changes to Configure extension and drops you onto the in-app extension detail page.

Rating and reviews

Below the install action on the detail page is a rating form: one to five stars and an optional written review. Ratings feed the Highest Rated sort and the stars shown on every card.

Submitting your own extension

Once you've built and tested an extension locally (see the Extensions page for the dev workflow), open the Marketplace and click Upload Extension. The form auto-saves as a draft in your browser, so you can close the tab and come back to it.

Form sections, in order

Marketplace Listing

Name, version, category, tags (up to 12), content rating (SFW or NSFW), short description (up to 320 characters), and detailed description (up to 6000, plain text plus links). Checkboxes for Requires Bluetooth and Requires API key.

Marketplace Icon

Three modes: use the icon from your manifest, upload a custom image (resized to 500x500 and compressed under 100KB), or pick a preset with foreground and background colours.

Extension Images

Up to three screenshots. They render in a gallery on the detail page.

Extension Package

Paste or load the manifest JSON and the JS module source. Loading from file pre-fills the listing fields where it can.

Changelog

A note on what changed in this version. Shown alongside the version on your listing.

A live card preview on the right shows how the listing will look. When you're ready, click Upload Draft. You land on a confirmation screen with a share link and a shortcut to My Extensions.

ℹ

Uploading creates a draft. Drafts aren't public. To put a version up for review, open My Extensions and click Request publish on it.

My Extensions

Open My Extensions from the Marketplace header. The page shows three counters (Owned, Published, Draft versions) and a row filter with All, Published, and Unpublished.

What each row offers

Edit listing — change name, category, tags, description, and icon.
View history — the version timeline for that extension.
Upload new version — opens the submit form for a new version.
Delete extension — only available while the extension has no published version.

Version statuses

A Draft is something you've uploaded but not submitted. You can edit it, share the preview link, or click Request publish to send it for review.

Pending review means it's sitting in the review queue. You can Withdraw at any point to pull it back to draft.

Approved is live on the marketplace. Changes requested means the reviewer wants edits; their note shows on the row, and Submit revision re-opens the form pre-filled with your last source so you can fix and resubmit.

Rejected is declined outright, with a reviewer note explaining why. Yanked is a version that was previously approved but has since been pulled from public listings, usually for a security or policy reason.

Version history

Every extension has a public history page at /marketplace/extensions/<key>/versions. Each row shows the version number, status, submission and review dates, the changelog, and (for approved versions) a download link for the raw manifest. Link to this page when someone asks “what changed in 2.4?”.

✦

Treat the changelog like a release note, not a commit message. People skim it to decide whether to update — describe what changed for the user, not what changed in the code.