Live view and manual control

Open Operations → Live view to inspect browsers while they work. Choose a Creator and group, or use Only with problems to find captchas, locks and browser errors within your access scope.

Find the right session

The grid offers 9, 16 and 25 tiles. Open a tile for the individual account’s session and context. A live frame is an observation of that browser; it is not proof that its latest action succeeded.

A browser can leave the grid when its work finishes, it rests or its machine disconnects. Check Activity, the account’s history and Issues after it closes.

Take control

1. Open the affected session and inspect its current step.
2. Choose Take control.
3. Wait for the runner to acknowledge that automation has yielded.
4. Click the browser image to use its mouse and keyboard controls.
5. Resolve the visible problem, then inspect the result.

Input becomes available after the runner grants control. Press Escape to release keyboard focus from the remote browser. Taking control holds the account’s automation so it does not type over you.

Hand the session back

Choose Solved, hand back when you have resolved the problem. Choose Hand back, not solved when you cannot complete it. Do not report success merely because the challenge panel disappeared.

After handing back, inspect the account’s health and next action. Safety rules still apply. A resting account or a separate proxy problem can continue to hold work.

When the stream is unavailable

Check the machine in Machines and the account’s profile binding. An unreachable runner cannot provide browser frames or accept input. If the session has ended, open the account’s own browser through the account page when available.

Workspace recording and evidence controls are in Runtime. Restrict access to live sessions to the teammates who need to operate those accounts.