Command reference
oko sessions inbox
Shows the inbox of a session a process outside the broker holds: which process reads it, and every message left there by `oko sessions send`, with whether it still waits, was delivered or was refused.
Invocation#
oko sessions inbox IDInputs and options#
- ID is the session id, or a transcript file name ending in it.
Output and state effect#
- Prints {session, folder, reader, messages: [{file, state, message}]}: reader is the pid the session's process recorded when it loaded Oko's OMP extension (null when none did), and each message is waiting, delivered (the extension handed it to the session as the user's message) or refused (the file was not a message; message then carries written, the bytes, and refused, why), oldest first. A session nothing was ever left for has an empty inbox. Nothing is changed.
- Oko Desktop's Sessions screen shows the same inbox under each row of Outside the broker (who reads it and how many messages wait, were delivered or were refused) and offers Send to its inbox beside Adopt, which leaves the row's text there as `oko sessions send ID --text TEXT --submit` does and answers with the product's refusal word for word; both go through the native API's sessions domain (inbox with session; send).
Refusals and safe exits#
- A missing ID refuses with “oko sessions inbox requires <id>” (exit 2); an inbox folder that cannot be listed, a message file that cannot be read or is not JSON, and an unreadable reader record refuse naming the file (exit 1).