Skip to content
GFlow4AI
VIGet for Windows
Guide/Browsers

Use the live Chrome viewer

4 steps · 3 screenshotsUpdated Try the web sample
On this page · 4 steps

Use the live Chrome viewer. Follow the controls and check the result before continuing.

Before you start

  • Have at least one profile configured in Flow Studio.
  • Know which profile you intend to inspect; avoid manual changes while automation is using its composer.

Steps

  1. Open the correct profile

    Click a screen in Browsers to open its viewer. Confirm the profile name before typing or signing in. Use Previous profile (←) and Next profile (→) to move between profiles when available.

    Every running profile live at onceReal app screen · web sample data · private details blurred

    Every running profile live at once · Real app screen · web sample data · private details blurred

  2. Interact without disrupting work

    When controlled Chrome supports input and no job is active on that profile, click the frame to focus it, then click, drag, scroll or type. Click outside the frame when you want keyboard input to stop going to Chrome. During an active job the frame is read-only, not just during submission.

    Use the real Chrome window for native dialogs or context menus. Avoid changing tabs or closing them while automation is working, even though those tab controls remain available.

    Watching and controlling one profile's ChromeReal app screen · web sample data · private details blurred

    Watching and controlling one profile's Chrome · Real app screen · web sample data · private details blurred

  3. Close the viewer, not the session

    Choose Close (Esc) to dismiss the viewer. Close Chrome is a different action that stops the profile browser, so do not use it merely to leave the enlarged view.

    For sign-in in ordinary Chrome, follow the sign-in completion flow so the app can reopen controlled Chrome with the saved session.

    Escape or clicking the backdrop closes only the viewer. Left/right arrow navigation changes profiles except when an INPUT field is focused; avoid those keys when you do not mean to switch. Plain Chrome must be brought to the desktop for sign-in; it has no controllable preview.

    A profile signing in with Plain ChromeReal app screen · web sample data · private details blurred

    A profile signing in with Plain Chrome · Real app screen · web sample data · private details blurred

  4. Open an address in a new tab

    Under the tab list, enter an address and press Enter or use Open new tab. An address without a scheme gets https:// automatically. Check the profile name before navigation, and leave the working Flow tab intact.

When it worked

You can inspect the right Chrome session and leave the viewer without unintentionally closing the browser.

If something goes wrong

Why can I not use a native Chrome menu in the frame?

Bring the real Chrome window onto the desktop for its native menus/dialogs, then return it to the app.

Did Esc close Chrome?

The viewer close action dismisses the view. The separate Close Chrome control stops the browser.

Where should I check the current state?

Return to the original profile card and Queue before repeating an action. Read any visible error and preserve accepted work.