hyperhive/hive-agent-wake
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-07-23 16:41:05 +02:00
..
src refactor(#2569): rename hive-agent-sock to hive-core-agent-sock 2026-07-20 21:58:28 +02:00
Cargo.toml docs(#2627): crate READMEs for the harness column (hive-agent, hive-agent-mcp, hive-agent-wake, hive-bash-mcp) 2026-07-23 16:41:05 +02:00
README.md docs(#2627): crate READMEs for the harness column (hive-agent, hive-agent-mcp, hive-agent-wake, hive-bash-mcp) 2026-07-23 16:41:05 +02:00

hive-agent-wake

A tiny CLI that injects a wake-up event into an agent's own harness inbox, so the next turn fires with a given --from/--body. That's the whole crate.

When to use it

Reach for this when you're wiring up an extraMcpServers daemon (scraper, webhook listener, custom integration) that needs to nudge claude on some external event — a new item arrived, a long job finished, whatever. The built-in daemons (matrix, bash) don't use this: they talk to the per-agent MCP socket directly instead. This CLI exists so a helper author only needs one small, dependency-light crate to get the same effect without linking hive-agent-mcp or the full hive-agent harness lib.

Shape

One binary, src/main.rs: parses --socket (defaults to /run/hive/mcp.sock, the per-agent MCP socket bind-mounted from the host), --from, and --body (pass - to read the body from stdin), dials the socket with hive-core-agent-sock's Request/Response wire types, sends a Wake request, and exits. It carries its own copy of the retrying request client rather than depending on hive-agent-mcp's.