Collaboration

Matrix collaboration adds people to an existing Chat or terminal. It does not create a separate workspace or move the session to another computer.

The session continues to run on the owner's Matrix computer, using the owner's runtime context and configured AI access. Each collaborator acts as themselves at the authorization boundary.

Find sessions shared with you

Open Shared with me from Chat navigation. A badge appears when invitations are waiting.

Pending invitations show the owner, item type, and proposed role. Accept an invitation to add it to your shared list, or decline it without opening the session. Accepted items open inside the normal Chat or Terminal app. Existing deep links resolve to the same native app experience.

If a session is revoked or the owner's runtime is unavailable, Matrix keeps the app frame in place and shows a safe recovery message.

Collaborate in Chat

A shared Chat uses the ordinary Chat timeline and composer:

• Owner and editor messages sent from the composer are prompts to the shared AI session.
• Human prompts appear on the right with subtle name and avatar attribution.
• AI responses remain on the left and use the normal Chat presentation.
• Viewers can read the Chat but cannot send prompts.
• Queue details stay hidden unless a request is waiting, several requests are pending, an approval is required, or a failed request can be retried.

Everyone sees the same canonical Chat history. Matrix does not reconstruct live history from a snapshot.

Discuss with people

Use Discussion in the session header for notes that should not prompt the AI. Discussion opens over the session as a side drawer on larger screens and a full-height sheet on phones, so the Chat or terminal remains underneath.

Discussion drafts are private to their author and session. Close the layer with its Close control, by selecting the light-dismiss area, or with Escape on a keyboard. Viewers can read discussion but cannot post.

Share and manage access

The access control in the session header shows whether the session is shared, your role, and the people who have access. Owners can open Manage access to:

• invite an existing Matrix user by supported username or email;
• choose editor or viewer access;
• change an accepted member's role; or
• revoke an invitation or remove a collaborator.

Matrix keeps Share snapshot and Invite collaborators separate. A snapshot is a point-in-time link and cannot authenticate live collaboration. Inviting a collaborator grants access only to the shared resource unless the access summary explicitly says it is inherited from a shared project.

Roles

Server authorization remains authoritative. A control disappearing in the interface is not the security boundary.

Collaborate in Terminal

A shared terminal stays focused on terminal output. Its compact session controls show your role and the current controller without adding a collaboration dashboard.

Editors can request control when it is available. Owners can take over according to the session's control rules. Input, paste, resize, renew, and release operations are checked against the current connection and lease, so delayed actions are rejected after control changes or access is revoked.

Terminal discussion and access use the same layered controls as Chat.

Privacy and boundaries

Standalone Chat or terminal sharing does not grant access to the parent project, sibling resources, the owner's home files, apps, or credentials. Personal presentation state and drafts remain personal. The owner's Matrix computer remains the execution authority throughout the shared session.