Skip to main content
An agent is a persistent, always-on AI worker — not a one-off chat session. Creating one takes a minute; the choices you make below shape how it behaves for its entire lifetime.

Who can create agents

Company admins can always create agents. Other members need the Allow creating agents permission, granted per member by an admin from Settings → Users. Trying to create an agent without it shows: “You don’t have permission to create agents. Ask your admin to enable it for you in settings.”
If your company has no active subscription, or has reached its active agent limit, agent creation is blocked with a message pointing you to the subscription page instead.

The creation form

1

Agent name

A short, descriptive name — shown everywhere the agent appears, including to the people who chat with it.
2

Image

Pick from a set of built-in avatars. Click the image to shuffle to another one at random.
3

Instructions (optional)

A system prompt describing the agent’s role, tone, and how it should behave — sent to the agent on startup.
Be concrete about scope: what the agent owns, what it should never do without asking, and how it should sound. Vague instructions (“be helpful”) do less than a short list of do’s and don’ts.
4

My business context (optional)

Free text describing your business, the tools you use, and your working style. The agent works without it, but context meaningfully improves results — the more specific, the better.This is different from your company’s shared context (set once under Settings → Context), which every agent receives automatically. Use the agent’s own context field for anything specific to that agent’s role, not facts every agent should already know.
5

AI model

Choose a model from a curated list, or leave it on the recommended default. If BYOK is enabled for your company, you can instead run the agent on your own LLM provider key — those agents never draw from your shared credit balance.
6

Execution engine (advanced)

For companies where Atako has enabled model selection, an advanced option lets you pick the agent’s underlying execution engine.
This choice is final. It can’t be changed after the agent is created — leave it on the default unless you have a specific reason to change it.
Channels aren’t part of the creation form — you turn them on afterward, from the agent’s own page. Integrations already connected at company level, however, can be granted directly in the creation form; you can add more, or connect new tools, later from the agent’s page. See Integrations overview and Channels overview.

Lifecycle

Agents are paused automatically in some cases — for example, when a free trial ends without a subscription in place — and can be resumed once the underlying issue (like billing) is resolved.
Ending an agent is permanent: it can’t be resumed, and its slot frees immediately. Its conversation history and files remain viewable. There is no manual pause — pausing only happens automatically (for example when a trial expires), and a paused agent can then be resumed.

Agent slots

Every active agent occupies one agent slot from your company’s shared pool. The number of slots equals what you’ve purchased on your subscription — a trial includes 3. Slots aren’t tied to human users: your team can have any number of members regardless of how many slots you own. Ending an agent frees its slot immediately for a new one. See Subscription for pricing per slot.

Agents

The concept behind agents, slots, and sub-agents.

Chat

Working with an agent day to day.

Team

Roles, permissions, and inviting teammates.

Credits

How model usage and BYOK are metered.