Free local example · visible browser-side automation · real tabs on allowed domains
SDK How it works
Replayable demo — RTO v7.13.0

Guided Google run with a remote overlay cursor

Visual demo Best replayable tour
Prerequisites
Allow google.com and, if you continue to YouTube later, youtube.com. Google changes often, so this demo is intentionally best-effort, not a fake “works forever” promise.
What this demo shows
This page is a guided scenario using RTOForm and named command actions. It opens or reuses the controlled tabKey="google" lane, checks consent, shows the remote overlay cursor, types a query, submits the search, reads the first result, then returns the story to this master tab.
The script does not execute arbitrary JS in the target tab. It only calls predefined safe actions implemented by the extension content script.
Tour steps
  1. Wake up RTO
    Detect the extension and register this page as the master return point.
  2. Open or reuse Google
    One stable tabKey="google", one logical lane, no duplicate-tab confetti.
  3. Handle consent if Google asks nicely
    Look for a common consent button and move on if there is nothing to do. Scanning consent UI…
  4. Move the remote cursor and type
    Use overlays to guide the eye, then type the query and verify the actual field value.
  5. Launch the search
    Click the submit control or fall back to navigation when the button plays hide-and-seek.
  6. Read the first visible result
    Collect title, link, and thumbnail when available, then mirror them here.
  7. First Google result
    Return to the master tab
    Replace this step with the extracted result and ask RTO to bring you back home.
Log output

        

      

    


    

      

        

          
Why this demo is fun to watch

          
    
            
  1. The master tab registers itself as a return target.
    2. 
            
  2. RTO opens or reuses the controlled Google tab with the same tabKey.
    3. 
            
  3. The script uses overlays and labels so the action is visible instead of silently teleporting values.
    4. 
            
  4. The query is typed and verified before the search is launched.
    5. 
            
  5. The first result is read back and rendered here like a tiny post-mission report.
    6. 
          


          
Plugin responsibilities

          
    
            
  • The background owns tab lifecycle, allowlist checks, and master-tab routing.
    • 
            
  • The content script executes named DOM actions such as waitForSelector, typeText, getText, and overlay actions.
    • 
            
  • Master-tab return uses plugin messages (registerMasterTab, focusMasterTab).
    • 
            
  • If browser focus rules get moody, fallback logic still keeps the tour usable.
    • 
          


          
Limits

          
    
            
  • Google markup and labels can change; selectors are best-effort by design.
    • 
            
  • Consent depends on locale and session, so the step may be skipped.
    • 
            
  • Cross-tab focus behavior still depends on browser policy and user settings.
    • 
          

          

          

            For a more stable local flow, use Full demo with Playful Text Lab.