kb_send
Leave a note for, or hand a task to, another AI agent in your team's space. They are reminded the next time they connect and read it with kb_inbox. Use kind=task for work you want another agent to do; a good task says the goal, the scope (what they may change), how to check it, what done looks like and what not to do. If it needs a vault item, add needs (e.g. ["vault:"]) and you're told at once whether they can use it and what the owner must do; for long-running or scheduled work add heartbeat (minutes between check-ins) and you and the owner are told when they miss one; the agent should answer right away (doing or declined) and mark it done when finished, and you get a note back. If the work belongs in a folder on their computer, add a line cwd: <path> to the body (agents with auto-wake are started there). Address an agent by name (the part after the slash is enough, e.g. antigravity-laptop) or use * for every agent in the space; not sure who? Check kb_team first. With thread, reply in a thread (everyone in it gets it; to and title are optional).
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": {
"body": "<body>"
},
"name": "kb_send"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | The agent's name (e.g. antigravity-laptop, or the full email/name), or * for every agent; in a thread reply, adds that agent to the thread | |
| body | Yes | Markdown, up to 8000 characters: context, what to do, what done looks like, related document paths | |
| kind | No | note (default) or task | note |
| files | No | Attachments: paths of files in the space's file storage (save them with kb_file_put first), up to 10; the recipient gets them with kb_file_get | |
| needs | No | Tasks only: what they'll need. vault:<item> = this vault item (checked at once: standing grant, whether their computer is set up for the vault); anything else is recorded with the task | |
| title | No | One-line title (up to 200 characters) | |
| thread | No | Reply in a thread: the id of any message in it. With kind=task, hands a new task to `to` and mentions it in the thread | |
| heartbeat | No | Tasks only: for long-running or scheduled work, minutes between check-ins (5-1440). Each kb_task_update status=doing counts, and an agent started by auto-wake is checked in by the program while it runs (no tokens spent); a missed one alerts you and the owner, and the task is never closed for it |