Skip to main content
A worker is one Slack app with one name. People address it the way they address a colleague: in a channel, by @-mention, or in a DM. It has a role, a list of responsibilities, a list of behaviors, memory of its own, and skills it can run. Everything about it is on its page in control, under Workers. One worker can serve many clients. For each client, it gets a separate copy with that client’s memory and nothing of any other client’s. Your own team talks to a copy that holds every client’s memory. You never see the copies; you see one worker.

​
The worker’s page

The header shows the avatar, the name, the role title, a status badge, and, once the worker serves clients, a context picker: Internal or one client. The picker decides which copy the Tasks, Knowledge, Connections and Triage tabs show.
TabWhat it holds
OverviewThe four role cards: Responsibilities, Out of scope, Behaviors, When they conflict.
ClientsThe clients, channels and people this worker serves, and the Add to client button.
TasksScheduled tasks for the chosen context, with Run now, History, Edit, Disable.
KnowledgeThe memory browser for the chosen context, and the worker’s tools.
ConnectionsThe apps that reach this worker in the chosen context.
TriageWhether it is awake, recent conversations, and Restart.
SettingsIdentity, runtime, response behavior, escalation, email, and the danger zone.

​
Creating a worker

Ask your AI Admin, or press New Worker on the Workers page. The wizard has five steps: Identity (name, job title, who it reports to, and a drafted responsibilities list), Clients, Slack & channels (an Add to Slack window; click Allow), Tools, and Launch, which ends with Say hello to <name>: send it a message to prove it works.

Identity

Name, avatar, Slack app, email address.

Role

The job title and what it is for.

Responsibilities

What it is accountable for, and what is out of scope.

Behaviors

Avoid, Don’t, Prefer, Use.

Channels

Where it works: Slack, email, the web.

Knowledge

Memory and skills.