Skip to content

Templates overview

A template gets you a working agent in one step, instead of configuring one from a blank page. It’s a complete, reusable snapshot of an agent: who it is, what it needs connected, and how it starts.

A template captures what makes an agent that agent:

  • Persona files — the Markdown files that define its identity, tone, and boundaries. See Persona files.
  • Setup requirements — the integrations, connections, and skills it needs. A template never carries credentials, so you connect your own accounts.
  • Defaults — a recommended model, voice, avatar, and suggested agent name.
  • Curated memory — optional starter knowledge, loaded into the new agent.

A template can also hold workspace files for authors to build on. These stay with the template when you fork or republish it. Anything an agent must have on disk belongs in a persona file instead, because only persona files reach the agent.

Templates save effort in a few ways:

  • Skip the blank page. A new agent gets a real identity and a first-conversation plan instead of an empty prompt.
  • Stay consistent. Several agents can share the same standards and tone.
  • Reuse what works. Save an agent you’ve shaped, and create more like it, on any runtime.
  • Launch a whole team. A team pack creates several specialists that already work together.

Each release of a template is an immutable snapshot. Its files are copied, so it isn’t a live link to the agent it came from. A release you install today produces the same agent later, even if the source agent has changed.

Any change to a template’s persona, workspace files, integrations, or configuration creates a new version. Older versions stay available.

You’ll find templates in two places on the Templates page:

  • My Templates — ones you’ve created or saved. They’re private to your account until you publish them.
  • The marketplace — public templates, including Alfe’s built-in roles and ones published by other people. You can also browse it at alfe.ai/templates.

Alfe keeps these two actions separate on purpose:

Installing gives you a running agent, while forking gives you a template you own.