cd /news/ai-agents/show-hn-agent-hive-cute-grokbot-like… · home › topics › ai-agents › article
[ARTICLE · art-172232] src=github.com ↗ pub= topic=ai-agents verified=true sentiment=↑ positive

Show HN: Agent Hive – cute Grokbot like agentic teams with queen and many bees

Eric Wang released Agent Hive, a free, MIT-licensed macOS app that runs multiple coding-agent CLIs — Claude Code, Codex, Gemini CLI and Cursor Agent — concurrently as a coordinated team, with a lead agent called Queen dispatching work to individual "bees." In a measured three-round task, Agent Hive reported a bee carried about 30% less context per round than plain `claude -p` on the same machine with the same setup (29k against 44k tokens), because sessions are compacted before they get expensive and scheduled runs start fresh. The app ships no API keys, stores none, has no account or server of its own, and requires macOS 12 or later plus at least one agent CLI on the PATH.

key takeaway

Agent Hive compacts sessions and starts scheduled runs fresh, which it measured at roughly 29k versus 44k tokens per round against plain `claude -p` across a three-round task.

read12 min views7 publishedNov 19, 2026
Show HN: Agent Hive – cute Grokbot like agentic teams with queen and many bees
Image: Michielbdejong (auto-discovered)

One Queen. Many bees. Your coding agents, working as a hive.

A free, open-source Mac app that turns Claude Code, Codex, Gemini CLI and Cursor Agent into a team you can watch, schedule and steer.

Install · Features · How it compares · FAQ

Agent Hive is a macOS app that runs several coding-agent CLIs at once and lets them work as a team. Each agent is a bee: Claude Code, Codex, Gemini CLI, Cursor Agent, or any command you like, working in its own folder. You can talk to each bee, put it on a schedule, chain bees into a relay where one writes and another reviews, or pull them into a group and let Queen hand out the work.

It uses the CLIs and logins you already have, including a Claude or ChatGPT subscription. It ships no API keys, stores none, has no account and no server of its own.

  • Any agent, mixed in one team. Claude Code writes, Codex reviews, Gemini tests. Any CLI that takes a prompt can be a bee.
  • Agents that work while you are away. Schedules (once, daily, weekdays, weekends, weekly, monthly, every N minutes) and event triggers (new commits, GitHub pull requests, comments and CI failures, another bee finishing), catch-up for runs missed while the Mac slept, and a daily budget that stops automatic runs when it is used up.
  • A lead agent instead of ten terminals. Tell Queen what you want; she picks the bees, dispatches the work, waits for the results and sums them up.
  • Everything they made, in one place. A Files page lists every PDF, deck, chart and link the bees produced, by bee and project. Search finds bees, skills, memory and anything said in a conversation.
  • Review built into the flow. Relay teams send a reviewer's findings back to the writer until it approves. Every bee has a diff view with commit, push and pull request.
  • Spends fewer tokens than the CLI on its own. Sessions are compacted before they get expensive, scheduled runs start fresh, unused tools and MCP servers are left out. In a measured three-round task a bee carried about 30% less context per round than plainclaude -p on the same machine with the same setup (29k against 44k tokens).
  • It remembers. Overnight, two helper bees turn the day's conversations into long-term memory and reusable skills. New sessions start with both.
  • Nothing to trust but your own machine. MIT licensed, no build step, no telemetry; the only request the app makes on its own is a check for new releases on GitHub. The app is signed and notarized by Apple and updates itself if you let it.
curl -fsSL https://raw.githubusercontent.com/ericwang915/agent-hive/main/install.sh | bash

This downloads the latest release for your Mac (Apple silicon or Intel), puts Agent Hive.app in /Applications and opens it. You can also download the .dmg from the releases page. The app is signed and notarized by Apple.

To run from source instead:

git clone https://github.com/ericwang915/agent-hive.git
cd agent-hive
npm install
npm start
  • macOS 12 or later
  • At least one agent CLI on your PATH :claude , codex ,gemini orcursor-agent . Queen, the daily report and the night bees needclaude .
  • git for diffs, commits, branches and pull requests.gh is optional and used to open pull requests.

Pull bees into a group and tell Queen what you want. She picks the right bees, dispatches the work, waits for the results and sums them up. She only wakes the bees she needs, and she asks before hatching new ones.

