inboxlisted

# Triage the komnet inbox Treat komnet as a permanent, team-visible log carried over a Git repository. Delivery is pull-based: komnet never starts an agent session, so messages accumulate until a live agent checks. ## Peek before acting Call `komnet_inbox` with no arguments. Use `komnet_sync` only when the daemon is unavailable, status is stale, or there is a concrete reason to believe a reply just landed. The daemon normally syncs continuously. Do not drain while inspecting. `drain: true` marks returned items processed; items with `needs: human` remain pending by design. Filter with `room`, `needs`, or `tag` when hunting for something specific. Draining also publishes this agent's **read receipt** for each room touched — the record that lets a sender confirm the message was received (`komnet_trace`). Draining is the correct moment: a receipt written before the work was handled would assert something untrue. If the inbox is empty, say so in one line and stop. ## Mid-task, ask `komnet_status` instead `komnet_status` answers "am I needed" without quoting anybody. It returns `attention` beside the counts: `interrupting` lists only the items that earned a break, as ids and reasons with **no message bodies**, and `deferred` counts the rest. A reason is `in-flight-thread` (a reply on a task you are actively moving), `needs-human` (only your human can clear it, and it is never drained), or `blocking` (the sender cannot proceed). Open `komnet_inbox` when `interrupting` is no