| Filename | Latest commit message | Latest commit date |
|---|---|---|
efbfeb3954
mara on #3923: "past tense is itself a smell for docs, we dont need any 'used to be somewhere else'" and "any gate we add should not have false positives". Those are one instruction: the entire false-positive set of a repo-path checker was prose naming files that are deliberately gone, so removing the prose is what lets the gate be strict instead of carrying a skip-list nobody maintains. Three sites, and only two of them are past tense: `agent-hierarchy.md` named two removed modules to explain that a code path is gone. A reader cannot act on where it used to live; they can act on where cancellation happens now, which is the half the sentence buried. `term_msg.rs` carried a "Design history" paragraph whose live content was three rules -- classification is server-side, `level` carries styling, four named fields are deliberately absent -- wrapped in narration about a redesign and a pointer to a deleted frontend file. Restated as the rules. `gotchas.md` is NOT past tense: it correctly names a file in the website repo. Qualifying it as `hyperhive/website:nix/options.nix` did not work -- the extractor still matches `nix/options.nix` as a substring, so the fix has to be prose that contains no repo-relative path at all. Naming the file alone does that and reads better. Verified against this tree rather than the default checkout: the audit script takes a directory argument and defaults elsewhere, so its first (unchanged) DEAD:3 was a true statement about a different branch. On this one: DEAD 3 -> 0, 141 distinct paths enumerated, and an injected dead path is still caught. Refs #3923 |
||
| .. | ||
| prompts | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-agent
The in-container harness serve-loop binary — one instance per agent.
Long-polls the broker inbox and drives one claude --print turn per
inbox message, over the hive-claude driver. There is one role here
(agent); the Surface trait + AgentSurface zero-sized type tag keep
the turn loop generic and testable for future roles without a
parallel copy of the loop.
When to use it
You don't call into this crate from elsewhere — it's the top-level
binary systemd starts per agent container. Look here when you need to
understand or change: what happens between "a message lands in the
inbox" and "claude produces a reply", how login/auth is bootstrapped,
how the per-agent web UI is served, or how turn/event stats get
recorded. Architecture detail lives in
docs/turn-loop/; this README is just the
map of the module tree.
Shape
turn.rs— the turn-loop policy layer: renders the system prompt + MCP config, invokeshive-claude, classifies the outcome, and feeds the event/turn-stats sinks.client.rs— broker client (inbox poll, ack, send) speaking thehive-sh4rewire protocol.login.rs/login_session.rs— first-run and session-resume auth flow for theclaudeCLI.mcp_config.rs— renders the per-turn--mcp-config/--allowedToolsblob from tool groups + capabilities.todos.rs/reminders.rs/todo_server.rs— the harness-local loose-ends v2 stores (sqlite-backed) and the in-agent socket server extra MCP daemons +hive-agent-mcpdial into for todo/reminder ops.vacuum.rs— periodic sqlite vacuum sweep for the harness-local stores.events.rs/turn_stats.rs/stats.rs— append-only event sink and per-turn telemetry recording (context usage, cost, tool favorites) underharness/.forge_notify.rs— subscribes to forge notifications and wakes the harness on new activity.prompt.rs— system-prompt renderer (persona + tool docs + environment facts).web_ui/— the per-agent dashboard (terminal pane, status, schedules) served over the built-inhive-agentweb port.paths.rs— canonical path resolution for state/harness dirs and the harness-local sqlite files.
Sibling: hive-agent-mcp (the MCP server this loop points claude
at every turn). Both are described together in
docs/turn-loop/::Harness binary shape.