A group works without Queen too. @mention a bee and it starts right away. Leave the name out and a small, cheap model picks the bee the message is for, so the others stay asleep; a bee with nothing to add stays quiet. Stickers work both ways. A bee can hand part of the job to another by @mentioning it, for at most three hops.

Up to four bees share a folder and pass work down the line. A reviewer can send its findings back to the writer until it approves, for at most three rounds. Bees on the same step run in parallel, each in its own git worktree, and a final bee merges their results. The clip at the top is one such team.

A relay team is also a squad with a name. Queen can hand it a whole job with one call and hears back once, when the chain is finished or stuck. You can start it yourself from any group: @Shop-squad add an export button. The group shows the chain and each bee's state as it runs.

Each bee has its own chat window with the full conversation. Replies stream in as they are written, edits show as inline diffs, sub-agents are nested, and every round shows its cost. Type @ to point at a file, / for commands, Shift-Tab to switch between Ask, Auto-edit and Plan. The bee's folder sits in a sidebar on the left, and file paths in the conversation are clickable: they open at the line mentioned. The Files tab is a small editor: create, rename and delete files and folders, edit and save, find in a file, and search the whole folder by name or text. The Changes tab shows the diff. Commit, discard, push and open a pull request from there, or keep a bee on its own branch and merge when you are happy.

The Hive page opens as a honeycomb; a switch takes you to the classic cards. Each squad is a cluster shaped by its relay: a chain sits in a row, a review loop is marked on the shared edge, and bees that work in parallel fan out and meet again at the merge. Click a cell and its full card, with every button, shows beside the comb.

Pick a folder, an engine and a model. Give it a prompt and a schedule, or leave both empty and just talk to it.

  • Schedules. Once, daily, weekly, monthly, or every N minutes. Runs missed while the Mac slept are caught up the same day.
  • Event triggers. Instead of a time, a bee can wait for something to happen: new commits on a branch (in its folder or on the remote), a GitHub event (new pull request, new comment, CI failure, through thegh CLI), or another bee finishing or failing. What happened is attached to its prompt. Its own commits and comments do not wake it, and a cooldown keeps bursts to one run.
  • Sleep-safe. Running bees stop when the lid closes and pick up where they left off when it opens, or when the app restarts.
  • Permissions. Approve each action from the app (Claude Code), auto-accept edits, allow everything, or plan first and change nothing. Switch at any time from the chat.
  • Context. A meter shows how full a Claude Code bee's session is./compact summarises it on the spot, and/new starts over.
  • Token savers. A session that is half full (100k tokens at most), or large and idle for an hour, is compacted before its next round. Scheduled runs start a new session. Each bee's settings list your MCP servers, so you tick only the ones it needs. Reports and the night bees use a smaller model. All adjustable.
  • Spend. Cost and tokens per round, and a daily budget that holds back automatic runs once it is used up.
  • Memory and skills. Overnight,Dreamer tidies long-term memory andGardener turns the day's conversations into reusable skills. New sessions start with both.
  • Dashboard. A 24-hour activity timeline, spend, and Queen's daily report.
  • Upgrades. When a newer release is out, an Upgrade button appears in the sidebar. It downloads the release, checks that it is signed by the same developer, swaps the app and restarts. Settings (the gear at the bottom of the sidebar) can install new versions automatically once no bee is working, and notify you when one is out.
  • Ranks. Every finished round counts. A bee climbs from Bronze through Silver, Gold, Platinum and Diamond to Master, and its look changes with each rank.
  • Files page. Everything the bees produced in one list, newest first: files they wrote or named in a reply (PDFs, decks, charts, CSVs) and links they gave (artifacts, Google Slides, pull requests). Each row shows the bee and its project; filter by kind or bee, open the file, or jump to it in the bee's window.
  • Chats in the sidebar. Every bee and squad in one list: its name and what it is for, or what it is doing right now. A squad folds into one line and opens when something is going on.
  • Search everything. The search box and ⌘K find bees, skills, memory, and what was said in any bee's conversation or group; a hit opens the chat at that message.
  • Right-click anything. Rename, settings, stop and delete for bees and groups.

Several good tools run coding agents in parallel. They differ in what they are built around. This is how Agent Hive sees the field in November 2026; check each project for its current features.

