Agent Template Library — webhouse.app Docs

Reusable agent presets — save your own as local templates, or browse the curated marketplace at github.com/webhousecode/cms-agents.

Two sources, one picker

The template library has two tiers, both visible on the Agents → Templates tab and on the Start from a template section of the new-agent page.

Tier	Where it lives	Who curates it
Local	`_admin/_data/agent-templates/{orgId}/{tplId}.json`	You — saved from existing agents via "Save as template"
Marketplace	`github.com/webhousecode/cms-agents`	webhouse.app team — open PRs welcome

Local templates are scoped to the org, not the site, so a template you save on one site is available on every site under the same org. Marketplace templates are global.

Saving a local template

Open any agent's detail page. The action bar has a Save as template button next to Clone. Click it and the agent's current configuration — name, role, system prompt, behavior sliders, tools, autonomy, target collections, field defaults — is copied into a new template.

What's not copied: stats, schedule, budgets, locale, active flag. Those belong to a running agent instance, not to a reusable preset. When you instantiate the template later, you set those fields fresh on the new agent.

The template is stored under the active org and visible to every site in that org's Templates tab and new-agent picker.

Deleting a local template

The Templates tab on /admin/agents lists all your local templates as cards. Each has a trash icon that opens the standard inline confirm pattern ("Remove? [Yes] [No]"). Click Yes and the template file is deleted.

Marketplace templates can't be deleted from the admin — they're read-only mirrors of the GitHub source.

The marketplace

When the admin loads the template list, it tries the marketplace in this order:

Primary: https://webhouse.app/api/agent-templates — the curated API on the main site (5-second timeout).
Fallback: https://raw.githubusercontent.com/webhousecode/cms-agents/main/manifest.json plus per-template fetches from the same repo.
Empty: if both sources fail, the marketplace section shows a soft warning and the picker still works for local templates.

Results are cached for 5 minutes per CMS process so the picker doesn't refetch on every keystroke.

Creating a new agent from a template

On the new-agent page, the Start from a template section shows two grids: "Your org" with your local templates, and "Marketplace" with the curated ones. Click any card and the form below is pre-filled with that template's payload. Tweak whatever you like, give the agent a name, save.

The form is still fully editable after pre-fill — templates are starting points, not constraints.

Contributing to the marketplace

The webhousecode/cms-agents repo is MIT-licensed and accepts pull requests. To add a template:

Add a new JSON file under templates/ matching the AgentTemplate shape.
Add a matching entry to manifest.json.
Open a PR with one paragraph on what the template is for and what kind of site you imagined while writing it.

Accepted templates must:

Have an opinionated voice (no generic "write a post about X" prompts)
Refuse hype words explicitly in the system prompt
Default to autonomy: "draft" (never publish without curator review)
Be honest about cost — mention if webSearch or imageGeneration is on
Work without per-site context