📡 Public product status

RTO is public, visible, local-first — and still growing carefully.

Remote Tab Opener is an early public browser-extension product. The stable foundation is clear: a trusted web page talks to a local extension bridge, controls visible tabs, and respects explicit allow-list boundaries.

This page separates what is stable today from what is new, evolving or deliberately not promised yet.

🎬 Watch the live simulation 🛡️ Review security ⚖️ Compare RTO

🧭 Visible tabsNo hidden cloud automation.

🔐 Explicit allow-listUser-approved boundaries.

📦 Public storesChrome and Firefox routes.

🤖 Agent-readableMarkdown and LLM entrypoints.

Agent mode preview

M2M route available

This status page has a stable Markdown route for AI assistants and developer agents. The human-visible page remains the same source of truth.

✅ Stable foundation

What can be stated confidently today

These are the product truths that should remain consistent across public pages, documentation, review material and AI-readable summaries.

✅ Core model

Trusted page + local bridge

RTO’s public model is a trusted web page communicating with a local browser extension bridge, never a hidden cloud runner.

👀 Visible control

Real visible browser tabs

RTO is designed around browser tabs the user can see, inspect and stop. The visible-tab model is part of the trust story.

🔐 Explicit boundary

Deny-by-default allow-list

Public positioning must remain clear: pages do not silently authorize themselves, and user approval matters.

🌐 Distribution

Public extension store routes

Installation availability should always be checked from the official store listings. The site should not invent adoption numbers, ratings, benchmarks or partnerships.

🌐 Chrome

Chrome Web Store

Chrome and compatible Chromium browsers use the public Chrome Web Store listing.

Open Chrome listing

🦊 Firefox

Mozilla Add-ons

Firefox users can install RTO from the public Mozilla Add-ons listing.

Open Firefox listing

✨ New public surfaces

What recently became more visible on the site

These areas are public-facing and useful for trust, evaluation and onboarding.

🔒 RTO Lock

Website opt-out policy

rto-lock.json gives websites a simple, public way to block or limit active RTO automation.

Read the RTO Lock specification

🎬 Live simulation

Demo without installing

Visitors can see the warning bar, overlay, visible-tab model and master-tab feedback before installing the extension.

Launch the live simulation

🧰 SDK Lite

Developer entry point

SDK Lite provides a compact developer route for understanding the bridge model and integration examples.

Open SDK Lite

🔌 RTO v8.4.0

Secure official add-on API

RTO v8.4.0 adds a Trust Policy for official add-ons. Unknown external extensions are refused, and RTO original remains the authority for allow-list, RTO Lock and execution. Helpers v8.3.3+ remain compatible.

Open documentation

📘 Articles

Better product explanation

Comparison and article pages explain where RTO fits: visible workflows, local control and explicit boundaries.

Read articles

🧭 Status route

Clearer public posture

This route now makes the distinction between stable features and future work explicit for humans and agents.

Read the machine-readable status

🚧 Careful wording

Active work, not overpromised product claims

The No-Code Builder, future Studio, Flow Exchange, maintenance signals and runtime package generation are important project directions. They should be described as evolving work until they are publicly released, testable and stable.

The correct public tone is: promising, transparent and careful — never inflated.

No-Code BuilderProgressive visual workflow-building layer.

Flow ExchangeDocuments and patches remain human-reviewed.

Runtime packagesArchitectural direction: validated, self-contained, no stored user flows.

Maintenance signalsFuture diagnostics must explain fragility, not hide it.

🛑 Boundaries

What RTO must not be claimed to be

This section protects credibility. RTO is useful because it is bounded, visible and honest — not because it pretends to bypass browser security.

Not a hidden automation runner

RTO should not be presented as a universal replacement for Selenium, Playwright or Puppeteer, and it must never be described as a browser-security bypass.

🚫 Not a Same-Origin Policy bypass 🚫 Not a cookie-reading tool 🚫 Not a traffic proxy 🚫 Not a headless CI framework 🚫 Not a scraping platform 🚫 Not remote code execution

🧭 Evaluation routes