| Filename | Latest commit message | Latest commit date |
|---|---|---|
23f4f1823b
The page's composer (its input, slash commands and completion), POST /send in hive-agent, the OperatorMsg request of the agent socket and its handler in hive-c0re, and the broker-error helper only the send route used are deleted: writing to an agent is the swarm UI's terminal. cancel turn, new session and log out stay in the state badge's menu; POST /api/compact stays, with nothing on the page calling it. The request-line limit keeps its size, and its comment says it is a generous bound now. The docs describe the actions in place of the footer and the prompt. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
hive-core-agent-sock
Wire types for the per-agent socket (/run/hive/mcp.sock) — the
unified Request / Response protocol spoken between an agent's in-container
harness 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, …) 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, 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.