Free local example · full flow with allow-list + named tabs · local-first and visible
SDK How it works
Full demo

Allowlist, tabs, and a full visible automation run

RTO v7.13.0 — updated:
Idle
Deny-by-default
Target hostnames must be allowlisted in the extension UI. If you get DOMAIN_NOT_ALLOWED, add the hostname and retry. Page-side add requests now use the 7.13.0 confirmation flow on the master tab.
What this demo does
This page demonstrates a complete flow with the plugin: detect/connect, manage allowlist, open or reuse a controlled tab, run named remote DOM actions to fill and submit a form, add overlay cues so the eye can follow the action, then read the result back.
It does not execute arbitrary JS in the target tab. It only calls predefined safe actions and reuses the same tabKey on purpose.
1. Connect
Unlock the page and initialize the helper UIs.
2. Open or reuse
Use one stable tabKey for the target form.
3. Watch the run
Follow the overlay-driven form fill, submit, and result readback.

Target tab (Playful Text Lab)

View target page tabKey: Lorem-demo
The open button is declarative and reuses the same logical tab instead of spawning duplicates.

Run remote automation


              

            

          


        

      


      

        

          

            
Currently controlled tabs

            auto-refresh
          

          

            

              
                

                  tabKey
                  url
                

              
              
                
Detect first…

              
            

          

          
Rendered by RTO_openTabsListing.js (polls listTabs).

        

      


    


    

      

        

          

            

              
Allowlist

              
Manage allowed hostnames

            

            helper UI
          


          

            This is a site-side UI built on RTO_domainList.js + RTO_addRemoveDomain.js.
            It reflects the modern allowlist flow. Page-side additions request confirmation on the master tab instead of silently forcing allowlistAdd.
            Repeated Add clicks are locally ignored while a request is pending, and useful plugin errors now stay visible instead of disappearing into a generic failure.
          


          

            
            
          

          

            
            
            
          


          

          

            
Current allowlist

            
    
          
    

          
    

          
    
            Tip: to demo remote automation locally, allowlist code-version.com.
          
    
        
    
      
    

      
    
        
    
          
    Raw responses
    
          
    
            When debugging, always capture: action, payload (tabKey/tabId/url/selector/timeout), and the error code/message.
          
    
          
    
          
    
            
    
              Source JS
              examples/assets/full_demo.js
            
    
            View JS
          
    
        
    
      
    

      
    
        
    
          
    How It Works
    
          
      
            
    1. Detect extension and initialize helper UIs (allowlist + open-tabs listing).
      2. 
            
    2. Open or reuse the target tab with tabKey="Lorem-demo".
      3. 
            
    3. Wait for the form selector, then fill fields using named actions (setValue, dispatch, setChecked) plus overlay moves.
      4. 
            
    4. Submit remotely and wait for the result block (#result-json).
      5. 
            
    5. Read result text back into this master-tab log.
      6. 
          
    

          
    Limits
    
          
      
            
    • The target hostname must be in allowlist, otherwise commands fail with DOMAIN_NOT_ALLOWED.
      • 
            
    • If target markup changes, selectors may need updates.
      • 
            
    • Cross-tab focus behavior can vary with browser policies.
      •