agent_checkin

Agent mesh · macOS · Windows

Effect: write (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

Announces YOU (this agent session) to the mesh: your role, the repo you are working on and what you can do. Call it when you start working and again every few minutes on long tasks — the entry expires after ttl_seconds, so an agent that stops checking in disappears from the directory instead of looking alive forever. You must check in before agent_inbox will deliver anything: you receive what arrives AFTER you show up, not the backlog.

Required inputs

agent_id — Stable name for this agent session (e.g. 'builder', 'qa', 'release'). Reuse it across check-ins.

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.

Use only the apps, accounts and resources authorized by the user on this platform. Consult this tool's platform-specific description for its connection and permission requirements; this catalog does not assert additional OAuth scopes or OS entitlements.

Full input schema — macOS

{
  "properties": {
    "agent_id": {
      "description": "Stable name for this agent session (e.g. 'builder', 'qa', 'release'). Reuse it across check-ins.",
      "type": "string"
    },
    "caps": {
      "description": "What this agent can do (e.g. ['merge','deploy'])",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "herdr_pane": {
      "description": "If you are running inside a Herdr-managed pane (check HERDR_ENV=1 first), your own pane id — e.g. $HERDR_PANE_ID. Registers this agent for #2540's automatic wake: when a Mesh message arrives, a fixed local prompt ('[auto-wake #2540] Hay N mensajes de Agent Mesh; llamá agent_inbox') is submitted to this pane via `herdr agent prompt`, so you get a real turn instead of a silent notification. The '[auto-wake #2540]' prefix is what tells you the turn came from the mesh and not from a person typing the same sentence. Never send the value of a remote message here — only your own pane id. Purely local: never sent to the mesh backend. Omit if you are not in Herdr.",
      "type": "string"
    },
    "repo": {
      "description": "Repo you are working on (e.g. 'local-mcp')",
      "type": "string"
    },
    "role": {
      "description": "What you are doing (e.g. 'builder', 'reviewer', 'release')",
      "type": "string"
    },
    "status": {
      "description": "What you are doing RIGHT NOW, one line (e.g. 'porting evernote to Go', 'measuring #1164 on 3674da7e'). agents_list shows it with its age, so peers can tell working from stuck — update it when your task changes.",
      "type": "string"
    },
    "ttl_seconds": {
      "description": "Seconds until this entry goes stale, 60-86400. Omit it and the default comes from `role`: 3600 for an agent that works (builder, reviewer…), 900 for 'ping' and 'verification'. Your presence also renews itself with every mesh call you make, so this is the silence you can afford, not how often you must check in.",
      "type": "integer"
    }
  },
  "required": [
    "agent_id"
  ],
  "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.

{
  "agent_id": "demo-reviewer",
  "repo": "demo-project",
  "role": "reviewer",
  "status": "Reviewing the documentation example."
}

Windows