vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

recv: drop wait_seconds from the MCP tool, always an immediate peek

Browse source
This commit is contained in:
damocles 2026-08-02 03:42:55 +02:00 • committed by mara
commit ceff662d25
6 changed files with 59 additions and 117 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/conventions.md
View file

@ -121,10 +121,13 @@ in `hive-c0re::dashboard_events::DashboardEvent`.
agent. Always returns a list (`Messages { messages }`) — empty when
nothing's pending, single-pop when `max = None` (default 1, the
single-message behaviour), batched up to `max` when caller asks for
more (server-side cap is 5; values above clamp silently).
`wait_seconds` long-polls for the first message; once one arrives —
or one is already pending — the call drains up to `max` in total
before returning, so a single `Recv` call coalesces a burst.
more (server-side cap is 5; values above clamp silently). The wire
request still carries an optional `wait_seconds` (long-poll the first
message, once one arrives — or one is already pending — the call
drains up to `max` in total): the harness's own turn-driving loop
uses it internally (`hive-agent`'s `recv_next`, 180s). The
agent-facing MCP `recv` tool no longer exposes this parameter at all
(#2814) — it always passes `wait_seconds: None`, an immediate peek.
Per-row bookkeeping inside the broker: