vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: nixpkgs-override guidance in README, fix stale CLAUDE.md repo map

Browse source 
README: add a "Overriding nixpkgs" section explaining hyperhive.inputs.
nixpkgs.follows and showing it in the quick-start flake example, since
hyperhive pins its own nixpkgs and consumers embedding it as a flake
input generally want to follow their host's nixpkgs instead.

CLAUDE.md: the repo map still described a hive-ag3nt/ directory
grouping hive-agent, hive-agent-mcp, and hive-agent-wake — that
directory doesn't exist; they're three separate top-level crates.
Also added the three wire-type crates split out of hive-sh4re
(hive-host-sock, hive-priv-sock) and hive-metric, none of which were
listed.
This commit is contained in:
iris 2026-07-15 23:32:42 +02:00 • committed by mara
commit 57765946db
2 changed files with 48 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

22
README.md
View file

@ -62,6 +62,9 @@ Minimal `flake.nix` for a host that runs hive-c0re:
inputs = {
nixpkgs.url = "github:NixOS/nixpkgs/nixos-26.05";
hyperhive.url = "git+https://forge.darkest.space/hyperhive/hyperhive";
# Pin hyperhive to your own nixpkgs instead of the one it ships with
# (see "Overriding nixpkgs" below) — recommended for most hosts:
hyperhive.inputs.nixpkgs.follows = "nixpkgs";
};
outputs = { nixpkgs, hyperhive, ... }: {
@ -87,6 +90,25 @@ manager container, and auto-rebuilds any container whose hyperhive
rev goes stale. `claude-code` is unfree — hyperhive scopes the
whitelist to itself, nothing for the operator to set.
### Overriding nixpkgs
hyperhive's own `flake.nix` pins `nixpkgs.url = "github:NixOS/nixpkgs/nixos-26.05"`
so the repo builds standalone (`nix flake check`, CI, `nix develop`) without
depending on a consumer's host flake. When you import hyperhive as a flake
input into your own host config, that pin becomes a second nixpkgs
evaluation living alongside your host's — extra closure to build/cache, and
a second place package versions can drift from what the rest of your system
runs.
Add `hyperhive.inputs.nixpkgs.follows = "nixpkgs"` to your input declaration
(as in the quick-start above) to make hyperhive build against your host's
`nixpkgs` input instead of its own pinned one. This is the standard flake
`follows` pattern — nothing hyperhive-specific — and works as long as your
`nixpkgs` is reasonably close to the `nixos-26.05` release hyperhive is
developed against; a much older or newer channel may hit `nixpkgs`-side
breakage hyperhive's CI doesn't catch. If you hit that, drop the `follows`
line and let hyperhive use its own pin again.
For the full list of host and agent NixOS options see the
**[options reference](https://hyperhive.darkest.space/options/)**.