Send message
send_messageSend a private one-to-one message to a named agent, optionally requiring a reply or auto-waking the recipient. Use for direct requests or no-response FYI updates.
Instructions
Private 1→1 message to another agent by name. By default auto-poke=true with quiet-guard (auto_poke:false opts out), and need_reply=true. Set need_reply:false for FYI/no-response-needed messages; recipients see need_reply in get_inbox. to_agent_name is the target's name within its team; bare names resolve on the caller's device, and name:device targets a specific device. For UUID-based sends use send_message_by_id. If the user refers to a recipient in the shorthand name(team) (e.g. skills-creator(default)), split it into to_agent_name=skills-creator and to_team=default. The daemon does NOT parse name(team), so the literal string fails to resolve (unknown_recipient). This is distinct from the name:device suffix, which the daemon DOES parse. REPLY RULE: when replying to a message returned by get_inbox, treat its from_device as authoritative — if it differs from your own device, you MUST send to from_name + ":" + from_device (bare from_name would resolve on YOUR device and miss the actual sender). Same-device replies can use the bare name. The safe fallback for unknown device is send_message_by_id({to_agent_id: from_agent_id, ...}). For multi-recipient use broadcast (same-team) or broadcast_to_role (same-team, by role). 除非用户明确指定 to_team, 不要跨 team 沟通 (explicitly set to_team only when user asks). Reports poked, poke_skip_reasons (no_pane, guard_failed, tmux_unavailable, self); on guard_failed daemon retries at 30s/180s/600s (retry_scheduled, retry_delays_s); stops early on poked. Auto-poke injects only a SHORT wake-up hint (新邮件 from , 请调 get_inbox 查看), NOT the body — read bodies via get_inbox. Delivery is NOT filtered by online/idle; direct and fan-out deliveries write mailbox rows for offline targets. The list_agents online flag reflects process liveness. DO NOT pre-verify the recipient via list_agents before calling send_message — this rule applies to BOTH same-team and cross-team sends (list_agents is caller-team scoped and CANNOT see cross-team agents, so a cross-team pre-check always falsely reports "missing"; for same-team sends the pre-check is pure waste). On miss send_message returns unknown_recipient cleanly with no side effects, so the correct pattern is "try send, then handle unknown_recipient" — never "list_agents first, then send".
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": {
"to_agent_name": "<to_agent_name>",
"body": "<body>"
},
"name": "send_message"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | ||
| subject | No | ||
| to_team | No | ||
| auto_poke | No | ||
| need_reply | No | ||
| to_agent_name | Yes |