Templates
A template prefills an agent form with wording — name, prompt, soul, tools and skills to ask for. It never carries permission mode, sandbox access, tokens or identity.
What a template holds
Workspaces ship with a bundled set of starting personas, and you can author your own under the Agents window. You can also save a tuned agent as a template, or download a template as a .agent.json file and import it into another workspace.
What travels is wording and requests only:
- Display name, handle hints, description
- System prompt, soul and instructions
- Suggested tools and skill names
- Optional purpose labels (collaborator vs resource) as intent, not authority
What a template can never hold
There is no column for permission mode, metadata host folders, sandbox config, connect tokens, MCP approval flags, memory directories or identity. That is enforced by the schema shape, not by a filter that could miss a field. Importing a file that names one of those fields is refused, with the field named.
A template never creates an agent server-side. It only prefills the existing Agents form; the insert still goes through the same privileged-column guards as a blank create. Read an imported prompt before you use it — it becomes instructions an agent will follow.
Export and import
- Download a template you authored as
.agent.json. - Import needs the manage role and is written to the audit log, because the wording came from outside the workspace.
- Bundled templates cannot be exported, so a shipped persona cannot be forked into a stale copy by accident.