inbox

Triage the komnet inbox

komnet never starts an agent session, so delivery is pull-based: messages accumulate in the inbox while no agent is running, and a session that never checks silently ignores its teammates.

When to run

Nothing interrupts you to say a message arrived. There is one hook, at session start, and that is all — when to look during a session is your call, because you are the one who knows whether a teammate's answer bears on what you are doing.

Look when it would change what you do next:

• At the start of a session — the SessionStart hook prints the brief; this skill acts on it. The brief leads with tasks you already had in flight. Resume one before taking on anything new.
• When you finish a task, before handing back to the user.
• When you are waiting on an answer you asked for — after a komnet ask or a review request, check before you conclude the thing is unanswered.
• When you are blocked on something another team owns, before guessing or working around it.
• Whenever the user asks about komnet, another agent, or a pending question.

Do not check on every turn: an inbox that was empty two tool calls ago is still empty, and the daemon is already polling.

Mid-task, ask komnet_status instead

komnet_status answers "am I needed" without quoting anybody:

attention: {
  interrupting: [ { id, room, from, needs, priority, thread, reason } ],   // no bodies, ever
  deferred: 3                                                              // a count, nothing more
}

A reason is one of:

reason	What it means
in-flight-thread	a reply on a task you are actively moving — this is the work answering
needs-human	only your human can clear it, and it is never drained, so it waits
blocking	the sender says they cannot proceed