Factories > Factory agents
Creating custom agents
# Creating custom agents Add a custom agent for work that needs its own instructions, configuration, and runs. For example, create a documentation agent to update reference pages after code changes. ## Prerequisites * Team or workspace admin access, or the team-level [Warp Factories Editor role](/factories/infrastructure-and-security/#factory-roles-and-permissions). * An existing factory. Follow the [Warp Factories quickstart](/factories/quickstart/) to create one. ## Create an agent in the web app For a Warp-managed factory, create the agent in the <a href=https://platform.warp.dev>Warp Factories web app</a>. For a GitHub-backed factory, use [definition files](#define-an-agent-in-code) instead. 1. In the web app sidebar, click your factory to expand it, then click **Agents**. 2. Click **New**, then **Custom agent**. 3. Enter an agent name and a description of its responsibilities. 4. Under "Agent resources", choose the agent's [harness, model, host, and runner](/factories/factory-agents/configuration/) as needed. Add [MCP servers](/platform/mcp/) and [secrets](/platform/secrets/) for its tools. 5. Under "Agent prompt", enter the agent's instructions. 6. In the top-right corner, click **Save**. The new agent appears on the factory's **Agents** page. Agent names can't be changed after creation. <span id="create-an-agent-in-definition-files" /> ## Define an agent in code For a GitHub-backed factory, add `agents/<name>/agent.md` to the factory's definition repository, replacing `<name>` with the agent's directory name. Define its instructions and configuration using the [`agent.md` configuration keys](/factories/factory-as-code/#agentsnameagentmd). Follow your repository's pull request process to apply the change. ## Add skills Custom agents have no built-in skills. Add [factory skills](/factories/factory-skills/) where needed: * **One agent** - `agents/<name>/skills/` * **All agents** - `skills/` <span id="choose-a-configured-factory-agent" /> ## Dispatch a configured agent The foreman uses `run_agents` to dispatch configured factory agents. It receives a list of available agents and their unique IDs (UIDs), then: 1. The foreman chooses an agent from the available list. 2. It sets `remote` to run the child in the cloud. 3. For each child, it supplies the selected agent's UID in `agent_run_configs[].agent_identity_uid`. The `name` field only labels the child run. Unless overridden, the run uses the selected agent's environment, runner, host, harness, and model. You can start child agents without factory configuration through [multi-agent orchestration](/platform/orchestration/) from any Warp conversation. For scheduled or event-driven work, use [factory automations](/factories/automations/). The foreman coordinates the work they start. ## Related pages * [About factory agents](/factories/factory-agents/) - Understand default roles and human decision points * [Configuring factory agents](/factories/factory-agents/configuration/) - Edit instructions, models, harnesses, and tools * [Factory skills](/factories/factory-skills/) * [Factory automations](/factories/automations/) * [Definitions as code](/factories/factory-as-code/)Tell me about this feature: https://docs.warp.dev/factories/factory-agents/creating-custom-agents/Create a custom factory agent, add skills, and configure how the foreman dispatches it.
Add a custom agent for work that needs its own instructions, configuration, and runs. For example, create a documentation agent to update reference pages after code changes.
Prerequisites
Section titled “Prerequisites”- Team or workspace admin access, or the team-level Warp Factories Editor role.
- An existing factory. Follow the Warp Factories quickstart to create one.
Create an agent in the web app
Section titled “Create an agent in the web app”For a Warp-managed factory, create the agent in the Warp Factories web app. For a GitHub-backed factory, use definition files instead.
- In the web app sidebar, click your factory to expand it, then click Agents.
- Click New, then Custom agent.
- Enter an agent name and a description of its responsibilities.
- Under “Agent resources”, choose the agent’s harness, model, host, and runner as needed. Add MCP servers and secrets for its tools.
- Under “Agent prompt”, enter the agent’s instructions.
- In the top-right corner, click Save.
The new agent appears on the factory’s Agents page. Agent names can’t be changed after creation.
Define an agent in code
Section titled “Define an agent in code”For a GitHub-backed factory, add agents/<name>/agent.md to the factory’s definition repository, replacing <name> with the agent’s directory name. Define its instructions and configuration using the agent.md configuration keys. Follow your repository’s pull request process to apply the change.
Add skills
Section titled “Add skills”Custom agents have no built-in skills. Add factory skills where needed:
- One agent -
agents/<name>/skills/ - All agents -
skills/
Dispatch a configured agent
Section titled “Dispatch a configured agent”The foreman uses run_agents to dispatch configured factory agents. It receives a list of available agents and their unique IDs (UIDs), then:
- The foreman chooses an agent from the available list.
- It sets
remoteto run the child in the cloud. - For each child, it supplies the selected agent’s UID in
agent_run_configs[].agent_identity_uid.
The name field only labels the child run. Unless overridden, the run uses the selected agent’s environment, runner, host, harness, and model.
You can start child agents without factory configuration through multi-agent orchestration from any Warp conversation. For scheduled or event-driven work, use factory automations. The foreman coordinates the work they start.
Related pages
Section titled “Related pages”- About factory agents - Understand default roles and human decision points
- Configuring factory agents - Edit instructions, models, harnesses, and tools
- Factory skills
- Factory automations
- Definitions as code