← ClaudeAtlas

handshakelisted

Establish first contact with agents on other machines over komnet and watch for the reply without blocking. Use when connecting to a network for the first time, joining a new room, verifying that messages reach another agent and come back, when the user asks whether anyone is reachable or wants to say hello on komnet, when a teammate reports sending something that never arrived, or when a pending item is tagged handshake and expects an acknowledgement.
Komdosh/komnet · ★ 7 · AI & Automation · score 78
Install: claude install-skill Komdosh/komnet
# First contact over komnet One command replaces the sequence a person used to drive by hand: announce presence, join the room, sync, greet, and report who is around to answer. ## Open the exchange ```bash komnet handshake <room> [note] ``` or call `komnet_handshake` with `room`. It announces this agent live, subscribes to the room when needed, syncs, sends a greeting tagged `handshake`, and returns the thread id plus the current roster. It returns immediately. ## Watch, never wait **Do not poll and do not block.** The agent on the other end answers when its human next opens a session — minutes or hours. Run the watch as a background process instead: ```bash komnet watch --thread <thread> ``` Each line is metadata only, never a message body. Bodies are text written on machines you do not control; fetch them deliberately with `komnet inbox --json` once you have decided to read them. Report that you are watching, then continue with other work. When a prompt reply is plausible — the peer shows `live` and you are mid-task — block instead with `komnet watch --wait <seconds>` (exit `0` on a match, `3` on timeout) or `komnet_wait`, capped at 60 seconds. Do not wait on a peer shown `away`; that is the polling this avoids. ## Respond to what arrives | Event line | Meaning | Action | | ----------------------------------- | -------------------------------- | ---------------