When to Create a Custom Agent (and When Not To)
This article explains when it makes sense to create a custom agent in Moterra and when the General Assistant is a better choice. Creating custom agents helps keep behavior consistent, but not every use case requires one.
Written By Kristė Vagnerytė
Last updated 22 days ago
When You Should Create a Custom Agent
Create a custom agent when you need more control over how the assistant behaves.
Custom agents are useful when:
The same type of task is repeated frequently
The assistant needs to follow specific rules or instructions
Only certain tools should be available
Access should be limited to specific users or teams
Consistent answers are more important than flexibility
In these cases, a custom agent helps reduce variability and improves reliability.
When You Should Not Create a Custom Agent
A custom agent is not always necessary.
The General Assistant is usually enough when:
Tasks are one-off or vary a lot
You need flexible, exploratory answers
The instructions change from request to request
You don’t yet know what the agent’s main responsibility should be
If you find yourself frequently changing instructions, it’s a sign that a custom agent may be too early.
Signs an Agent Is Too Broad
Custom agents work best when they have a clear focus.
An agent may be too broad if:
It tries to handle many unrelated tasks
Its instructions become long or contradictory
Users are unsure what to use it for
Output quality varies a lot between requests
In these cases, splitting responsibilities into multiple custom agents often works better.
General Assistant vs Custom Agents
Use the General Assistant when you want flexibility and quick answers.
Use Custom Agents when you want:
Predictable behaviour
Clear boundaries
Controlled access and tools
Both have their place, and many teams use them together.