| Filename | Latest commit message | Latest commit date |
|---|---|---|
10285ff764
forge_admin interpolated its whole argument vector into the error context, and two callers pass a live operator password in that vector (user create --password, user change-password). Any failure of those commands wrote the password to hive-c0re's log in cleartext -- and the likeliest trigger is forgejo rejecting a weak password, so the secret got logged precisely because forgejo refused it. Redacting the value after --password would repeat the bug the issue is about: redact_password_line matched one keyword and a differently named secret walked past it. A denylist fails open, silently, and the next secret-bearing flag would leak until someone extended the list. describe_forge_admin keeps the leading verb path and stops at the first flag, so "user create --username iris --password ..." is reported as "forgejo admin user create". The verbs are a closed set this crate chooses itself; argument values never are, so a new flag is excluded by construction. Nothing useful is lost -- the context says which operation failed, and the underlying error already carries forgejo's own message about why. The same pattern in hive-priv is deliberately untouched: that crate runs as root and the redactor's shape is still an open question on the issue. This change holds under either answer. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-c0re
The unprivileged host daemon (runs as hive-core). Owns the sqlite
broker, the approval/question/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, questions, 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.