Skip to main content
Collaboration in Studio escalates without switching apps. You start solo in a terminal. When a teammate needs to see what you’re seeing, you share it. When typing isn’t enough, you open a call inside the same session. The context — the device, the output, the conversation with Copilot — travels with you. Every shared surface is explicit about who can do what. A viewer watches. A co-worker types alongside you. The owner holds the keys. And when the session ends, the recording and the conversation are still there for the next person who needs to catch up.

​
When to share

Share a session when the live context matters more than a pasted transcript:
  • A second engineer needs to verify output before a change.
  • A vendor needs to see the device response in real time.
  • A field tech is on-site and you need one shared view of the console.
  • An incident commander needs visibility without keyboard control.
  • A teammate is taking over and needs the scrollback, current prompt, and Copilot context together.

​
Sharing a terminal

Any open terminal can be shared from the session toolbar. You pick a role for each person you invite, and you can change roles mid-session as the situation evolves.
RoleWhat they can do
OwnerFull control. Type, disconnect, end the session, adjust roles, invite more people.
Co-workerType alongside the owner. Typing indicator shows who’s at the keyboard.
ViewerRead-only view. See output, copy text, ask questions — cannot type.
Participant avatars sit in the session header so you always know who’s present. A typing indicator tracks the active hand on the keyboard, which matters when two people are in the same buffer. Handoff is a right-click on the participant — the owner can promote a viewer to co-worker during the session, or pull control back when it’s time to close out.

​
Handoff pattern

Use a clean handoff when control changes:
  1. The current operator stops typing and says what state the session is in.
  2. The new operator confirms the target host, privilege level, and next intended command.
  3. The owner promotes the new operator to co-worker or owner-level control.
  4. The previous operator stays as viewer until the next prompt or validation check.
It feels formal, but it prevents two people from typing into the same production shell with different assumptions.

​
Inviting guests

Not everyone you need to pull in has an Altostrat account. Copy a guest invite link and send it to the vendor, the field tech, or the external responder on the incident call. The link drops them into the session with the role you chose, so they land exactly where you want them. Guest access ends when the session closes — there’s no lingering grant to clean up afterward.

​
Voice and video

When two or more people are in a shared session, a Call button appears in the session toolbar. It opens a call inside the workspace, right next to the terminal everyone’s already watching. The call view has a responsive participant grid that adjusts from 1 tile up through 2, 4, 6, and 9 tiles depending on who’s on. Screen share lets you pull in a dashboard, a ticket, or a piece of a diagram that isn’t in Studio. Audio and video pickers let each participant choose their microphone, speaker, and camera without leaving the call. The important thing is that nothing context-switches. The terminal keeps running. Copilot is still there on the side. The call sits in the same tab as the work it’s about.

​
Working with Copilot while shared

Shared sessions and Copilot complement each other. Use Copilot to summarize long output, draft a plan, or turn the session into an artifact while humans keep control of judgment and approvals. Good shared-session prompts:
  • “Summarize the last 200 lines for the teammate who just joined.”
  • “List the commands that have changed state in this session.”
  • “Draft the handoff note with current hypothesis, evidence, and next checks.”
  • “Turn this successful investigation into a procedure draft after we finish validation.”

​
Team presence

A status dot next to each teammate in your organization shows online, away, or offline. Presence updates continuously while you’re signed in, so you can see who’s around before you ping them — and see when someone you’re waiting on comes back.

​
Session recording

Every shared terminal is recorded alongside the individual session recording. Tell participants before sensitive work. Recording can be paused, but the considerate move is to disclose before you do anything that shouldn’t be captured.
Recordings preserve the full buffer, the typing order, and the timeline so you can replay exactly what happened. This is the same mechanism that makes solo sessions replayable — sharing doesn’t change what’s captured, only who can see it later.

​
Privacy and visibility

Data typeWho sees it
Terminal outputEveryone in the session, in real time.
Your typingCo-workers see keystrokes as they happen.
Your voice and videoEveryone on the call, for the duration.
RecordingAnyone who can open the session recording after the fact.
Treat a shared terminal like shared production access, not a passive screen share. Everyone in the room has the same view of the device.

​
After the session

Close the loop before everyone leaves:
  • Save or share the recording if it is needed for review.
  • Create an artifact with the final summary, evidence, and commands run.
  • Save durable findings as memories.
  • Promote repeatable work into a procedure.
  • Remove any guest access by ending the session.

Terminal

Start a terminal session before you share it.

Teams and organizations

Organization scoping, roles, and how shared resources reach teammates.