All tools

agent_send

Agent mesh · macOS · Windows

Effect: send (strongest supported action). Status: gated.

Gated means the tool requires an installed app, a connected account, permission, or runtime availability. Check those requirements on the listed platform before using it.

macOS

Purpose

Sends a coordination message to an agent on ANOTHER of the user's machines (get its handle from agents_list). Use it to hold merges during a release ('freeze'), announce a PR is up ('pr-ready'), hand work over ('handoff') or say a release shipped ('release-out'). Without to_agent it reaches every agent on that machine, which is what you want for a freeze. A DIRECTED to_agent must be one that is ALIVE — take it from agents_list, never invent it: if it is not alive you get a 404 listing the agent_ids that ARE alive on that machine, so you can re-address to one of those instead of the message being silently lost. The recipient gets it on its next agent_inbox poll — this is not instant, and it is not a request you can force: the other agent decides what to do.

Required inputs

Permissions and confirmation

No explicit confirmation parameter is exposed in this snapshot. This does not grant permission to act: obtain user authorization before any real action.

Full input schema — macOS
{
  "properties": {
    "from_agent": {
      "description": "Your own agent_id, so the recipient knows who is asking",
      "type": "string"
    },
    "msg_type": {
      "description": "One of: ping, pr-ready, freeze, freeze-clear, release-out, handoff, note",
      "type": "string"
    },
    "payload": {
      "description": "The content: reason, PR number, branch… Keep it small (max 16KB).",
      "type": "object"
    },
    "to": {
      "description": "Handle of the target machine, from agents_list",
      "type": "string"
    },
    "to_agent": {
      "description": "Optional: a single agent_id on that machine (it must have checked in). Omit to reach all of them.",
      "type": "string"
    }
  },
  "required": [
    "to",
    "msg_type"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "msg_type": "note",
  "payload": {
    "message": "The documentation review is ready."
  },
  "to": "demo-workstation"
}

Windows

Purpose

Sends a coordination message to an agent on ANOTHER of the user's machines (get its handle from agents_list). Use it to hold merges during a release ('freeze'), announce a PR is up ('pr-ready'), hand work over ('handoff') or say a release shipped ('release-out'). Without to_agent it reaches every agent on that machine, which is what you want for a freeze. The recipient gets it on its next agent_inbox poll — this is not instant, and it is not a request you can force: the other agent decides what to do.

Required inputs

Permissions and confirmation

No explicit confirmation parameter is exposed in this snapshot. This does not grant permission to act: obtain user authorization before any real action.

Full input schema — Windows
{
  "properties": {
    "from_agent": {
      "description": "Your own agent_id, so the recipient knows who is asking",
      "type": "string"
    },
    "msg_type": {
      "description": "One of: ping, pr-ready, freeze, freeze-clear, release-out, handoff, note",
      "type": "string"
    },
    "payload": {
      "description": "The content: reason, PR number, branch… Keep it small (max 16KB).",
      "type": "object"
    },
    "to": {
      "description": "Handle of the target machine, from agents_list",
      "type": "string"
    },
    "to_agent": {
      "description": "Optional: a single agent_id on that machine (it must have checked in). Omit to reach all of them.",
      "type": "string"
    }
  },
  "required": [
    "to",
    "msg_type"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "msg_type": "note",
  "payload": {
    "message": "The documentation review is ready."
  },
  "to": "demo-workstation"
}