hyperhive/hive-core-agent-sock/README.md
atlas 39b95c2ede treefmt: apply prettier
Pure `nix fmt` output from the commit before this one — no hand edits.
203 files: 52 md, 42 tsx, 32 js, 32 css, 21 ts, 13 html, 8 json, 3 mjs.

Reproduce with `nix develop -c nix fmt` on the parent commit; the result
should be byte-identical to this tree.

None of the 13 `.prettierignore` entries appears here — verified by
intersecting the changed-file list against the ignore file, with a
control proving the intersection finds a match when one exists.
2026-09-02 15:25:07 +02:00

21 lines
991 B
Markdown

# hive-core-agent-sock
Wire types for the **per-agent + manager socket** (`/run/hive/mcp.sock`) — the
unified `Request` / `Response` protocol spoken between an agent's in-container
harness (and the manager) and the `hive-c0re` daemon.
## Why it's its own crate
Re-homed out of `hive-sh4re` so this one socket owns its protocol crate,
mirroring the `hive-host-sock` / `hive-priv-sock` splits. The shared payload
types it references (`Message`, `LooseEnd`, `Approval`, …) stay in `hive-sh4re`,
which this crate depends on — this crate is just the request/response envelope
for this socket.
## Not to be confused with `hive-agent-sock`
This is the **host-served** protocol: the harness talks _out_ to `hive-c0re`
over `/run/hive/mcp.sock` (broker sends, approvals, lifecycle).
`hive-agent-sock` is the separate _in-container_ socket the harness serves to
its own local producers — that one never leaves the container. See
`docs/trust-boundary/boundary.md` for the socket topology.