Browser
Sends prompts and displays private pictures and results. It cannot operate Windows directly.
Interactive tour — mock data Private operator view
No installation or account required
Try the real operator workspace with mock data.
The same console component used by an authenticated operator is filled with an unmistakably fake computer, account, desktop, activity, and result.
The interactive tour uses clearly marked mock data, requires no account or device, and never contacts a computer. Anything entered is validated and immediately discarded.
Synthetic demo — no real computer
Everything in the tour is deterministic mock data. Nothing entered here becomes production work.
Review the complete simulation boundary
- No real device is contacted.
- No production request or account record is created.
- No entered prompt or action is sent to analytics.
- All pictures, timestamps, computers, and results are mock data.
Showing the AI working mock state. Connect AI is working.
The recurring remote-control path
Connect. Ask. Run. Follow.
Current mock state: AI working. Status words and shapes carry the meaning; the tour never invents a progress percentage.
- ConnectConnectedComplete
- AskPrompt sentComplete
- RunRunning locallyCurrent
- FollowResults appear hereNext
Now use the same console an authenticated operator sees.
Only the records and MOCK labels differ. The desktop, Agent, Activity, Settings, prompt, Stop, and result components share the production renderer.
RemoteEndpoints
Studio PCMock computer · Connect online
Alex Morgan Interactive tour — mock data
Private desktop picture · mock
Running locally
Studio PC desktop
Connect OnlineRemote control ActiveLast picture Just now
Prompt Connect AI
The AI runs on Studio PC and uses the capabilities available to the signed-in Windows account.
You
Open the project dashboard, check the overnight build, and summarize anything that needs my attention.
Connect AI
Working on this computer now. New desktop pictures and activity appear as Connect reports them.
Connect AI workingUse Stop to request cancellation
Stop requests cooperative cancellation and cannot undo completed external effects.
Private activity
What Connect reported
- Desktop ConnectedStudio PC came online with Remote control active (mock event).
- Instruction QueuedThe remote operator sent a prompt to Connect AI.
- Instruction StartedConnect AI started using the mock desktop.
Connection and revocation details
- Extension on target
- Enabled — mock
- Account delivery
- Enabled — mock
- App version
- Mock build
- Last heartbeat
- 2026-07-13T18:04:18Z
- Reported capabilities
- desktop, programs, network, connect ai
- Authorization
- Independent RemoteEndpoints extension enabled during setup
Stop, Pause, Disable, and Revoke are not interchangeable.
Each changes a different scope. None promises to roll back work already completed on the computer or network.
- Stop One run
- Requests cooperative cancellation of one active run. Completed external effects remain.
- Pause Account delivery
- Closes this account's new-prompt delivery gate while preserving the pairing. It cannot re-enable a locally disabled extension.
- Disable Target extension
- Closes the RemoteEndpoints extension gate inside LocalEndpoint Connect on the target computer. The website cannot re-enable that local gate.
- Revoke Pairing
- Invalidates the server-side pairing and deletes its retained active desktop pictures. An offline computer learns the revocation when it reconnects; pairing again is required.
Mock settings cannot change a real computer.
The authenticated workspace uses these controls to pause account delivery or revoke a pairing. This public tour has no account, credential, device record, or production connection to change.
Browse another deterministic mock state
Exact workspace · five run states
See how one remote run changes.
What this state means: Request Stop prevents further work when Connect receives it; it cannot undo completed external effects.
Showing: AI working. Choose a state to reload this one shared workspace with deterministic mock records.
RemoteEndpoints carries control. Connect AI operates the computer.
RemoteEndpoints authenticates the remote operator and carries prompts, control messages, private desktop pictures, and status. The enabled RemoteEndpoints extension lets LocalEndpoint Connect AI perform the work on the target computer; the website itself does not invoke Windows APIs.
No per-prompt local approval: Installing and enabling the RemoteEndpoints extension is the intentional authorization for unattended remote control. A person is not expected to be at the target computer to approve each prompt.