Tool Built around Good fit when
Agent Hive A standing team: scheduled agents, a lead agent (Queen), relay teams with review loops, memory and skills. Open source, macOS. You want agents that keep working on a schedule, hand work to each other, and that you can supervise from one window.
Conductor Parallel workspaces, each agent in its own git worktree. A proprietary macOS app. You want to start many independent tasks on one repository and review each branch.
Claude Squad A terminal UI on tmux, each agent in its own git worktree. Open source. You live in the terminal and want sessions that survive a closed window.
Vibe Kanban A kanban board of tasks that agents pick up in workspaces. Open source. You think in tickets and want a board as the main view.
Claude Code agent teams Several Claude Code instances that message each other. Claude only. You use only Claude Code and want it to split one task among teammates.

What Agent Hive adds on top of running agents side by side:

  • Scheduling with catch-up, sleep-safe runs and a daily budget , so unattended work is predictable.
  • Routing by a small model. In a group, a message without an@mention goes only to the bee it concerns; the others stay asleep and cost nothing.
  • Review loops across engines : a reviewer on one model can send work back to a writer on another, for at most three rounds.
  • Token controls you can see : a context meter, automatic compaction, cost per round, and a checklist of MCP servers per bee.
  • Memory and skills that are distilled from your own conversations and shared by every bee.

Agent Hive also uses git worktrees, for bees that run in parallel on the same step of a relay.

Bees run real commands on your machine, with the permission level you choose. "Allow all" skips every confirmation, so only use it in folders you trust.

The app listens on 127.0.0.1 on a random port, protected by a per-launch token. Claude Code uses it to ask for permission decisions, and Queen uses it to call her tools. Nothing is exposed to the network.

State lives in ~/Library/Application Support/Agent Hive/. Workspaces, skills and memory live under ~/AgentHive/ by default.

Yes. It is open source under the MIT license. You pay only for the agent CLIs you already use, through their own subscriptions or API billing.

No. Agent Hive starts the CLIs installed on your Mac (claude, codex, gemini, cursor-agent) with the logins they already have. It never sees or stores a key.

Yes. If the CLI works in your terminal, it works as a bee, with the same account and limits.

Claude Code, Codex CLI, Gemini CLI and Cursor Agent out of the box, plus any command line that accepts a prompt (a custom template with {prompt}). Queen, the daily report and the night bees need Claude Code.

Subagents and agent teams are features of Claude Code and use Claude only. Agent Hive runs separate, long-lived agents from different vendors, each with its own folder, session, schedule and chat window, and keeps running them after you close the conversation.

Yes. Each bee can run once, daily, weekly, monthly or every N minutes. Runs missed while the Mac slept are caught up the same day, and a daily budget can stop automatic runs.

Agent Hive has no server and sends your code nowhere. The agent CLIs talk to their own providers exactly as they do in your terminal. The only request the app makes on its own is a check for new releases on GitHub.

Not yet. It is built and tested for macOS 12 or later, on Apple silicon and Intel.

An Upgrade button appears in the sidebar when a new release is out. Settings can also install new versions automatically once no bee is working.

No build step and no framework: plain HTML, CSS and JS in the renderer, Electron in the main process, two small dependencies for Markdown.

File Role
main.js Main process: state, process management, scheduling, relay execution, git, approvals, groups and Queen
core.js Engines and command lines, schedule keys, output parsers, relay planning, git and worktree helpers
team.js Relay-team graph helpers, shared by main and renderer
queen.js Queen's tools, dispatch rules and result parsing
garden.js Skills and memory files, Dreamer and Gardener prompts
events.js Event triggers: checking the settings, telling what is new on GitHub, matching a finished bee
outputs.js Files page: finding the files and links a bee produced in its log
update.js Upgrade: finding, down, verifying and installing a newer release
files.js File browser: listing, reading and locating paths inside a bee's folder
approve-mcp.js ,hive-mcp.js Small MCP stdio servers that call back into the app
index.html ,app.js Main window
chat.html ,chat.js Per-bee chat window
test.js Unit tests for everything that does not need Electron
npm test             # unit tests
npm run dist         # build an ad-hoc signed .zip and .dmg into dist/
npm run dist:signed  # the same, signed and notarized (needs CSC_NAME and NOTARYTOOL_PROFILE)

Issues and pull requests are welcome. See CONTRIBUTING.md for how the code is laid out and how to add an engine.

── more in #ai-agents 4 stories · sorted by recency
── more on @agent hive 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/show-hn-agent-hive-c…] indexed:0 read:12min 2026-11-19 · —