loupe-inboxlisted

# Asking the owner through the Loupe inbox An item is one question or one to-do for the project owner. An ask is the set of items one session hands over. An ask closes when every blocking item in it closes, so an ask with no blocking item closes at once. The tools act on the project your token is bound to. When the flag is off, every tool answers "The inbox is switched off on this instance." ## Search before you ask 1. Call `inbox_search` once for each item you plan to hand over. It includes closed items. Search with two or three key words, not the whole title, because every word must match. 2. When an `answered`, `done` or `declined` item already answers you, read it with `inbox_get` and do not ask again. 3. When an open item asks the same thing, call `inbox_join` with its `itemId`. Pass the same `sessionId` and `bridgeId` as for `inbox_ask`. You then wait for the same answer. `inbox_join` refuses a closed item. Pass `itemId`, never the item number. ## Ask Call `inbox_ask` with: - `sessionId`: your own session id. Read it with the Bash tool: `echo $CLAUDE_CODE_SESSION_ID`. - `bridgeId`: only when the bridge started you, from the footer line "Your session id is … and your bridge id is …. Pass both to inbox_ask." Omit it in an interactive session. - `context`: one or two sentences the owner reads above the items, such as "Working on card 33, I need two decisions before I write the migration". - `items`: each with a `kind` (`question` or `todo`) and a one-line `title`.