Appearance
Best practices & agent design
The single biggest lever on agent quality is restraint: a small, focused agent with a few well-chosen tools beats one agent with everything switched on. This page covers how to keep agents lean, and how to combine several focused agents into something bigger — with delegation and teams.
In the app
Tools, knowledge, and connectors are per-agent switches on the agent's Settings tab — app.mychatbot.app/agents → pick the agent → Settings. Only turn on what that agent's one job needs.
Keep agents small & focused
A focused agent beats a kitchen-sink one. Resist the urge to build one agent with every tool, connector, skill, and knowledge source turned on. Build small, single-purpose agents and combine them (see Delegation & teams).
This isn't just tidiness — an over-loaded agent is measurably slower, pricier, and less accurate:
| Turning on more… | …costs you |
|---|---|
| Every connector / knowledge source | Each enabled one opens a live connection on every run — the more you attach, the slower each reply |
| Every extra tool + long instructions | Fills the model's limited working context, crowding out the actual task and making it likelier to pick the wrong tool |
| Constant tweaks to a bloated setup | A lean, stable setup caches better — cheaper and faster; a setup you keep changing can't reuse the cache |
Do / Don't
Do
- Give an agent only the tools, knowledge, and connectors its one job needs.
- Keep instructions short and specific.
- Split distinct jobs into separate agents, then wire them together with delegation or a team.
- Prefer attaching a knowledge source over pasting long reference data into instructions — it stays live and doesn't eat context. See Knowledge bases.
Don't
- Don't enable "everything just in case." Unused tools still cost context and cache stability.
- Don't pile unrelated skills / connectors onto one agent — it makes tool choice worse, not better.
- Don't grow one agent to cover two jobs when two simpler agents would do.
The platform practices this
MyChatBot itself ships many narrow specialists — a general assistant, a content maker, a site builder, a recruiter, and so on — rather than one do-everything agent. Mirror that: build the specialist, not the monolith.
Delegation & teams
Once your agents are small and focused, you combine them so no single agent has to do everything. There are two ways, and they behave differently:
| Delegation | Teams (Director) | |
|---|---|---|
| Shape | One agent hands a task to a peer | A Director leads a small team of specialists |
| Waits for the result? | No — fire-and-forget | Yes — coordinates, then replies |
| Where the answer lands | A new conversation, labeled [delegated] | The same conversation you're in |
| You see | A separate thread with the peer's answer | One synthesized reply, attributed per teammate |
| Best for | Firing a task off to run on its own | One coordinated answer from several specialists |
Delegation — hand a task to a peer
An agent with the Schedule & delegate capability can hand a task to another agent on your account. It's fire-and-forget: it kicks the other agent off and moves on rather than waiting. The peer's answer shows up in a new conversation, labeled [delegated] in your chat list — not in the original thread.
The agent already knows its peer agents and what each is good at, so it picks the right one for the job. Reach for delegation when a task needs a capability the current agent doesn't have. Sensible limits apply (a handful of delegations per conversation, scheduled from a minute up to about a day out).
Delegation rides the same switch as scheduling — see Tasks & schedules.
Teams — a Director coordinates specialists
A Director agent leads a small team of specialist agents but behaves like one agent to you: one chat thread, one reply. It routes each sub-task to the right specialist and stitches the results together, attributing each part to whoever produced it.
Reach for a team when you want a single coordinated answer that draws on several specialists at once. (Tools, skills, and connectors are configured per team member, not on the Director — see Agents overview → Directors and teams.)
Team vs. delegation, in one line
Use a team when you want one coordinated answer; use delegation when you want to fire a task off to run on its own.