Shared with me (the invitee half of Multiplayer Sessions)
Shared with me is a top-level sidebar entry that lists sessions a teammate shared in — never your own. Opening one shows that conversation read-only, live, in your own Omniscio; if the owner granted you can-reply, a composer appears at the bottom and your messages go into their session attributed to you by name. A reply is text only — images and files cannot be sent into a shared conversation — and it is the receiving end of the owner's Share this session dialog.
What it is
Shared with me is a top-level sidebar entry that lists sessions a teammate shared in — never your own. Opening one shows that conversation read-only, live, in your own Omniscio; if the owner granted you can-reply, a composer appears at the bottom and your messages go into their session attributed to you by name.
It is the receiving end of the owner's Share this session dialog. The two halves are one
feature (multiplayer-sessions), gated off by default, and are entirely separate from the
unrelated Shares feature, which publishes artifacts to a public URL.
Desktop only for now. Reading and replying inside a teammate's live session is a computer flow in this first version. The phone is not told the feature is switched on, so it never shows the Shared with me entry, and nothing has been built to give the phone that screen. If a shared conversation is opened on the phone anyway (from the inbox, say), it shows the "view only" notice with no reply box, no Join, no Leave and no Request reply access, and the phone's connection to your computer refuses every Multiplayer request. A paired phone still gets a short push when you are invited or a conversation moves, and those pushes name nothing of the conversation.
Where to find it
Shared with me, its own top-level row in the sidebar — never nested in a group, and never hidden by folding one. It is not a separate screen: a conversation somebody shared with you arrives as a real session in your ordinary session list, and it opens in the ordinary session panel — the same transcript, bubbles and search every session has. Everything specific to a share lives at the bottom, in the composer area.
The conversation shows up under Shared with me the moment your copy exists — no restart and no clicking around to make it appear. Omniscio tells the open window about the new conversation at the same moment it saves it; before this, a copy saved while the app was open stayed out of the list until something else made the app reload its sessions.
A shared conversation sits idle almost all the time, because it is the other person's assistant that is between turns — it is still a listed conversation, so the Live Sessions header counts it and never reads (0) over a chat you can see (interrupted-sessions-section.md).
How it behaves
If somebody sends you a link
The owner can copy a link to a conversation they shared, and opening it lands on that conversation in your own Omniscio — it is the same shared copy under Shared with me, opened directly. If the conversation is a workspace share you have not joined yet, join it once from Shared with me first: the link opens a conversation you already have, it does not add you to one.
If you have never turned Multiplayer Sessions on
The invitation first appears under Invitations (and as a card in your inbox) with Accept and Decline. Nothing of the conversation reaches your computer until you accept.
Someone can invite you before you have ever enabled the feature, and the invitation still reaches
you. Pressing Accept raises one card in your inbox — <Sharer> shared "<session>" with you — with two buttons:
- Turn on and open switches Multiplayer Sessions on, starts receiving shares immediately (no restart) and lands you on Shared with me, where the conversation is now waiting.
- Not now leaves the feature exactly as it was and stops the app asking about that particular share. It never asks about that one again.
The card arrives either way: whether you clicked the Open it in Omniscio link in the invite email, or the app noticed a share already addressed to you in the background.
If you already have Multiplayer Sessions on
The invitation first appears under Invitations (and as a card in your inbox) with Accept and Decline. Nothing of the conversation reaches your computer until you accept.
Once you accept, you are told in the same inbox, with a plainer row: <Sharer> shared "<session>" with you, and one line saying whether you can reply or only read. It is one row per conversation,
however you came to accept it — the link in the email, a workspace share you join, or being added
back to a conversation you were removed from.
That row clears itself. Open the conversation and it goes, because you clearly have it; if your access ends first — you are removed, or you leave — the row goes too, so an invite never sits there for a conversation you can no longer open.
Why it never lists your own sessions
A new share is created with an empty participant list — the owner is deliberately not a participant on their own share. So your own shares correctly never appear here. That is not a quirk to route around: the owner reads their share directly by id (to manage participants), while you are reached through the participant list. Testing the owner down the invitee's path returns nothing and looks exactly like a bug.
What the person sees
| State | What shows |
|---|---|
| A share you can read | The mirrored conversation in your ordinary session panel, oldest first |
| Message arrives while you are elsewhere | One inbox row, "New message in «session title»", with the newest words and a link to the conversation; your phone gets a push naming none of it |
Granted replier |
The ordinary reply box; your messages go into the owner's session, attributed to you by name |
| A reply the relay did not take | Your bubble disappears, your draft comes back into the box, and one line says why: you need to be signed in, you can no longer reply, the conversation is no longer shared, or too many replies at once. A failure that might still have landed — a server error, a timeout, a dropped connection — keeps the bubble and says the reply may not have arrived, so you can check before sending again |
| The owner's agent is running | The reply box stays usable and says Send a message... — there is no Stop button and no "queued" promise on your screen, because the running turn is the owner's agent and only the owner can stop it |
Granted viewer |
No reply box at all — a "view only" notice sits where the composer would be, not a disabled box |
Granted viewer and you want to help |
On the desktop app, a Request reply access button sits under the view-only notice (the phone never shows it). Press it and the owner gets one Approve / Decline card; the button turns into "Request sent — the owner has been asked." If they approve, the reply box appears on its own. If they decline, the notice says "The owner did not approve reply access this time." and the button comes back. You can have only one request waiting at a time — pressing again while one is pending changes nothing |
| A workspace share you have not joined | A Join control in place of the composer — seeing the row grants no access, and one click asks the relay to add you |
| The owner is away | Their Omniscio has stopped publishing the share's presence heartbeat — their computer is not there to take your reply — so the message area says "The owner is offline. Your message is saved and will be answered when they're back." while a message or suggestion of yours is still waiting (before you send, a guest who can reply sees the same line in the form Messages you send are saved…), never as an error and never as a fake success. It is their APP being gone, not their agent resting between turns: a live conversation with nothing running shows no such line, and the line clears on its own the moment their heartbeat returns |
| The owner stopped their turn — a Stop, an interrupt, or the agent exited | The reply box STAYS: the owner's session is only idle, and your next message wakes it and lands in the conversation like any other turn |
| The owner closed the conversation for good — they archived it or ended it | You can still read the whole transcript; where the reply box was, one plain line says the shared conversation has ended and no new messages can be sent |
| You archived a shared conversation | It moves to Archived under Shared with me, exactly as an archived conversation does in any other project — expand the section and it is there, transcript intact, and one click on Unarchive brings it back. A conversation the owner ended stays in that list only while you still hold it; one the owner removed you from is the exception — it is in no list at all, Archived included |
| You no longer want it | Leave removes only your own access and is offered in every state where you still hold the share — live, idle, or closed by the owner. The owner is told |
| You left, then the owner invited you again | The new invitation waits under Invitations; once you accept, the conversation comes back to Shared with me with its reply box and you get one "shared with you" notice, exactly as any new invite. Leaving is not a permanent block on that share — and a leave you did take is never mistaken for the owner removing you, so your copy of the conversation is kept and no "You were removed" line appears |
| You were removed, then the owner invited you again | The same fresh path: the conversation comes back to Shared with me with the permission the owner gave you, you get one "shared with you" notice, and the removal notice from before is cleared. A re-invite is never blocked by the removal |
| The share was revoked — the owner pressed Stop sharing | It leaves your live list, your inbox tells you why — one row naming the conversation, which reads the same whether the owner stopped sharing or removed you, and which has no Go to Session button because there is nothing left to open — and your copy of the conversation is removed from your computer at the same time. It is not filed under Archived either, so you will not find it in any list afterwards: the inbox row is what you keep. Without that row a revoked share was silent — the conversation simply vanished, which reads exactly like the app breaking. This is detected even if the live connection had quietly stopped updating |
| You were removed | Your inbox says so, and the conversation stays open with one plain line saying the same thing at the end of it: "You were removed from this session." It appears without a refresh — whether the owner removed you while you were online or while you were away — and the copy then leaves "Shared with me": its row, the hub's badge and the panel's counts all stop counting it at once, it is not filed under Archived either, and it is no longer readable from your phone. Your copy of the conversation is deleted from your computer at the same moment — the notice is the only row left on it, so nothing of the owner's conversation survives on your install after your access ends |
What you cannot send yet
Your reply is text only. An image or a file cannot be sent into a shared conversation today — the reply lane carries your words, not attachment bytes. The reply box says so in one plain line, the attach and screenshot buttons are not offered to you, and a paste or drop of a picture is refused with that same line instead of being attached and then quietly left behind. Describe what you are looking at in words and the owner and their assistant will get it.
Who said what
Every message carries its author — a name on every bubble, whoever wrote it: the owner, each guest, and the agent itself, named by the session's title. Human messages also carry a picture on your screen and on everyone else's (initials when there is no photo), so you can tell the owner's words from your own and from a second guest's at a glance. A guest whose account has no profile name is shown by their full email address — the address the owner typed when inviting them, so their own messages and the owner's list of participants name them the same way — never as "A guest". Messages written before this carry the sender's name in their text instead; they still show the right author.
What you type is what the others read: your reply travels as your own words, with nothing this app adds for its own models wrapped around it, and it appears once — not again after it comes back from the owner's side. The exported transcript names you on your messages too, instead of calling every message "You".
It arrives live
The conversation no longer refreshes on a timer. A newly written agent reply appears as it is written, with the same status, tool and lifecycle rows the owner sees. If your connection drops, nothing is deleted — the conversation simply catches up when it returns.
How you find out
An invite emails you: "«name» shared «session title» with you («share ref»)", naming the session in the subject and what you can do, with one link that opens your invitation in Omniscio's Invitations hub; after you accept, the same link opens the conversation. Each invite has its own subject and short share reference, so invites do not pile into one email thread — and if the conversation has ended by the time you click, it opens read-only with a plain notice instead of a reply box. If Invitations is switched off, the link says so and offers the setting — turn on Show invitations in my Inbox first. The owner can turn that notification off, in which case the share simply appears in your list with no email.
When the conversation moves without you
The owner is told every time you write. You are told the same way, on your own computer: when the owner — or the owner's assistant — writes into a shared conversation you are not looking at, one row appears in your inbox: "New message in «session title»", carrying the newest words and opening that conversation. It arrives whether the message came from the owner's own keyboard or from their assistant, and your phone gets a short push that names nothing of the conversation itself.
It is deliberately quiet, and each rule is there for a reason:
- One row per conversation, never one per message. A whole back-and-forth is one card whose words keep up with the newest message.
- One alert per turn. An assistant that writes forty rows while it works is one interruption, not forty.
- Never about your own words, and never while you already have that conversation on screen.
- A re-invite does not re-announce the past. When you leave and the owner invites you again, the conversation's earlier messages are not news to you, so they raise nothing at all; only a message the owner writes after the new invitation does. And opening a shared conversation clears both of its inbox rows — the "shared with you" one and this one — even in the first seconds after an invite, before your computer has finished reading the share's own record.
- Gone the moment you open it, the same as the invite row — and gone if the owner stops sharing or you leave, so a card never points at a conversation you can no longer read.
Before this, a message could sit in a shared chat asking for your answer with nothing on your machine to pull you back to it. If you would rather not hear every turn, the row is a normal inbox alert type and you can turn Shared session new message off in Settings.
"On screen" means you are actually looking at it: the row is suppressed only while that conversation is the one in front of you in a focused window. A window left minimised or in the background still tells you, because that is exactly when you are away from it.
When your own message is answered
If you can reply, you can ask a question and walk away. When the owner's assistant finishes answering the message you sent, your computer shows one desktop notification: "Your message was answered", naming the conversation. Clicking it brings Omniscio forward on that conversation.
- Only you. It goes to the person whose message was answered, never to the other people in the conversation, and never about the owner's own turns.
- When the answer is finished, not when it starts. An assistant that says "let me look" and then works for ten minutes tells you at the end, not at the first line.
- One notification, however many messages you sent. Send two in a row and you hear once, when the last one is answered.
- Never while you are looking at it, using the same "on screen" test as the inbox row above.
- Never after your access ends. If you leave, are removed, or the owner stops sharing before the answer lands, nothing is shown. A message the owner declines shows nothing either.
- Your notification settings decide. Silence, Focus Mode and your desktop notification choice apply to it exactly as they do to every other notification Omniscio shows.
- The words stay in the conversation. The notification names the conversation only, never the reply itself.
Two honest limits: Omniscio listens for the answer only while it is running, so a message answered after you closed the app is not announced when you reopen it (the inbox row above still is); and it stops listening a day after you sent the message.
A share the owner opened to your whole workspace can also be reached straight from the link without being added first — opening it joins you, at the permission the owner set for the workspace. Everyone in that workspace can see the share exists; nobody can read the conversation until they open or join it. Joining that way lasts only as long as your workspace membership: once you leave the workspace, or its owner removes you, the share and its conversation close to you too. A share you were invited to by name is yours regardless of any workspace.
Nothing shared with you arrives
Look in your inbox for Shared conversations are paused: sign in again. It means your sign-in for shared conversations has expired; click Sign in again, and everything shared with you reconnects and the notice clears itself.
Cost
Reading costs nothing. Replying spends the owner's tokens, because your message drives their agent in their session — which is why can-reply is granted per person and revocable.
Making your own copy
On a conversation that is live for you, Make a copy (next to Leave conversation, desktop only) lets you try your own idea without touching theirs. Pick one of your projects and Omniscio starts a new session there, with the conversation you can see as background. It starts quietly: nothing runs until you type your first message, and it runs on your own account.
- The copy holds only what you could already see, as a snapshot. Later messages in either session never flow to the other.
- The button is not shown, and the app refuses, when the person who shared the conversation has turned copying off, or when the conversation is no longer live for you.
Related
- overseers.md — an unrelated always-on session, not this.
- The owner-side dialog, the trust boundary, and the invariants that lock all of it live in
the feature contract:
.claude/memory/contracts/multiplayer-sessions-contract.md.
Last verified 2026-11-16