Omniscio

Share a session with a teammate (the owner half of Multiplayer Sessions)

Share this session invites a named teammate into one of your live sessions. They read the conversation in their own Omniscio under Shared with me, and — if you grant it — reply into the same conversation under their own name. This is the sending end.

On this page

What it is

Share this session invites a named teammate into one of your live sessions. They read the conversation in their own Omniscio under Shared with me, and — if you grant it — reply into the same conversation under their own name.

This is the sending end. The receiving end is shared-with-me.md. Both halves are one feature (multiplayer-sessions), off by default, and entirely separate from the unrelated Shares feature that publishes artifacts to a public URL.

Desktop only for now. Multiplayer Sessions is built for the Omniscio app on a computer. 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 these screens. The one thing a paired phone does get is the two push notifications described under What reaches your phone.

Where to find it

How to share

Open the session's ⋯ menu and pick Share this session (or press Ctrl+Shift+G). It is one step, like sharing a Google Doc: click the field and your workspace teammates drop down with their name and photo — type to narrow the list and pick one — or type anyone's email address. Each person becomes a chip with their own permission beside it; add as many as you like, remove one with its ×, and press Invite. A typed email turns into a chip when you press Enter, a comma or a space; a name with a space in it ("Ann Lee") just keeps searching.

Somebody you have already added still shows in the list, marked Has access — they are there so you can see the invite already went out, and they cannot be picked a second time.

Notify people sits under the field and is on by default: it is what tells the person they were added. Turn it off to add somebody silently — useful when you are setting a conversation up before they know about it. And if you invite somebody who was already on the share, the dialog says so instead of reporting a fresh invite.

The list shows only current members of your own workspace — never you, never anyone already on the share, never someone already in the field. Picking a teammate invites their account directly, so you never need their email, and Omniscio never shows it. If a pick cannot be invited, the message says so and suggests their email instead. An account with no workspace sees no list and invites by email exactly as before.

If your workspace's people cannot be loaded, the field says so — Could not load the people in your workspace. You can still invite anyone by email. — with a Retry beside it. The sentence stays up while the retry runs, so the list never blinks to empty, and an email invitation is never blocked by a roster Omniscio could not read: type the address and press Invite as usual.

The row names who the session is already shared with, so you can see that from the menu without opening the dialog. It is absent entirely while the feature is off.

Once a session is shared, a small people chip sits beside its title in the session header — the accent-coloured people icon with the number of people it is shared with. Hover it to see their names; click it to open the Share dialog. It appears the moment you send the first invite, and a teammate who already has an Omniscio account shows under People with access straight away.

When you do not know in advance who is coming, make a join link instead of inviting people one by one: in the same Share dialog, under General access, pick what the link allows (read, or read and reply) and press Create link. Anyone signed in to Omniscio who opens it confirms, then joins with that permission. The link is reusable: it keeps working for everyone who has it until you turn it off or replace it. Copy browser link beside Copy link gives a web address for the same link, for people without the app: they sign in with their email and watch in a browser, and reply there if the link allows replies. The full walk-through is in join-a-shared-session-by-link.md.

Who has access, and who can find it

People with access lists you first, marked Owner, then everyone you added with their photo, their name and their permission. Their permission is a dropdown right there, so changing somebody from can-view to can-reply is one pick, and Remove takes one person's access away without disturbing anyone else. Someone you invited shows as Invited until they accept; Remove cancels the invitation.

Below that is General access, the Google Docs idea, in two states:

General access Who can open it
Restricted Only the people listed above
Anyone in your workspace with the link Any full member of your workspace — a Team Chat guest is not one

The second one also carries a permission — what somebody who arrives that way may do. Full members of your workspace can see that the conversation is shared and join it with one click, but they cannot read it until they do. A Team Chat guest — someone invited to particular channels only, rather than to the workspace itself — is not a full member: a workspace-wide share never appears in their list, and a link to one opens nothing for them. General access can be changed at any time after the share exists, so you can open a conversation up to the workspace later, or close it back down to just the people listed. If you belong to no workspace, this section simply offers Restricted, because there is no workspace door to open.

Copy link puts a link to the shared conversation on your clipboard. The link opens the shared copy on any machine that already has it — yours is the original, so the link is for sending someone else. Somebody who has not joined yet still joins from Shared with me, where the conversation appears as soon as their copy exists — they do not need to restart the app.

The share itself is created on that first invite — there is no separate "create the share" click, because nobody shares a session as an end in itself. A session that has never been shared shows just the one field, the permission dropdown and the button.

