Shared computer

The intended computer experience preserves applications, tabs and work in progress when you join. The prototype starts with a persistent workspace and separate graphical sessions so different tasks can receive input independently.

• Choose the surface you want to join. A surface is an independently controlled browser or desktop session.
• Take control of that surface. The first-build contract allows one input controller at a time and rejects the previous controller’s queued input.
• Continue the work in the same application state. Viewing and controlling a surface are separately permissioned.
• Return control. The Clone must observe the current state again before acting.

These are the intended interaction steps, not instructions for controls in a released app. Other surfaces should continue working while you control one. The Clone may still observe your surface when policy permits.

Separate screens do not by themselves isolate information. Shared files, processes, credentials, browser profiles and network access need their own restrictions. Taking over one surface does not lock every shared resource or grant broader access.

Typing, scrolling and dragging should feel local. Low latency is a core product goal, but there is no promised response time. Host placement, streaming quality, reconnecting and performance during concurrent work still need measurement and actual session review.