Agents
Agents are your AI employees. On this screen you create them and set their personality, behavior, model, skills and what they are allowed to do. The screen is scoped to a workspace — selector at the top. Agents are shown as tiles: icon, name, model (or “default model”), status, a preview of the system prompt, and “Profile” / “Delete” buttons.
Creating an agent
The “+ Create” button opens a modal with the basic fields:
- Name — required, shown in lists and channels.
- Avatar — an emoji or an image URL.
- System prompt — the text that defines the role and behavior rules.
- Model — a model id; leave it empty to use the default from the provider chain.
That is enough for the agent to work. Fine-tuning happens in the profile.
Agent profile
The “Profile” button opens an editor with independently saved blocks.
Identity
Short and full name, role, how to address the user, mood, gender (unset / male / female / other), character (free text), personal phone and e-mail. These fields form the employee’s “personality” and how it introduces itself in channels.
Mailbox
Appears once the agent has a personal e-mail: IMAP and SMTP parameters (host, port, user, password). Passwords are write-only and never read back. This lets an agent work with its own inbox.
Behavior sections
A set of accordions, each with an “enable” checkbox and a text body:
known_user, rules, safety, capabilities, memory_policy,
refusal_style, response_format, escalation, persona_constraints.
This — not a separate set of “permission checkboxes” — is where you define what an
agent may and may not do: describe it in safety, capabilities and rules.
Shared blocks
You can link company-wide shared blocks from the workspace catalog (a single set of company rules) — see Skills & prompts. A block shows a sensitivity badge.
Skills
The agent’s own skills (create/edit/delete: name, description, body, enabled, order; the slug is generated by the server) plus linking the workspace’s shared skills.
Setting rights and model
- Rights/permissions are described in the
safety/capabilities/rulessections and through the set of available skills and tools. Real risky actions pass through Approvals and Moderation. - Model can be set at creation (free text) or left empty for the default; which models are allowed at all is on Instructions → allowed models.
Tips
- Keep the system prompt short and push details into sections and shared blocks — they are easier to reuse across agents.
- Sensitive shared blocks are edited through the approvals queue.
Next
- Orchestration — wire several agents into a graph.
- Skills & prompts — reusable blocks.
- Models — providers and priority.