hub_queue_send
Append a message to a role's queue for cross-agent handoffs, delivering it to the next consumer that waits on that role, locally or on a mesh-synced peer node.
Instructions
Append a message to a role's queue (queues/..queue.md) for cross-agent/cross-node handoffs. Delivered to whoever calls hub_queue_wait (or hub queue wait) for that role, here or on a mesh-synced peer node.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"role": "<role>",
"text": "<text>",
"from": "<from>"
},
"name": "hub_queue_send"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| from | Yes | who is sending — the function you are performing, e.g. "dev-hubd" or "orchestrator". NOT which model you are, and NOT the target role. Required like every other write: the delivered block says "from <sender>" forever. | |
| role | Yes | queue/role to deliver to, e.g. "dev" or "owner" | |
| task | No | the task id this message is ABOUT, if any. Stamped into the delivered block and handed back to the consumer, so a reply (a blocker, a HOLD, a result) can be reported onto the task instead of being lost with the message. An id matching no task comes back as taskKnown:false — the ref is still recorded. | |
| text | Yes |