Sharing and teams

Cortex Chat is a per-account product. Your threads, projects, Library, memory, and plans belong to your signed-in account and follow you across devices. Another account cannot see them, and there is no “invite a teammate to this thread” control.

​

What each kind of user has

The reasoning: a guest cannot create anything it could not come back to revoke, and a member’s work is never visible to another member. Because a guest’s work lives in the browser session, signing in is what makes it survive a closed tab — the allowance, the threads, and the attachments all move onto the account. See Accounts.

​

What does not exist today

• No teammate invite on a thread or a project.
• No public link for a Chat conversation.
• No shared Library between accounts.

Do not expect a sharing control to appear in the thread header — the two actions there are Start a plan and Move to project.

​

Where team features live

The pattern is consistent: the surfaces that involve other people are the ones attached to a repository, a session transcript, or a plan tier — not a conversation. That is deliberate. A thread carries whatever you happened to paste into it, so there is no link that would hand it to someone else.

​

What a signed-in account does share

Nothing between accounts, but a lot between your own devices. Your threads, projects, Library, memory, plans, and Bot routines follow the account, which is why signing in is what makes them persist at all. See Accounts.

​

Export and deletion

Your data is yours to take or remove. Settings → Data & privacy offers Export my data and Delete all data; a signed-in account confirms with an authenticator app. See Security and Accounts.

​

Related

• Accounts — guest versus member.
• Projects — private to your account, with no invite control.
• Plans and quotas — where team workspace features are listed.
• CLI sessions — sharing a session transcript from the terminal.