2cdd7f2ff1
The harness has had its queue coordinates since the credential reached the container, but nothing used them. This offers each terminal row upward on `$SWARM.term.<hive>.<agent>`, so a swarm-level terminal can render an agent without reaching into the hive that hosts it. It publishes the same `TermMsg` the web UI is handed rather than a second model of the same events, so a new tool or a reclassified event changes both surfaces together. It subscribes to the event bus rather than to the SSE handler: the handler classifies per connected browser, so hanging this off it would mean an agent nobody is watching publishes nothing. That also means its own long-lived `ClassifyCtx`, since a publisher restarting its correlation state would lose the `tool_use` → name mapping a `tool_result` needs to render. The hive in the subject is derived from the queue client id, not from the harness's hive display name. Those come from different sources with no rule tying them together, and the responder builds its grant from the client id — so deriving it from the display name yields a publish the broker refuses, reaching an operator as a terminal that is merely empty. The prefix and suffix that bracket the hive are the responder's flags, which the agent is not told; it restates their defaults, and the symptom of a deployment retuning one without changing this is every publish refused rather than a wrong subject accepted. Oversize rows degrade in the publisher. Exceeding `max_payload` is not a truncation: the server refuses the message and closes the connection, so an oversize publish costs the row, the connection, and the rows racing behind it through the reconnect. The body is the only unbounded field — summaries are already trimmed at classification — so it is the field spent, and the row keeps its icon, level, summary and coalesce key. A row that does not fit even then is logged and dropped rather than sent. The limit is read off the connection, so `8388608` stays spelled once in the queue's own module; size is measured by serializing, because JSON escaping separates character count from wire length by an unbounded factor on exactly the rows already near the limit. Best-effort throughout: no queue, an unparseable client id and a failed connect each disable the publisher with one log line, and a failed publish loses its row and nothing else. The turn loop and the web UI never block on the queue. Refs #3805
54 lines
1.6 KiB
TOML
54 lines
1.6 KiB
TOML
[package]
|
|
name = "hive-agent"
|
|
edition.workspace = true
|
|
version.workspace = true
|
|
readme = "README.md"
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
# Named directly only for the client type the terminal publisher holds; the
|
|
# connect and the credential handling live in `swarm-queue-client` below.
|
|
async-nats.workspace = true
|
|
axum.workspace = true
|
|
chrono.workspace = true
|
|
reqwest.workspace = true
|
|
hyper.workspace = true
|
|
hyper-util.workspace = true
|
|
http-body-util.workspace = true
|
|
futures-util = "0.3"
|
|
clap.workspace = true
|
|
hive-claude.workspace = true
|
|
hive-agent-sock.workspace = true
|
|
hive-core-agent-sock.workspace = true
|
|
hive-sh4re.workspace = true
|
|
hive-sock-client.workspace = true
|
|
libc.workspace = true
|
|
opentelemetry.workspace = true
|
|
opentelemetry_sdk.workspace = true
|
|
opentelemetry-otlp.workspace = true
|
|
rmcp.workspace = true
|
|
rusqlite.workspace = true
|
|
schemars.workspace = true
|
|
serde.workspace = true
|
|
serde_json.workspace = true
|
|
# Bare: `kv`/`notices` name buckets and streams this harness opens neither end
|
|
# of. The terminal publisher is a plain core-subject publish, so it needs the
|
|
# connect and the payload limit and nothing from JetStream.
|
|
swarm-queue-client.workspace = true
|
|
tokio.workspace = true
|
|
tokio-stream.workspace = true
|
|
tower-http.workspace = true
|
|
tracing.workspace = true
|
|
tracing-subscriber.workspace = true
|
|
|
|
[dev-dependencies]
|
|
tempfile = "3"
|
|
|
|
# Single harness serve-loop binary: `hive-agent` (from `src/main.rs`).
|
|
# The sibling MCP server is its own bin crate now (`hive-agent-mcp`).
|
|
# Privilege boundary is enforced server-side at the socket (tool
|
|
# groups / manager surface).
|
|
# See `docs/turn-loop/README.md::Harness binary shape`.
|