← All developer systems
Hosted verificationSimulator

Verify ScreenSteer with the Hosted Simulator

Exercise the production protocol, consent flow, redaction, pointer guidance, registered actions, and teardown before embedding an SDK.

A protocol demonstration environment; it is not an embeddable SDK.

Download and install

Use the hosted browser simulator to verify consent, redaction, pointer guidance, registered actions, and session teardown.

Launch simulator

Requirements

  • ✓Two browser windows
  • ✓Console agent access
QUICKSTART

Run the verification workflow

The hosted simulator is a protocol-verification tool, not an embeddable SDK.

Verification flow
Steps
1. Open the hosted simulator and choose Get live help.
2. Approve view consent.
3. In another window, open Console → Sessions and join.
4. Verify video, redaction, pointer guidance, and control consent.
5. End from either side and confirm both views tear down.
STEP 1

What the simulator proves

The simulator runs the same TypeScript agent, registry, validator, session API, and LiveKit flow used by the Web SDK.

It demonstrates the support experience and protocol contract. It does not download or embed code into your application.

STEP 2

Run the two-window workflow

Open the simulator and select Get live help. Review and approve view consent.

In another signed-in browser window, open Console → Sessions, join the new request, and use the agent workspace.

STEP 3

Verify permissioned control

Move over the video to verify pointer guidance, request control, and approve it in the simulator.

Invoke registered controls in the simulated app. Unregistered areas cannot receive actions.

STEP 4

Verify redaction and lifecycle

Confirm the Account details area is visible locally but opaque in the agent video.

Rotate the simulated device to invalidate old geometry, then end from both device and agent sides.

What the device enforces

  • ●Explicit view and control consent.
  • ●Pre-publication redaction.
  • ●Registered semantic actions instead of raw input.
  • ●Expiry, sequence, controller, and layout validation.
  • ●Device and agent teardown paths.

Smoke test

  1. 1Launch the simulator and approve view consent.
  2. 2Join the request from a second console window.
  3. 3Confirm video, opaque redaction, and pointer guidance.
  4. 4Approve control and invoke every registered action.
  5. 5Rotate and confirm stale targeting fails closed.
  6. 6Revoke control, then end from both sides in separate sessions.

Troubleshooting

No session appears in the console

Confirm the simulator reports a live phase and that the console account is viewing the workspace configured for the hosted simulator.

Capture pauses

Keep the simulator tab visible; background browser tabs can throttle its canvas render loop.

Control actions remain unavailable

Request control from the agent and approve the pending request in the simulator before invoking a registered action.