Skip to product content
Products05 · Agents

HQ Agents

AI teammates that show up for work.

HQ Agents are persistent company teammates with a role, memory, tools, and responsibilities—not another chat window waiting for a prompt.

An HQ Agent working with teammates in Slack.
HQ Agents live in Slack alongside the rest of the team.

Why HQ Agents

Some work needs a teammate, not another chat.

A chat waits for someone to open it, explain the task, and keep the conversation moving. That works for one-off requests, but it does not create ownership.

Each HQ Agent has an identity, responsibilities, company context, and approved tools. It can keep continuity across requests and own work that continues over time.

How it works

Give the Agent a role and a place on the team.

01

Define the teammate

Give the Agent a name, role, responsibilities, and the company or team it belongs to.

02

Give it context

The Agent receives the relevant HQ memory, policies, Skills, and approved connections it needs.

03

Put it to work

Teammates can reach it in Slack, by email, or through direct assignments.

04

Let it initiate

The Agent can also begin work when a schedule or company event calls for it.

Part of the team

They work where your team works.

01

In Slack

Message an Agent in a channel or thread, bring it into conversations, and keep the work visible to the team.

02

Over email

Every Agent receives an email address, so it can receive requests, reply, and take part in the workflows that already run through the inbox.

An HQ Agent responding in Slack and visibly working on the request.
Agents are present in the conversation: teammates can see when they are thinking and when the work is ready.

Email identity

Every Agent gets an email address.

Give an Agent a real inbox identity so it can receive work, participate in email workflows, and reply as the same persistent teammate people already know from Slack.

An email sent by an HQ Agent from its persistent company email address.
The Agent keeps the same identity across Slack, email, and ongoing work.

Persistent by design

More than a chat window.

01

Identity

A consistent name, role, and place in the company.

02

Memory

The context to remember its responsibilities and continue the work.

03

Access

The company tools and connections it needs to do its job.

04

Responsibilities

Ongoing work it can own, not just one request at a time.

HQ Console showing provisioned Agents with names, roles, handles, and status.
Every Agent has a persistent name, role, handle, and place on the team.

Agents vs. HQ Workers

Agents are teammates. Workers are specialists.

Both are useful, but they solve different problems. Choose an Agent when the company needs a persistent owner. Choose a Worker when an active AI session needs a reusable specialist for one part of the job.

01

HQ Agent

An Agent has a persistent identity, memory, tools, and responsibilities. It communicates in Slack and email and works with the company over time.

02

HQ Worker

A Worker is a file-based, reusable specialist called inside an active AI session for a particular kind of work. It does not have its own Slack or email identity.

HQ Console Workers directory with the email-operator Worker expanded to show its durable files.
Workers live in HQ as reusable specialists with their own instructions, Skills, scripts, and queue.

HQ Agents

Add AI teammates to your company.

Give every Agent a role, the right context, and a place on the team.