Overview
HiveBoss brings your team's conversations, calls, and files together into one place, and turns them into a shared memory your whole organisation — and its AI agents — can draw on.
The pieces
Chat and Waggle calls
Teams talk in direct messages, group conversations, and channels. Live voice/video sessions, called Waggle, can be started from any conversation and produce a recap afterwards — decisions made, action items assigned, and open questions left behind.
The Hive Mind
Everything your team discusses or imports — chat messages, call recaps, GitHub repos, Gmail threads, uploaded files — flows through an ingestion pipeline that extracts and structures knowledge into a graph called the Hive Mind. Related pieces of knowledge get linked together and deduplicated over time, so the Hive Mind stays a single, queryable source of truth rather than a pile of raw documents.
Bees
Bees are AI agents scoped to a department or role. A Bee can search and read the Hive Mind, write new knowledge back into it, and run automated workflows — all within the scope it's been given. Some Bees are built-in and handle background/automated jobs; others you configure yourself for a specific team or purpose.
Honey
Every time a Bee does work — answering a question, running a workflow, ingesting a file — it costs Honey, a usage currency tracked per organisation in a ledger. This is how you see and control how much AI usage your organisation is spending, and where.
Workflows
Multi-step automations that Bees can trigger and run against your Hive Mind, instead of you doing the same multi-step task by hand every time.
Suggested next steps
- Create or join an organisation and invite your team
- Start chatting, or import a first batch of knowledge (a repo, a folder of docs, an email thread) to seed your Hive Mind
- Configure a Bee for a department that could use one
- If you want an external tool (Claude, Cursor, Claude Code) to read or write your Hive Mind directly, see MCP Server