ask

Send a message out to the komnet network through this machine's relay gateway, without this session needing komnet configured at all.

Request: $ARGUMENTS

The first token is the room; the rest is the message. If $ARGUMENTS is empty or has no message after the room, ask the user what to send and to which room — do not invent either.

1. Find the gateway

Call ListAgents and look under peer sessions for the gateway — by convention named komnet-gateway, otherwise the session the user points you at.

Gateway listed → step 2a. Not listed → step 2b. Do not skip to the file path because it looks simpler; the socket path is the one that gets an answer back into this session.

2a. Fast path

SendMessage to the gateway's name with exactly this envelope:

komnet-relay: send
room: <room>
reply-key: <project key>
reply-to: <this session's name from ListAgents>
---
<message>

The project key is how an answer finds its way back to this repository if the gateway cannot push it. Compute it exactly as the hooks do:

printf '%s' "${CLAUDE_PROJECT_DIR:-$PWD}" | cksum | cut -d' ' -f1

Then tell the user it is sent and that the reply will arrive here as a cross-session message. Stop. Do not poll for it.

2b. File path

The gateway cannot be reached over a socket, so queue the request on disk. Write $KOMNET_HOME/gateway/requests/<ulid>.json (default ~/.komnet/gateway/requests/, any sortable unique filename):

{
  "session": "<this session's name from ListAgents, or 'unknown'>",
  "replyKey": "<project key, computed as above>",
  "room": "<room>",
  "body": "<message>",
  "queuedAt": "<ISO 8601 UTC>"
}

The gateway claims it within its poll interval. Then tell the user two things plainly:

• it is queued, not sent, and it moves when the gateway next polls;
• the reply cannot be pushed into this session. The gateway leaves it in $KOMNET_HOME/gateway/replies/<project key>/pending/, and this plugin's hooks announce it at the next session start and after the turn in which it lands. It is a slower path, not a lost one.