Skip to content

HiveHive

A shared LLM workspace for developers. Bring your own subscription (Claude, OpenAI, OpenRouter, Ollama, aider, pi, or any local agent), collaborate with peers on real work — code, commits, reviews — and keep your data local-first.

Hive workspace overview /// caption Hive's three-pane layout: sidebar navigator (left), conversation canvas (center), right-rail utility pane (right). Workspace bar at the top keeps runtime, presence, and git status visible at a glance. ///

Why Hive

Most "AI for code" tools assume one developer, one model, one machine. Hive flips that:

  • Multiple peers, one workspace. Alice's Claude subscription and Bob's Ollama instance can both participate in the same chat, reviewing each other's proposals.
  • Bring your own agent. Aider, pi, Claude Code, or any CLI agent you trust can act as a workspace participant. Hive doesn't recreate agent logic — it hosts what you bring.
  • Local-first, P2P sync. Workspaces sync directly between peers over a tiny optional relay. No central server holds your content.
  • Real consent flow. Every tool that touches the filesystem or runs a command asks before acting. Approvals persist per-chat or per-workspace as you grant them.

What's in here

  • Getting started

    First launch, configuring runtimes, your first chat.

    Start here

  • Concepts

    Workspaces, agents (built-in vs BYO), tools, consent, identity.

    Read the model

  • Networking & relay

    How peers find each other; setting up your own relay.

    Networking

  • Addon agents

    Wire aider, pi, or any subprocess agent as a workspace participant.

    BYO agents

Built with

Hive is a Tauri v2 desktop app — a Rust backend (crates/hive-core, hive-runtime, hive-relay, plus app/) with a React + TypeScript frontend (web/). One codebase ships macOS, Windows, and Linux. State is an append-only event log in SQLite; replies stream from your chosen runtime (the claude CLI by default — bring your own subscription).

Project status

Pre-release. The multi-runtime workspace + relay-forwarded multiuser sync are in place. Build from source with cargo tauri build (see Building the dist); run the reference relay with cargo run -p hive-relay or one of the deploy recipes in deploy/relay/. Release builds are unsigned for now — run from source or click through your OS's first-launch prompt.

The reference relay is MIT-licensed and lives at crates/hive-relay/ (a small axum service). Direct peer-to-peer (STUN/hole-punch) and the collaborative-text CRDT are tracked follow-ups; relay forwarding is the multiuser path that works today.