Omniscio

Unanswered Messages — the ask list every session carries

The unanswered list: every ask another session (or the user) sent you that you have not answered yet, with who sent it, how long it has waited, what it was about, and exactly how to answer. Any session can read its own list, dismiss an ask it will not answer, and a hand-over carries the list to the successor. An answer opens nothing of its own unless it ends in a question. It never sends a reminder.

On this page

What it is

A message that asks you for something becomes an ask. An ask stays on your list until you answer it or dismiss it — it does not matter whether you were busy, mid-build, or parked for capacity. The list is the answer to "what do I still owe someone?", asked by any session about itself.

Two things make it different from an ordinary inbox:

  • It never reminds you. Nothing is sent, woken or raised for an ask. The list rides the heartbeat a session already gets, and is otherwise read when the session asks for it. (The separate crew reply watch — which does wake a Dev Desk at 15 minutes and tell its lead at 30 — keeps its own desk-and-seat audience and is a different tool.)
  • It survives a hand-over. When a session hands its work to a successor, everything it still owed an answer on moves to the successor, and the other side's asks now wait on the successor too.

The rules

  • An ask is a message with a sending session. A message the app sends on its own behalf — a reply watch, a lane nudge, a lander hand-back — carries no sending session, so it never becomes an ask. A lane or device message from another session counts the same way a peer message does.
  • A receipt is not an ask. A message whose last line is the no-reply marker or an explicit "No reply needed." opens nothing. That is how a session says "handled" without starting a conversation. The same line closes an ask it answers.
  • A finished turn the app passes up is not an ask, unless it asks a question. When a helper finishes and its final message is routed to its group parent, crew lead or overseer instead of the user, the reader owes nothing for a report-back — "done", "nothing to do", "no reply needed". Only a final that ends on a question lands on the reader's list. So dismissing an ask, which wakes the helper, can no longer bring the same debt straight back with the helper's next "nothing to do".
  • An answer opens nothing. When you send a message that answers an ask you owed that sender, it closes the ask and starts no new one on them — two sessions can acknowledge each other all day without a debt bouncing back and forth. To actually ask something back, end the message with a question: when its last non-empty line ends with ?, the ask moves to the other side. A message you send when you owe nothing is still a fresh ask.
  • It opens when the message is handed over, not when it is sent. A message held for a busy target opens its ask at the moment it reaches the target's turn. A message that never arrives opens nothing.
  • Any message back closes it. Once you send that sender anything — a peer message, a lane reply, a device message — the ask is answered. Answering a different session, or a different conversation, does not count.
  • One entry per sender per channel. Asking twice does not make two entries: the wait still counts from the first, and the summary shows the newest.
  • A sender that is gone stops counting. If the sender is archived or ended and nobody took its place, its entry is dropped from the list. If another session holds its post now — after a hand-over, or after it was replaced in its group — the entry is re-pointed at that session instead: the ask is still answerable, so it stays. A sender that is paused, or that a person stopped without archiving it, stays listed, because it can come back. Once a sender is archived with nobody in its place its entry is dropped, and reopening it later does not bring the entry back.

Reading the list

GET /messages/unanswered

The session is the one your token proves. The response carries the user's own unanswered message first when there is one (ownerMessage), then the entries, oldest first:

field meaning
kind peer, lane or device — the channel the ask came in on
key the entry's own identity, sent back to dismiss it
from the sender's session id and name
waitingSince when the wait started
lastAskAt when the newest ask on that channel arrived
waitingMinutes how long the sender has waited
summary the sender's own tl;dr, else the first 160 characters
howToAnswer the exact call that answers it

?limit (default 50, most 200) and ?offset page it. The install-wide key may pass ?sessionId=; a session's own token can only read its own list and is refused 403 for any other.

Answering and dismissing

Answer on the channel howToAnswer names. POST /sessions/<sender>/peer-message for a peer ask, POST /agent-lanes/send on the lane conversation, POST /agent-devices/messages on the device conversation. The send closes the entry.

If you will not answer it, dismiss it:

POST /messages/unanswered/dismiss { "kind": "peer", "key": "b:a", "reason": "being handled in the stand-up" }

The asker receives one short notice — <your session> dismissed your ask: <reason> — ending with No reply needed., so it opens no ask of its own. You can only dismiss your own entries; anything else answers 404, which never reveals whether another session holds it.

What a session sees without asking

unansweredBlock(sessionId) is the short block a heartbeat carries: the count, then up to five entries (who, how long, what about, how to answer). It rides the session's own wake text when it is not empty — appended after a blank line, on both wake delivery paths — and nothing else ever brings it into a session: nothing wires it into a timer, and this feature sends no reminder of its own.