Owns a job
Works from a clear responsibility
Set up persistent bots with a name, role, company membership, shared context, approved tools, repeatable skills, responsibilities, and a work history your team can review.
Start free. Give one bot one responsibility and one clear approval boundary.
Works from a clear responsibility
Draws from shared context and tools
Produces reviewable history and handoffs
The bot persists as a company participant instead of disappearing with the session.
Persistent role and company identity
Shared context and governed tools
Reviewable work with people in the loop
The broken workflow
A useful prompt or local subagent can complete a task. It does not automatically become a durable company participant with responsibility, context, access, and history.
Instructions and working memory disappear when the conversation or local environment ends.
Tools and credentials are wired for the session instead of granted to a company identity with a clear scope.
The bot output lands in a chat without a durable project, reviewer, next action, or improvement loop.
The HQ workflow
HQ connects identity, context, capability, responsibility, and review so a bot can keep contributing after the first task.
Name the bot, the job it owns, the output it produces, and the human who remains accountable.
Add the knowledge, skills, tools, project access, and boundaries required for that specific responsibility.
Let the bot complete a real task, review its history, and update the shared method before the next run.
Why HQ
HQ does not replace native bot features. It adds the persistent company layer around identity, access, memory, responsibility, and collaboration.
What the team can inspect
The useful proof is not a personality description. It is the connection between role, responsibility, context, capability, boundary, and completed work.
A named company participant with an explicit job and accountable human owner.
The bot receives only the knowledge, tools, skills, and projects required for its responsibility.
Runs, outputs, review, and corrections remain available for the team to inspect and improve.
What changes
Keep useful bots available beyond one session
Ground bot work in current company context
Make responsibilities, boundaries, and review explicit
Your first win
A narrow job with a visible owner and review boundary is the fastest way to prove value without pretending the whole company can run itself.
Set up your first botName the bot, its role, and the human owner
Grant one shared skill plus only the context and tools it needs
Complete one reviewable task and record the approval boundary
Built for company work
HQ makes bot identity, access, and company work explicit so teams can start narrow, review outcomes, and widen scope deliberately.
HQ bots are persistent AI teammates. They are not a promise of unsupervised autonomy or a substitute for accountable human ownership.
Start with one workflow
Start with one named bot, one useful responsibility, and one work product your team can review and improve.