Agents, apps and harnesses for your own Loams.
The Marketplace is where you will add ready-made agents, coding-agent harnesses, console plugins and factory apps to the Loams you run, and see exactly what each one asks for before you install it. It is not open yet: there are no listings and no install flow. This page says what it will be and what it builds on.
Coming soon. Nothing here can be installed today. The listing types, the name and the timing are still being decided; the roadmap will show it when work starts.
Four kinds of listing.
The design starts with first-party listings from the Loams repository; listings from other projects would come later.
Agents
Ready-made agents that work in Studio threads and on factory apps, with the tools and approvals they need declared up front.
Harnesses
Coding-agent CLIs that loams-agentd can install, update and run, beside the ones you already have.
Console plugins
Pages and panels for the Loams console, each with a manifest that lists the permissions it asks for.
Factory apps
Self-hosted apps for the Software Factory, pinned by image digest, with their licences shown before you install.
What it builds on.
The marketplace is new; the pieces it installs into are not.
The console plugin host
A plugin manifest, catalog files, sandboxed frames, permission checks and an action registry, with about 30 first-party plugins.
The harness catalogue
loams-agentd lists, installs and updates coding-agent CLIs and finds their skills, from a built-in list.
Pinned factory apps
The factory’s app images are pinned by digest in the repository (merged after 0.1.0), the first step toward an installable package.
Not a directory. A place things run.
Agent stores and MCP registries already list many thousands of servers and tools, and they will keep that lead. What a Loams listing can add is the runtime and the data under it.
A listing installs into something that runs it
Registries stop at discovery. A Loams listing installs into your own Loams: an agent in Studio, an app in the factory, a page in the console, with its data in your bucket.
See it before you install it
What gets created, which permissions each piece asks for and which licence it carries, shown before anything runs.
Open formats, not a new silo
The aim is to read the formats people already publish in, such as MCP server metadata and plugin manifests, rather than invent a closed one.
Help decide what comes first.
Which agents, harnesses or apps would you install first? Tell us on Discord, or open a discussion on GitHub. Meanwhile, Studio and the Software Factory work today.