Owner cards (a status card any session can keep)
One card, kept current, for any session. A session can put a status card in the owner's inbox, refresh it as work moves, file a report beside it, and ask the owner a question the owner answers right there — without joining a crew. The card belongs to the session that raised it and nobody else can take it over. A session linked under a parent with the Group tool hands its cards to that parent instead, the same way its finished turns go.
On this page
What it is
Owner cards are a small tool in front of Omniscio's inbox-card primitive. The card appears in the same inbox as an agent alert: the owner reads it, can archive it, and can answer it if it asks a question.
The tool offers three kinds of card:
- An update — the session's standing card. One per topic (the default topic is
Overall), the newest words replace the previous ones in place. - A report — a complete writeup, filed as its own card. A later report is another card; it never overwrites an earlier one.
- A question — its own card, waiting until the owner answers it or the session withdraws it. Each question has its own identity, so a session can leave two questions and an update open at the same time and every one stays answerable.
Before this tool existed, only a registered crew lead could keep a standing card, and a plain session had to raise a fresh dismissible alert each time it wanted to say something. Owner cards make that a normal capability of every session; the old lead cards are the same cards underneath, so an existing mission's open cards carry over.
What the owner sees
A card titled with the session's name (and its topic when the session names one), carrying the body the session wrote. An update card quietly changes in place as the session reports again — it does not stack up copies. A question card stays until it is answered or withdrawn, and the answer travels back to the session as the owner's message, so the session can carry on from the answer.
If the owner archives a card, nothing happens to the session: it keeps running. The session's next update brings the card back into the inbox.
When the session reports to another session
A session that belongs to another session — linked under it with the Group tool — does not put its
cards in the owner's inbox. The text goes to the session it reports to, the same way its finished
turns do, and a question arrives as a question. The reply says so: deliveredTo is parent, with
the parent's id and name and whether it accepted the hand-off. Nothing is filed for the owner.
If the hand-off is refused, the reply says that too (accepted is false, with a reason) and no card
is created — the session decides what to do next.
The exception is the owner's own turn: when the owner typed into the session to start the turn being
answered, the card goes to the owner even with a parent above the session. A session with no group
parent, and an always-on Overseer session owned by a slot, keep exactly the card they have today
(deliveredTo is owner).
When a session hands its work over
A session can be succeeded by a new one — a hand-over. The open cards move with the work: every update, report and question the old session still has in the owner's inbox is re-keyed onto the new session, so the owner keeps exactly the cards they were reading and any answer they give arrives at the session that is now doing the work. A card the owner already put away stays where it is. If the new session had already opened a card of its own on the same subject, the two do not stack up: the newer one stays and the older one is withdrawn.
This covers both ways a session is succeeded: the stay-alive hand-over, and a crew lead starting fresh, where a brand-new session takes the post over and the outgoing one is archived. The carry also runs once more just before the outgoing session is archived, so a card its last turn raised is not stranded there. News from the new lead on a subject it already has a card for updates that card rather than opening a second one for the owner.
A card that moves to the new session is dated from the moment it moved, so it never reads as older than the session now holding it — except a report card, which keeps the date of its own report so the next report still counts what the owner said since.
Cards raised by a tool
Not every card comes from a session. A tool inside the app — a review panel, a background helper — can raise its own card to report what it found, and withdraw it again. Those cards belong to the tool, not to a session: they carry no answer route to a session, and anything they offer the owner is a button the tool itself declares. Raising the same card again updates it in place rather than piling up copies, and a card the owner dismissed comes back when the tool raises it again. The same Plain Speak rule applies to them: one raised without its glance card is held out of the inbox, and raising it again with the card brings it back.
Only code inside the app can raise or withdraw a tool card; there is no web route for it, and the generic alert door refuses the tool-card family outright.
The rules that keep it trustworthy
- Only the session that owns the card can write it. The card is keyed to the session its own credential proves. A different session, or a session pretending to be another by naming it in a header, is refused.
- A card follows the report. A session with a live group parent hands its card to that parent and writes nothing for the owner, unless the owner opened the turn by typing into the session.
- A card waiting on the owner is never overwritten. If a standing card carries a question the owner has not answered, the session's next routine update opens a new card beside it instead of destroying the question. The session can still replace it by restating the question.
- Reports never replace each other. Every report is its own card.
- Each question has its own identity. A retry with the same request id lands on the same card; a new request opens a new one.
- The same inbox doors apply. The "Allow agents to raise inbox alerts" switch stops the tool when it is off, each source has its own creation budget, and a card that is dropped or held says so in the reply instead of pretending it was delivered.
- Plain Speak. While the owner's Plain Speak overlay is on, a card must carry its Plain Speak glance card. Without one the request is refused with the reason, and the session is told exactly what to add.
Related
- inbox-alerts.md — the inbox card itself: what it looks like, how it is answered, and how duplicate alerts are kept from flooding the owner.
- question-widget.md — the clickable answer options a question card can carry.
Last verified 2026-11-11