Skip to main content
A specialist that forgets everything between sessions starts from zero every time. HQ specialists don’t. They remember the work, arrive knowing your workspace, and get sharper the more your team relies on them — while leaving you in control of everything they know. For how this fits the rest of the architecture, see How HQ works.

​
Knows your workspace from day one

From the first message, a specialist already knows your channels, people, and the documents you connect. It reads your team’s past conversations — with consent — into a private index at install, so its very first reply fits how you already work, with no setup or re-explaining. Inviting the bot opts a channel in; removing it pauses.

​
Remembers across sessions

Memory persists between conversations and compounds over time:

About you

Preferences per person — like how you want briefs written — so replies stay in your style.

Accounts

Facts about the accounts you work, shared across the team, so context carries between people.

Skills learned

The steps that worked for recurring tasks, so the work gets faster each time it runs.

Grounded every turn

A specialist pulls the relevant background into each answer on its own, so you don’t re-supply context.
Memory consolidates while a specialist is idle, so it sharpens with use rather than just accumulating.

​
Yours to govern

You can always see what a specialist knows, then correct, delete, or freeze it. Memory is something you govern, not a black box — and that governance maps directly to the API.
Edit, delete, and freeze controls over stored data support your data-protection obligations under GDPR.
→ Read and manage what a specialist knows through the Memory API (memory:read / memory:write).