Marketplace

The marketplace is where the machines of one beam host share vApps and skills. Each one is a git repository on the Forgejo behind your beam host, published from the machine that made it. Other machines install it from there and pull it again when it changes.

It needs a beam host with a Forgejo set up (Running a beam host). Without one, the page says so and links to Settings > Beam.

The page

Open Marketplace from the command bar, from its card under Built-in on the vApps page, or at /market. Each row shows:

• the title, description and icon, and whether it is a vApp or a skill
• the machine that published it
• for a skill, the source it was adapted from and the commit, when it has one
• whether it is listed, or yours

Filter by All, vApps or Skills, and search by text. Refresh reads the marketplace again; the page also does when you come back to the window.

Install brings an item onto this machine. Once it is installed, the button reads Update and pulls the published version again. A skill you edited here since its last install is not overwritten: the update stops and says which files changed, and Replace, losing those edits does it anyway.

The vApps page's Marketplace shows the same list, vApps only, and a first install there still opens the import preview. Skills too opens this page.

Publishing

• A vApp publishes from its backstage, under Share (vApps).
• A skill publishes from Enhance > Skills, after you fork it and edit the copy.

Turn on Listed to let the other machines on the host see it. An unlisted item is yours alone, which is useful while you are still working on it. Publishing again keeps the listing as it was unless you change the switch.

Bedos and sessions

A session asks the marketplace with market_list and installs from it with market_install, which needs configure on that machine. A Bedo can share a published skill in a thread, where it shows up as a card with an Install button (Bedos).