Permission What they can do
Can view Read the conversation live
Can reply Read it, and send messages into it under their own name

You can change anyone's permission afterwards, from the same list, and Stop sharing deletes the cloud copy outright.

Removing ONE person is a separate action from Stop sharing: it ends that person's access and destroys nothing, and they are told in one plain line — "You were removed from this session" — within seconds, in the conversation they already have open. Removing the same person twice asks you once: the second request answers the first rather than stacking a second identical approval card.

When a viewer asks to reply

Somebody you gave Can view can press Request reply access in the conversation. You get one Approve / Decline card in your inbox — "«their name» asks to reply in «session title»" — within about a minute, while your Omniscio is open.

  • Approve switches that person to Can reply at once, exactly as picking it from the permission dropdown would. It is a widening, so it needs the same team plan as any other can-reply grant.
  • Decline leaves them on Can view, and they are told it was not approved this time.
  • They cannot pile requests up. One request per person can be waiting at a time; pressing the button again while it waits does nothing. After you answer they may ask again — and if they keep asking, Remove still ends their access.
  • An old card can never undo a later choice. If you change their permission in the dialog, or remove them, before answering, the card goes away by itself, and approving a card for a request that was already answered changes nothing.
  • Nothing reaches your phone for this — the request is an inbox card only.

What they see, and whose words are whose

Your teammate's view updates as the agent writes, not on a timer, and shows the same status and tool rows you see, so their pane reads as a normal session rather than half a conversation. What your own computer looked like when the session started is not part of the conversation: the launch notes about work that stayed behind — unsaved changes, your project's secret files, the master test baselines that did not reach the cloud machine — stay on your machine. Every human message carries its author — a name and a picture — on your screen and on theirs, so you can tell your own words from one guest's and from another's at a glance.

Who can open it, and how they hear about it

By default a share is restricted: only the people you added can open it. Anyone in your workspace with the link widens that to every live member of your Team Chat workspace — they can open the conversation's page from the link without being added first, and opening it joins them (view-only or can-reply, whichever you chose as the general permission). Leave it restricted to keep a conversation to the people you named.

Every invite sends the person an email — "«you» shared «session title» with you («share ref»)" — naming the session in the subject and in the body, with what they can do, and with a button that opens that conversation. The button is a normal web link, so it works in Gmail on the web and on a phone: it opens a small Omniscio page that says "Press the button and your browser will ask to open Omniscio", and that press opens the share the email was about, whether the app was already running or was started by the click. The page works on a computer with Omniscio installed, and it also offers Watch in your browser: someone on a phone, or without the app, can sign in with their email and follow the conversation in the browser, and can reply there if you gave them reply permission (see watch-a-shared-session-in-a-browser.md). A browser reader needs a verified email, gets an Omniscio account on first sign-in (or an "invitation required" screen when sign-up is invite-only), and writes nothing into the share except a message you allowed them to send, so you never see them as present. A browser reply is judged exactly like an app reply: your approval settings, the spending limit and the guest permission limits all apply. The email carries the same browser link under Not at your computer?, and someone without the app is still pointed to the download. If the page cannot read its link, it says so in plain words and tells them to open the app and look under "Invitations". Until they press Accept there, the link lands on their invitation's row rather than the conversation. The old omniscio:// link stays at the bottom of the email for pasting into a browser's address bar. The share's id travels after the # in the web link, so no web server ever sees it. Because each subject carries the session's own title and a short reference to that share, each invite is its own conversation in Gmail rather than one long thread, and an older invite in that thread cannot drop them into a session that has since ended — an ended share opens read-only and says so. If they have never turned Multiplayer Sessions on, they are offered a one-click Turn on and open card that lands them on the same conversation. A teammate you picked from the workspace list is emailed at the address on their own account; you never type it and it is never stored on the share. Turning the notification off sends nothing at all: the person simply appears under Participants and finds it the next time they open Omniscio.

What reaches your phone

Two events send a push notification to your paired phone, and only these two:

  • You were invited to a session. It goes to the guest, on their own computer's phone link, and tapping it opens the shared conversation.
  • The agent finished answering your message. It goes to the guest, as a notice on their own computer, only after the owner's assistant has finished the turn that answers it, not when the message is merely received. A turn that was stopped before it produced an answer sends nothing. Tapping it opens the conversation.
  • A guest message is waiting for your approval. It goes to the owner, only when Approve each message before it reaches your assistant is on in the share dialog or the session runs on a cloud machine, and tapping it opens the session the message is held in. The same notice sits in your inbox and clears itself once you approve or decline the message.

