Agent Template
A preconfigured bundle of driver, model, tools, skills, and prompt used to provision an agent in one step.
Definition
An agent template is a saved, preconfigured bundle of agent settings, driver, model, tool selection, skills, and system prompt, that Agenhood uses to provision a new agent in a single step, instead of requiring each setting to be chosen individually.
How it works in Agenhood
When a user provisions an agent from a template, the control plane applies the template's stored configuration to the new agent: which driver it runs on, Vanilla, Opencode, Codex, or Claude Code, which model it uses, which tools and skills are available to it, and what system prompt it starts with. The result is a new agent that is immediately ready to receive tasks, with a workspace volume and lifecycle state like any other agent, but without the operator repeating the setup work each time a similar agent is needed. Once provisioned, the agent is an independent record: changing the source template afterward does not retroactively alter agents already created from it.
Templates can be created for recurring roles, for example a code review agent with a fixed toolset and prompt, or a research agent configured to use a particular model and skill set, and then reused across a team whenever that role needs a new agent instance. A workspace can hold multiple templates side by side, covering different roles or different driver and model combinations, and users choose among them at creation time.
Why it matters
Provisioning from scratch is still fully supported in Agenhood, but templates reduce repeated configuration and make agent setup consistent across a team. They also act as a form of documentation: a template makes explicit which driver, model, tools, and prompt a given agent role is expected to use, rather than leaving that knowledge implicit in however the last agent happened to be configured. This matters more as a fleet grows, since it becomes impractical for every new agent to be configured by hand from first principles.
Related concepts
Using a saved configuration profile to provision a new instance quickly, rather than repeating manual setup, is a general pattern found across infrastructure tooling, from virtual machine images to infrastructure-as-code modules. Agenhood applies the same idea to agents: a template is not itself an agent, and has no runtime or workspace of its own, until it is used to provision one.