0xorial

Hive Containers — Git skill for Claude Code

Git community

Hierarchical Claude Code containers with one curated egress bridge: a root control plane, a sealed node tree, per-node live internet/GitHub switches, and desktop-app SSH access.

How to install Hive Containers

This entry records only its repository, not the path inside it, so there is no exact command to give. Open 0xorial/hive-containers and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Hive Containers does

Hierarchical Claude Code containers with one curated egress bridge: a root control plane, a sealed node tree, per-node live internet/GitHub switches, and desktop-app SSH access.

Alternatives in Git

  • GitLab — Source Control GitLab integration via MCP 14k ★
  • GitHub Review Failures — Use when CI checks are failing on a PR — fetches failure logs, diagnoses root causes, implements fixes, and pu 1.5k ★
  • Codexia — Agent Workstation for Codex CLI + Claude Code — with task scheduler, git worktree & remote control, skills man 638 ★

README

hive

Hierarchical Claude Code containers with one curated bridge to your Mac.

 MacBook ────────────────────────────────────────────────────────────────
 │  hive CLI · config/ (the two curated files)
 │
 │   docker         ┌────────────────────────────────────────────┐
 │   socket ──────► │ root        control plane (docker CLI +    │
 │                  │             hive CLI + Claude Code)        │
 │                  │   ├─ node a      ├─ node b                 │
 │                  │   │   └─ node a2 │                         │  hive-net
 │                  │   (any depth, tracked via labels)          │  (internal —
 │                  └───────────────────┬────────────────────────┘   no way out)
 │                                      │ only crossing point
 │                            ┌─────────┴─────────┐
 │   host.docker.internal ◄── │ bridge            │ ──► internet
 │   (only what's listed in   │  squid 3128       │     (allowlisted domains for
 │    config/forwards.conf)   │  socat forwards   │      sealed nodes; everything
 │                            └───────────────────┘      for nodes you `net on`)

Three guarantees, all enforced by Docker networking rather than convention:

  1. Nodes are sealed. Every node sits on hive-net, an internal: true network. No internet, no Mac, not even with root inside the container.
  2. The bridge is the only door, and you curate both sides of it. Outbound HTTP(S) goes through a domain allowlist (config/egress-allowlist.txt); access to your Mac exists only as the explicit TCP forwards in (config/forwards.conf).
  3. Only root holds the Docker socket. It is the one container that can spawn or destroy others — a Claude instance in root can orchestrate the whole tree, while Claude instances in nodes can't touch the hierarchy.

Quickstart

alias hive="$PWD/bin/hive"     # or add bin/ to PATH

hive up