The push shows fixed wording only — never the guest's name, the session title or what they wrote. Someone joining, leaving, replying, @mentioning you, or a share ending stay in the inbox and send nothing to the phone. Your normal notification silence mutes the push, and a push reaches the phone only while the phone is paired and has notifications allowed.

How it behaves

The one-time warning, and why it comes first

The first time you ever share anything, a notice explains that a copy of the conversation is uploaded so the people you invite can read it. It appears before anything leaves your computer, and confirming it is what starts the upload. A warning shown afterwards would be an apology, not a disclosure — so if you dismiss it, nothing is created and nothing is sent.

You see it once, ever.

What your teammate can read

You choose, before you share. The Share dialog's Guests can read row offers two options:

Guests can read What reaches the cloud copy
The whole conversation (the default) Everything, including what was said before they joined
Only messages from now on Only what is said after you press Invite; everything before stays on your computer

The whole conversation copies up the conversation from the start, not just what follows the invite. This is the single most important thing to know before inviting someone into a session you have been working in for a while — which is exactly when Only messages from now on is the safer pick.

Only messages from now on is not a screen filter. The earlier part is never uploaded at all — not when you share, not when Omniscio restarts and re-copies the conversation, and not if an older message changes later. A reply the assistant was still writing when you pressed Invite counts as earlier, so it stays home too.

You make the choice once, when the share is created. After that the same row tells you which one your guests get — for example Only messages from 9:14 PM on — and the one-time upload notice is worded to match. To change it, stop sharing and share again.

Your computer's own housekeeping is not part of the conversation — how many sessions you are running, its session limit, and the "waiting for a free place" notices that go with them stay on your machine.

What the AI is told

The moment an invite lands, the AI running that session is told — before its next word — who joined, what they can do, and what they can read: the entire history, or — on a share made only from now on — just what followed the moment you shared, with a request not to repeat or summarise the earlier part unless you ask. It is not a message in your transcript and it costs no extra turn: it rides along invisibly with your next message.

From then on the AI keeps working normally but stops volunteering private or sensitive detail into the open conversation the way it would in a one-to-one.

When you Stop sharing, it is told that too, and goes back to normal.

The AI's private line to you

The AI can mark a passage as for the owner only. Those passages are stripped out before anything reaches the cloud, so your teammates never receive them — and in your own transcript they render as a clearly labelled private note.

Use it for exactly what it sounds like: the AI raising a concern about a teammate's request, or asking your permission before acting on one.

Two honest limits, stated plainly:

  • It is a convention the AI follows, not a wall. A teammate can still ask the AI to repeat what it said privately.
  • If the markers are ever malformed, the AI's whole message is withheld from your teammates rather than half-shown — and you see it unchanged, markers and all, which is the signal that something went wrong.

The guarantees that are enforced: only you can approve a permission request, and a teammate's message never inherits whatever auto-approve you have switched on for yourself.

A session that runs on a cloud machine always asks you first. Cloud sessions run without permission prompts, so on a shared cloud session every message from a guest waits in your inbox until you approve it, even when Approve each message before it reaches your assistant is off. The share dialog says so under that switch. Guests can still reply; you decide what reaches your assistant. If the app cannot tell where a session runs, it asks you too.

Cost

Inviting and reading cost nothing, and your teammate never pays — they can be on the free plan. Their replies spend your tokens, because their message drives your agent in your session. That is why can-reply is per person and revocable.

Creating a share requires the team tier; being invited to one does not.

What a guest's message may do without asking you

While your agent works on a guest's message, it runs at the Guarded level, whatever level you picked — Full trust included. Reading files outside the project, fetching web pages, running shell commands and writing outside the project all show you the normal approval card first, and the sensitive-file check (SSH keys, credentials) asks again even if you run at Full trust. Your own messages keep your chosen level.

The limit lasts until the agent finishes answering that message, including any automatic retry of it, with a 30-minute ceiling. If you stop the agent in the middle of a guest's message, your own next message may show one extra approval card; the one after it is back to normal.

A spending limit for guests

