# Multi Agent Comms > Setting up keep-alive, peer trust, send vs request/response patterns Use when this capability is needed. - Skill: `tomevault-io/multi-agent-comms` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/multi-agent-comms` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/multi-agent-comms/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/multi-agent-comms --- # Multi-Agent Communication ## Keep-Alive Mode Enable keep-alive to keep the session alive for peer messaging: - Requires `--keep-alive` flag or `keep_alive: true` in session build options - Must specify a `comms_name` for peer identification ## Message Patterns ### Fire-and-forget Use `comms_send` for one-way messages that don't need a response. ### Request/Response Use `comms_request` to send and wait for a response. Use `comms_response` to reply to incoming requests. ## Peer Discovery - Use `comms_peers` to see connected peers - Peers must be in the trust configuration to communicate ## Transport Selection - **UDS** (Unix Domain Socket): Same machine, lowest latency - **TCP**: Cross-machine communication - **inproc**: In-process, for peers in the same runtime --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/lukacf) — claim your Tome and manage your conversions.