---
title: Share a session with a teammate (the owner half of Multiplayer Sessions)
---
# Share a session with a teammate (the owner half of Multiplayer Sessions)

## 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](shared-with-me.md), 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](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.

## 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**: type the teammate's email, pick their permission, press **Enter** or **Invite**.

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.

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 |
|---|---|
| **View only** | Read the conversation live |
| **Can reply** | Read it, and send messages into it under their own name |

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

## 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

**Everything — including what was said before they joined.** Sharing copies up the whole
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.

### 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 that they can read the entire history. 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.

### 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.

### When an address does not match

You are told plainly that no Omniscio account uses it. The reply an invite gets back is
deliberately shaped the same whether or not an account exists, so nobody can use the invite
box to probe who is registered — the dialog reads the one field that distinguishes them and
tells you honestly.

## Related

- [shared-with-me.md](shared-with-me.md) — what your teammate sees.
- The trust boundary and every invariant that locks it:
  `.claude/memory/contracts/multiplayer-sessions-contract.md`.