Because guests' replies spend your money, you can cap them. In the Share dialog, under Guest spending limit, type a dollar amount ($0.01 to $10,000) and press Save. Below the box you see how much guests' turns have cost so far, so you can choose a limit that fits.

  • Off by default. With no limit, guests reply exactly as before. Remove limit takes it off again.
  • Only guest turns count. The cost of the turn a guest's message started is added up. Your own turns never count, even when you write right after a guest.
  • At the limit, guest messages wait. They are not sent to your agent and not thrown away. Your inbox gets one card naming the session and the amount, for example "Guests have used $5.00 of the $5.00 limit". Change limit opens the Share dialog; dismissing the card keeps replies paused.
  • Guests are told plainly. They see one line in the conversation: "Paused by the owner — your messages are saved and will be sent when they resume." They never see the amount.
  • Raising the limit sends the waiting messages at once. A new limit at or below what guests already used keeps them waiting.
  • It is a soft limit. It is checked before each guest message, so a guest turn already running when the limit is reached finishes, and can take the total a little past it.
  • Only you can change it, by hand. The limit lives on your computer only, and no agent can raise it — not even the agent your guests are talking to.

When your sign-in lapses

Sharing needs your Omniscio cloud sign-in. If it is lost or can no longer be confirmed, guests can still read what is already there, but their new messages cannot reach you. Before, nothing said so.

Now the conversation you shared shows a notice above the message box: "Sharing is paused because your sign-in has lapsed. Guests can't be heard until you sign in again." Press Sign in again to open Settings on the Accounts page. Once you are signed in, the notice goes away by itself within a minute, with nothing else to press. Nothing shows when Multiplayer is off or when you have shared nothing.

When an address does not match

You are not told whether an Omniscio account uses the address you typed — the invite reply is deliberately identical whether or not one exists, so nobody can use the invite box to probe who is registered. The Participants list is the signal instead: it shows everyone the invite actually reached, whether or not they have opened it yet, so an address no account uses simply never appears there. If a name you expected is missing, check the address.

The one thing the reply does say is "already has access" when the person is already on the share: nothing is written and no second email is sent. That is a fact about your own share's participant list, which you can already read — it tells you nothing about whether any other address belongs to an account.

Who is here right now, and who is typing

Above the message box in a shared conversation there is one quiet line naming the other people who have it open — "Sam is here · Priya is typing…". Everyone sees it: you, each guest, and a guest who can only read. It names only people who have that conversation actually open on a screen right now, so it answers the question you will genuinely ask of it — is anybody else in here with me — rather than "is that person's computer switched on".

  • It disappears when nobody else is around. There is no empty state, no placeholder and no badge: an ordinary conversation looks exactly as it did before this existed.
  • It clears itself. A typing mark fades a few seconds after the person stops, with no send needed, and somebody whose app closes or crashes drops off within about a minute.
  • A read-only guest is shown as here, and never as typing. They cannot reply, so the line never implies they are about to.
  • Nobody can appear as anybody else. The line's names come from the participant list you invited them from, not from anything the other person's app sends, so a guest cannot label themselves as you.
  • It costs nothing while nobody is looking. The signal exists only while that conversation is on screen; a share nobody has open writes nothing and reads nothing.

Letting guests make their own copy

In the Share window there is a switch, "Let guests make their own copy". It is on by default, because a guest can already read the conversation and copy the text by hand. Switch it off and the "Make a copy" action disappears for that share, and the guest's app refuses the request too.

  • A copy only ever holds what the guest could already see. Your private notes and anything the share hides stay hidden.
  • It is a separate session on the guest's own account. Nothing they do in it reaches yours, and it carries none of your files, keys or permissions.
  • Switching it off does not take back a copy someone already made.
  • Changing the switch needs the sharing service to be up to date. If it is not yet, the Share window says so, and copying stays on.

Rules your workspace admin can set

If you belong to a company workspace, its owner or admins can set four house rules for sharing, in Settings under Workspace, in a section called "Sharing conversations". Only an admin sees the controls; everyone else in the workspace sees a line saying only an admin can change them. The section is there only while Multiplayer is switched on.

  • Allow sharing with people outside the workspace. Switch it off and you can invite only other members of your workspace. An email address of anyone else is refused, and the Share window says your workspace admin only allows sharing with people in the workspace.
  • Allow share links. Switch it off and "Create link" is replaced by a line saying your admin turned links off. A link that already exists keeps working until you turn it off yourself.
  • Default permission for new guests. What "Permission for new people" and the link permission start at. You can still pick the other one for a given invite.
  • Default end date for new shares. What the end date starts at (1 hour, 24 hours or 7 days). You can still pick another end date, or Never, for a given share.

When a rule stops you, you see one plain sentence naming your workspace admin, not a general permission error. Rules apply only to new shares, invites and links; conversations you already shared and people already in them are not changed. With no rules set, nothing is different. The rules are checked by the sharing service itself, so they hold even if someone uses an older copy of the app. Until the sharing service is updated, the section stays hidden and sharing works as before.

Last verified 2026-11-14