Skip to content

Getting started

Linux x86_64 and macOS Apple Silicon have prebuilt binaries; Intel macs and Linux arm64 build from source with --dev. The installer downloads the latest GitHub release:

Terminal window
bash <(curl -fsSL https://hivemind.griiken.com/install.sh)

It installs the hive CLI and the hivemind app into ~/.hivemind-app/, symlinks both into ~/.local/bin/, and warns if no agent CLI is on PATH. Re-run to upgrade; pin a version with HIVEMIND_VERSION=v1.0.0.

hivemind runs agent CLIs you install yourself. Spawnable today: claude, codex, opencode, droid, pi, kiro. After installing one, check detection from an initialised workspace with hive agent detect. Capability differences are in Agents.

Terminal window
cd ~/my-project
hive init --prefix MYP

Writes .hivemind/ (the markdown issue tracker) plus the agentic stack: hive skills in .claude/skills/ and an agentic section in CLAUDE.md. Variants:

Terminal window
hive init --prefix MYP --no-agentic # tracker only
hive init # refresh the agentic stack in an existing workspace
hive add skill # refresh the skills only
Terminal window
hive new "Fix token expiry comparison" --ac "boundary test || manual check passes"
# → .hivemind/issues/MYP-1.md

Each issue is one markdown file with YAML frontmatter; --ac seeds the acceptance checklist. Full command list: CLI.

Terminal window
hivemind .
  • Number keys 17 spawn: terminal, agent, explorer, diff, issues, frame, browser. 2 spawns the default agent in the selected frame.
  • ▶ Work on an issue card spawns an agent pre-loaded with that issue and the hive skills.
  • ⌘L toggles the Layers rail (tiles grouped by frame, live agent status).
  • ⌘E cycles workspace views; double-click a tile name to rename it.

The installed skill drives the agent through the execution contract: load the issue (hive show MYP-1 --json), set in_progress and claim it, tick criteria with hive ctl mark-acceptance, and end every session with a final hive ctl set-state. Each state change is a markdown write; the board tile updates from filesystem events. Open a diff tile (4) beside the agent to watch edits land, review per-file, and send line comments back to the agent.