Installing from the catalog
What happens when you click Install — per-kind semantics and where the data lands.
You don't install assets here — the marketplace is the catalog. The Install button on a listing detail page sends the install request to your own Enclaw tenant, where the asset gets registered or cloned.
How to install
- Browse the catalog at / and open the listing you want.
- Click Install. You'll be redirected to your Enclaw tenant's
marketplace page (
<your-enclaw>/marketplace) with the listing pre-selected. - Pick which agent / squad / tenant context the asset should land in.
What lands in your tenant
The kind of the listing determines whether the install creates a reference (a binding to the marketplace listing, where version bumps flow through automatically) or a clone (a fresh copy in your tenant that you own and can edit freely).
| Kind | What lands |
|---|---|
| Skill | Registered as a callable tool on the selected agent (or all agents if scoped wide). Stays a reference to the marketplace listing — version bumps are available later. |
| Integration | Registered as a tool family; you fill in configSchema values (API keys, OAuth tokens) which are encrypted at rest in your tenant. |
| Agent template | Cloned into your tenant's agent_templates. You can edit identity / model / skills freely without affecting the marketplace listing. |
| Workflow template | Cloned into your tenant's workflow_templates — the steps, trigger, and references are copied verbatim. Edit it as your own. |
| Squad template | Cloned into squad_templates + the squad's referenced agent templates are also cloned (so an update to the squad doesn't depend on the agent listings still existing). |
Sign-in
You don't need to sign in to the marketplace to install — the catalog browse is anonymous. You do need to be signed in to your Enclaw tenant before clicking Install (the redirect lands you on a tenant page that requires the tenant's own auth).
What gets stored where
- The marketplace records an install row (anonymous, for download counters) but does not record which tenant installed.
- Your tenant stores the cloned templates or the binding in its own Postgres. Marketplace asset payloads (system prompts, tool schemas, workflow steps) are visible in the tenant's normal UI — no marketplace round-trip needed at runtime.
- Configured secrets (integration tokens) live encrypted in your tenant's secrets store, not in the marketplace.