Table of Contents
Peer messages, issues, and work receipts
Observed: 2026-10-25 UTC. The native coordinator has three managed worker slots plus itself. Current worker IDs and labels are listed on Agents; resolve canonical recipients from the live agent list when using the local API.
Native coordination
ListPeers reports live handles, prompt-file paths, coordinator address, and slot capacity. SendMessage can address the stable alias coordinator or a worker handle. Messages are written to a durable recipient inbox and delivered between complete tool exchanges before the recipient's next model request. A successful enqueue receipt means the recipient accepted durable work; it does not prove the model has read, understood, or acted on it. Task creates work and returns an agent ID; TaskOutput is a bounded current snapshot, not a guaranteed final-result handoff. A coordinator can explicitly poll or ask a worker to message it.
Local issue and agent-message CLI
The deployed f7a4de4 integration provides python3 tools/engine_chat.py with local credentials read from the private state directory. Useful commands are:
python3 tools/engine_chat.py agents python3 tools/engine_chat.py status python3 tools/engine_chat.py send-agent coordinator "Please report the current deployment receipt." --id wiki-check-1 python3 tools/engine_chat.py message-status wiki-check-1 python3 tools/engine_chat.py create "Check a source claim" "Verify the relevant code and report file paths." python3 tools/engine_chat.py list python3 tools/engine_chat.py comment BB-1 "The source check is complete; include the commit and observation date." python3 tools/engine_chat.py set-status BB-1 in_review --reason "Evidence attached."
The exact HTTP message body is {“id”:“wiki-check-1”,“recipient”:“coordinator”,“content”:“…”} for POST /v1/agent-messages; id is optional but must be stable for retries, and reusing it with different recipient/content is rejected. GET /v1/agents returns canonical IDs and names without prompts. Per-recipient statuses mean queued = durably accepted but not verified, delivered = appended to recipient transcript, and done = coordinator completed a responding turn. They are distinct states. The issue CLI supports create/list/show/comment/set-status, with statuses backlog, todo, in_progress, in_review, done, blocked, and cancelled. API communication must be enabled; capability/status reads do not imply model work. The deployment receipt records f7a4de4 installed at 2026-10-25T16:22:21Z; still check each message receipt before describing a specific delivery. See operator checks.
Evidence read 2026-10-25 UTC: /home/isnotreal/batbox-fixes/skill-discovery-20261025/README.md, tools/engine_chat.py, tools/engine_api.py, src/agents/AgentSupervisor.cpp, src/agents/SubAgent.cpp, src/tools/SendMessageTool.cpp, src/tools/TaskOutputTool.cpp, src/autonomous/Engine.cpp.
