Hive
What it does
This is ithub Repo for the installer https://github.com/samkomedved319-dev/Hive-Desktop/releases Most AI desktops run one model at a time. A user asks a question, waits, then maybe starts a second pass. That is a queue, not a team. Hive is a Windows desktop workspace where several agents take the same user message at once. Scout searches. Hive writes. Pulse checks the live shape of the job. Critic reads Hive’s draft. Sentry can stop a tool call. They share one conversation room on disk, stream into the same chat, and show overlap on a live ops timeline. Around that core there is a 3D office view of the same agents, a cursor buddy that can click and type on the PC when asked, website login, and a one-click Windows updater. The product is the concurrent room. Everything else is how a person watches it work.
How the agents run concurrently
Agents that run together on one user message: Scout — web / lookup. Starts immediately. Does not wait for Hive. Hive — main writer. Starts immediately on the same prompt. Pulse — watches timing and job shape. Starts immediately. Critic — does not start with the others. It reacts when Hive emits an answer, then reviews that draft. Sentry — idle until a tool / function call is about to run. It can intercept and block. Shared state: one swarm room per conversation, persisted on disk. The room holds the user text, each agent’s partial tokens, tool events, and timestamps. The renderer subscribes to the same event stream, so the chat bubbles and the ops timeline are the same run, not a replay. Coordination: Mozaik runLoop, not a fixed pipeline. Scout, Hive, and Pulse are concurrent. Critic is event-driven off Hive. Sentry is event-driven off tools. If two agents overlap, the UI shows a swarm strip instead of hiding the second one. A group chat can @mention one bot so only that bot replies; without a mention, Hive is the speaker and the others still run in the room. What is not concurrent on purpose: the Windows installer update, website auth, and Buddy’s Fast/Auto/No mode. Those are product chrome. The hackathon claim is the shared room and the overlapping runLoop.
