Omniscio

Watch and reply to a shared session in a web browser (signed in)

If someone shared an Omniscio session with you, you can watch it in any web browser — on a computer or a phone — without installing anything. Open the browser link, sign in with your email, and the conversation appears and keeps updating. If the owner let you reply, you can also type a message right there. If not, the page is read-only.

On this page

What it is

Multiplayer Sessions lets an owner bring people into one of their live AI conversations. Until now, everyone needed the Omniscio desktop app. The browser viewer is a small web page on shares.omniscio.com that shows the same conversation a desktop guest sees, live, to anyone the owner already let in. It never shows more than the desktop does.

Where to find it

  • In the invite email — under Not at your computer? there is a browser link.
  • On the invite page — the page the email's button opens has a Watch in your browser button beside Open in Omniscio.
  • From a join link — the owner can press Copy browser link in the Share dialog's Join link block and hand that address out instead of the app link. It is the same reusable link as the app link, and the owner can turn it off at any time.

How it behaves

Signing in

  • The page asks for your email and a password. Use the email address the invitation was sent to, and press Sign in, or Create account if this is your first time.
  • A new account must confirm its email first: the page says Check your email, and a button checks again once you have opened the link. Send the email again is there if it got lost.
  • Google sign-in is not offered yet.
  • No Omniscio account yet? Signing in creates your Omniscio account on the spot. It needs a verified email. If Omniscio has switched to invitations only, the page says An invitation is required and tells you to ask the owner to invite your email address.

Watching

  • The conversation shows who said each message — the owner, another guest, or the assistant with the AI it runs on — and new messages appear as they are written.
  • A Watching · read-only badge sits at the top for someone who may only watch, with a line saying the owner has not given you permission to reply. There is no message box.
  • The page does not tell the owner you are there; unlike the desktop app, it shows no "is here" mark.

Replying

  • If the owner gave you permission to reply, the badge says Watching · you can reply and a message box sits at the bottom. Type and press Enter to send (Shift+Enter starts a new line), or press Send. The box empties the moment you send, so your message shows once, in the list below the conversation. The box stops at 50,000 characters. It takes plain text only.
  • Each of your latest five messages shows one plain line: Sending…, Waiting for the owner, Sent to the assistant, Answered, Not delivered or The owner turned this down. While it waits, the page adds that the owner may need to approve it first. In a session that may run in the cloud the owner approves every guest message, so a message can wait a while.
  • You can have 3 messages waiting at once. The box tells you so and the Send button stays off until one has been picked up.
  • If the owner has been away more than 10 minutes, the page says so and tells you your message is saved and will go through when they are back.
  • If sending fails (for example your connection drops) the page says so and puts your text back in the box. Press Send again: the same message is never sent twice.
  • If the owner removes you or ends the conversation while you are typing, the box disappears and the page tells you; a message that had already gone through still reaches the owner.
  • The page signs you in, joins you through the same join step the app uses, then shows the conversation. A join link is reusable: it works for anyone who has it, again and again, until the owner turns it off or replaces it. When it has been turned off or replaced, the page says it no longer works and asks you to get a new one.
  • The secret part of the address is wiped from the address bar before the page makes any request, and it is never written to a log, an error message or a report. It travels once, in the body of the join request to the same site. Because it is gone from the address bar, reloading before the page has joined you shows This link is incomplete: open the join link again. Once you have joined, the address bar holds the share address instead, and a reload works.

When access ends

  • The owner stops sharing — the page says the owner stopped sharing.
  • You are removed, or signed in with the wrong account — the page says you do not have access, with a Sign out button so you can try the invited account.
  • The share reaches its end date — the page closes itself and says the share has ended.

What keeps it safe

  • The link alone opens nothing. You must be signed in, and the cloud decides from your sign-in whether you are on the share — the same rules that protect desktop guests.
  • Nothing private travels in the address. The share id and any join secret sit after the #, which browsers never send to a server, and the page clears a join secret from the address bar before it sends anything. A join link stays usable by whoever holds it until the owner turns it off, so the owner is the one who ends it.
  • The only thing the browser writes is your message. It writes the same queued message the app writes, and only if you were given reply permission; the cloud and the owner's computer check it exactly as they do for the app (permission, size, the per-share spending limit, and owner approval in a session that may run in the cloud). It writes no presence mark or anything else, and it keeps no sign-in of its own beyond the sign-in the browser already stores.
  • Private notes and secrets never reach the cloud copy in the first place; the owner's computer removes them before upload.

Last verified 2026-11-16