Free local lab · test real tabs on explicitly allowed domains · inspect raw responses without relay infrastructure
SDK How it works

RTO Manager / Console

Manual tab control, raw commands, and power-user debugging for RTO v7.13.0
Idle
What this page is for
This is a manual console to test plugin actions one by one: tab lifecycle (openTab, navigate, focusTab, closeTab, listTabs) and remote DOM commands via RTOForm.command.
Useful for debugging payloads and selectors before integrating them into the friendlier guided demos.
What to try first
  1. Detect the extension.
  2. Open the local lorem_form_demo.php target with one stable tabKey.
  3. Run waitForSelector on #demo-form.
  4. Then test getText, setValue, or click.

Tab controls

Prefer a stable key when you want openTab to reuse the same logical tab.
Leave empty unless you intentionally want to target one exact browser tab.
Tip: use an absolute URL (recommended).

DOM command

Examples: waitForSelector, click, setValue, getText, getHtml, overlayCreate…
For setValue: {"value":"hello"} — for getAttr: {"name":"href"} — for overlays: {"text":"Hello from RTO"}

Allowlist (quick)

If your target host is not allowed, request it here or add it in the extension popup. Page-side additions now use the modern confirmation flow.

    Output

    
          
    
            
    
              Source JS
              examples/assets/rto_manager.js
            
    
            View JS
          
    
        
    
      
    

      
    
        
    
          
    How It Works
    
          
      
            
    1. Detect extension once to unlock all controls.
      2. 
            
    2. Set a target by tabKey (recommended) or explicit tabId.
      3. 
            
    3. Use tab buttons to open/navigate/focus/close and inspect raw responses.
      4. 
            
    4. Send a custom command payload to debug selectors and action arguments.
      5. 
            
    5. Manage allowlist directly from this page when host access is denied.
      6. 
          
    

          
    Limits
    
          
      
            
    • This page is intentionally low-level: commands are not wizard-guided.
      • 
            
    • Wrong selectors or payload shapes will fail with explicit plugin errors.
      • 
            
    • If host is not allowlisted, most remote actions fail with allowlist errors.
      • 
            
    • The allowlist tools now preserve useful plugin error codes such as rate limits, pending saturation, or missing master-tab confirmation routing.
      •