| Filename | Latest commit message | Latest commit date |
|---|---|---|
bfae9aa51a
Per mara on the PR: the issue is about a *new* agent, there is no approval because the operator clicked create at swarm level, and most of what a hive does on create is already done by the controller. `spawn_nodes` splits out of `spawn` the way `rebuild_nodes` already splits out of `rebuild`: two callers want the same four nodes and disagree only about what closes them. `first_deploy` is that subgraph with no approval tail, and the absence is the point — that tail exists because an operator used to approve the spawn at the hive, and asking again after they clicked create at swarm level asks the same person the same question twice. The handler's predicate is "does a container exist", not "is one running". `agents_for_meta_listing` is `nixos-container list`, so a stopped agent still counts. `Coordinator::list_agents` looks like the right check and is the registered-MCP-socket set — a stopped agent is absent from it, and this would then try to create over an existing container. Enumeration failure drops the request rather than guessing: without the list this cannot tell first deploy from rebuild, and guessing "new" is the destructive direction. Still missing, and the reason this is not the whole change: the hive seeds its own config repo with `git init` instead of cloning the one the controller already created. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-c0re
The unprivileged host daemon (runs as hive-core). Owns the sqlite
broker, the approval/reminder/schedule queues, the generic job-DAG
queue, container lifecycle, gateway/forge/matrix provisioning,
per-container stats, and the axum operator dashboard. Largest crate in
the workspace — bin-only, no separate lib.
When to use it
Host-level, cross-container orchestration: spawning/rebuilding/
destroying agent containers, the approval flow, dashboard-visible
state, provisioning per-agent forge/matrix/gateway accounts. Agent-side
behavior (turn loop, MCP tools) lives in hive-agent/hive-agent-mcp
instead — this daemon only talks to agents over the socket wire types
in hive-sh4re.
Shape
Cohesive clusters live in directory submodules, each re-exported at
the crate root (crate::broker::… keeps resolving regardless of which
subdirectory a module actually lives in). One line each — read the
module's own //! doc-comment for real detail, don't expect this file
to track it:
dashboard/— the operator dashboard (containers, approvals, schedules, logs, topology).job_queue/— the job-DAG queue + desired-state reconciliation (docs/coordinator.md).lifecycle/—nixos-containerlifecycle + per-agent config flake generation.stores/— sqlite-backed stores (broker, queues, audit, power).workers/— background sweeps (crash watch, scheduled prompts, auto-update, knowledge sync).agent_config/— per-agent registries (tool groups, capabilities, resource limits, topology).stats/— dashboard metrics aggregation + OTEL export.socket_server/— the unix-socket request server shared by per-agent + manager sockets.forge/— optional Forgejo wiring (docs/forge.md).coordinator.rs— top-level wiring forserve.meta.rs,migrate.rs— the meta flake + schema/state migrations.matrix.rs,gateway_nginx.rs,webhook_secret.rs,priv_client.rs— matrix provisioning, gateway vhosts, webhook secrets, and thehive-privclient respectively.
See the top-level CLAUDE.md/docs/ index for the full reading-path
map.