Agent Templates

  • Desktop app
  • All plans

What it does

A library of reusable agent definitions saved at your account level, organised in folders, ready to instantiate in any project. A template carries everything an agent is configured with: role (or an Expert / Community identity), provider, variant and model (including extended context or a free-typed model), the CLI account pinned per agent, system prompt, default skills, colour, browser access, always-memorize, personal flag, and the worktree mode. Creating an agent from a template copies the whole definition; the template's name becomes the agent's default name.

Where to find it

  • Sidebar, Agents tab (next to Projects): the folder tree of your templates, with New Agent Template to create one. Empty state: "No agent templates. Save reusable agents with names, roles, prompts."
  • Inside a project, the Add agent form offers Select an Agent Template to instantiate one.

How to use it

  1. Open the Agents tab of the sidebar and click New Agent Template ("Reusable agent config, saved to your account and available in every project").
  2. The form is the same as Add agent: pick a role or an expert, provider and model, write or preview the system prompt, choose default skills, colour and capabilities. Advanced options are expanded by default. Give the template a name and save (Create agent / Save changes).
  3. In any project, open Add agent, pick Select an Agent Template, and the agent is created with the template's full configuration.
  4. Right-click a template in the tree to edit, duplicate or delete it; drag it between folders.

A template whose worktree mode is "always" gives every agent created from it its own git worktree and branch, so several can work on the same repository at once.

Settings

None.

Agent tools (MCP)

None for templates themselves. agents_save creates or updates a project's agents, not the account library.

Providers

All providers: a template records the provider it was built with, and the agent created from it runs on that CLI. A CLI account pinned in a template is a machine-local identity: on another computer the agent falls back to the project or global default account.

Mobile

Not available on the mobile companion. Agents created from the phone use the room's Add agent sheet without templates.

Limits

  • Working directories and the choice of an existing worktree are hidden in template mode: they are absolute paths of one checkout and make no sense for an object that travels with the account. The dynamic worktree mode replaces them.
  • Default skills reference the skills of the project where the template was written; an unknown skill is ignored when the template is used in another project.
  • Templates sync through your account, so they need you to be signed in.

Common questions

  • Does a template keep my provider and skills? Yes. Since July 2026 the template stores the full configuration, not just role, model and prompt.
  • Why did the pinned CLI account not apply on my other Mac? Account pins are local to a machine; the agent uses the project or global default there.
  • Can I turn an existing agent into a template? Create a template with the same settings from the Agents tab; the form is identical to the agent's.
  • Where is a template's worktree option? In the form's worktree mode: "Every agent created from this template gets its own git worktree and branch".