Agent Message
Send direct messages to yourself or within the current agent's nuclear family
through the local daemon: parent, siblings, and direct children. Roots are siblings
of each other only when they share a parent worker; a root has no parent to
message. The daemon derives your sender identity from the current session; do
not try to include a from field.
Call directly from the kernel:
roster = await agent_observe.list_agents()
child = next(
(
item
for item in roster.get("agents", [])
if item.get("relationship") == "child"
),
None,
)
if child is not None:
receipt = await agent_message.send(
"Please inspect the latest result.",
receiver_role="child",
receiver_name=child.get("sessionName") or child["sessionId"],
)
API
await agent_observe.list_agents() (agent-observe skill) is the roster: it
lists the parent, siblings, and children this skill can reach, active or not,
with the relationship and sessionName that send takes as
receiver_role and receiver_name.
await agent_message.send(message, receiver_role="parent" | "sibling" | "child" | "self", receiver_name=None) — sends one direct
text message to one family member. Sending to an inactive or idle completed
subagent wakes it and starts an ordinary follow-up turn in that same session
and context.
The child remains available only until its parent session closes. The daemon
resolves receiver_role within the current agent family; receiver_name is
required for siblings and children and omitted for the unique parent.
send("all", message) broadcasts only to the family roster and returns
{receipts: [...]} in roster order; successful entries are ordinary receipts
and failed entries contain the target id and a short error. One failed delivery
does not reject successful deliveries. Family messages use follow-up delivery: a busy target
receives them after its current turn finishes, without interrupting active work.
receiver_role="self" queues steering input for this agent itself; omit receiver_name.
It is consumed at the next safe model/tool boundary, without interrupting an active
model call or tool. Strict FIFO applies: it cannot overtake earlier follow-up or
held input, so it may wait until a later turn. An idle eligible session wakes.
There is no delivery_mode argument and no promotion of already queued messages.
Self messages preserve agent provenance and cannot grant human authorization.
All targets use the same ordered inbox. A receipt with deliveryStatus: "queued"
and queueItemId means durable admission (in-memory for ephemeral sessions),
not that the model has processed or answered the message.
receipt = await agent_message.send(
"At the next safe boundary, check the latest result before continuing.",
receiver_role="self",
)
Do not wait inside the current Python call for the model to process your self
message. Return control to reach a safe boundary. Interruption, exhausted turn
budgets, or uncertain crash recovery can hold input for review rather than run it.
Safety
- Do not delete a child immediately after
send: delivered follow-ups may still
be running and queued receipts have not run yet. Wait until observation shows
the child is idle and its context is no longer needed before closing it.
- Reach is limited to parent, siblings, and direct children; relay through an
intermediate child instead of messaging grandchildren or cousins directly.
- Sender identity is daemon-derived and cannot be spoofed from Python.
- Host-delivered messages retain agent provenance and do not count as human
authorization, even though the model transport uses the user role.
- Avoid unbounded repeated messages; this path does not implement a general
per-sender rate limiter or exactly-once retries.
1---2name: agent-message3description: Send yourself safe-boundary steering input, or send follow-ups to your parent, siblings, or direct children. All messages preserve strict FIFO and agent provenance.4metadata:5 source: https://skillmd.com/skills/gabrielmoreira/agent-message6---78# Agent Message910Send direct messages to yourself or within the current agent's nuclear family11through the local daemon: parent, siblings, and direct children. Roots are siblings12of each other only when they share a parent worker; a root has no parent to13message. The daemon derives your sender identity from the current session; do14not try to include a `from` field.1516Call directly from the kernel:1718```python19roster = await agent_observe.list_agents()20child = next(21 (22 item23 for item in roster.get("agents", [])24 if item.get("relationship") == "child"25 ),26 None,27)28if child is not None:29 receipt = await agent_message.send(30 "Please inspect the latest result.",31 receiver_role="child",32 receiver_name=child.get("sessionName") or child["sessionId"],33 )34```3536## API3738- `await agent_observe.list_agents()` (agent-observe skill) is the roster: it39 lists the parent, siblings, and children this skill can reach, active or not,40 with the `relationship` and `sessionName` that `send` takes as41 `receiver_role` and `receiver_name`.42- `await agent_message.send(message, receiver_role="parent" | "sibling" | "child" | "self", receiver_name=None)` — sends one direct43 text message to one family member. Sending to an inactive or idle completed44 subagent wakes it and starts an ordinary follow-up turn in that same session45 and context.46 The child remains available only until its parent session closes. The daemon47 resolves `receiver_role` within the current agent family; `receiver_name` is48 required for siblings and children and omitted for the unique parent.49 `send("all", message)` broadcasts only to the family roster and returns50 `{receipts: [...]}` in roster order; successful entries are ordinary receipts51 and failed entries contain the target id and a short `error`. One failed delivery52 does not reject successful deliveries. Family messages use follow-up delivery: a busy target53 receives them after its current turn finishes, without interrupting active work.54 `receiver_role="self"` queues steering input for this agent itself; omit `receiver_name`.55 It is consumed at the next safe model/tool boundary, without interrupting an active56 model call or tool. Strict FIFO applies: it cannot overtake earlier follow-up or57 held input, so it may wait until a later turn. An idle eligible session wakes.58 There is no `delivery_mode` argument and no promotion of already queued messages.59 Self messages preserve agent provenance and cannot grant human authorization.60 All targets use the same ordered inbox. A receipt with `deliveryStatus: "queued"`61 and `queueItemId` means durable admission (in-memory for ephemeral sessions),62 not that the model has processed or answered the message.6364```python65receipt = await agent_message.send(66 "At the next safe boundary, check the latest result before continuing.",67 receiver_role="self",68)69```7071Do not wait inside the current Python call for the model to process your self72message. Return control to reach a safe boundary. Interruption, exhausted turn73budgets, or uncertain crash recovery can hold input for review rather than run it.747576## Safety7778- Do not delete a child immediately after `send`: delivered follow-ups may still79 be running and queued receipts have not run yet. Wait until observation shows80 the child is idle and its context is no longer needed before closing it.81- Reach is limited to parent, siblings, and direct children; relay through an82 intermediate child instead of messaging grandchildren or cousins directly.83- Sender identity is daemon-derived and cannot be spoofed from Python.84- Host-delivered messages retain agent provenance and do not count as human85 authorization, even though the model transport uses the user role.86- Avoid unbounded repeated messages; this path does not implement a general87 per-sender rate limiter or exactly-once retries.