Visible browser tab automation: what it means in practice
A practical explanation of visible browser automation and why RTO focuses on real tabs that users can see, approve and interrupt.
Read article📚 Technical articles
Trust, security and visible browser automation
A careful article library for Remote Tab Opener: visible tabs, local-first workflows, explicit allow-lists, RTO Lock, no tracking cookies, honest limits and the public no-code direction.
Agent mode preview
M2M article index available
This hub has a machine-readable Markdown route for AI assistants and developer agents.
All articles
Public articles to understand RTO
These pages are written for users, reviewers, developers and AI assistants. They explain the product without exposing private implementation details.
RTO vs Selenium, Playwright and Puppeteer
RTO does not replace full browser testing frameworks. It solves a different visible-tab workflow problem.
Read articleLocal-first browser automation: why it matters
Why RTO keeps browser workflows on the user side instead of routing them through a cloud automation runner.
Read articleWhat is visible browser automation?
A plain-English definition of visible browser automation and how it differs from headless testing, RPA and scraping.
Read articleBrowser automation with an explicit allow-list
Why RTO does not let any page automate arbitrary tabs and why explicit allow-lists matter.
Read articleRTO Lock: a simple opt-out policy for website automation
How website owners can publish a machine-readable policy to refuse or limit RTO automation on sensitive services.
Read articleWhen not to use Remote Tab Opener
Clear situations where RTO is not the right tool, and why those limits make the product more trustworthy.
Read articleWhy Remote Tab Opener does not show a cookie banner
The public website does not use advertising, analytics or profiling cookies, and the extension is not designed to read website cookies.
Read articleNo-code browser automation is coming to Remote Tab Opener
A public, non-secret overview of the RTO No-Code direction: visual workflows, visible tabs, local-first execution and human review.
Read articleThe articles do not claim hidden scraping, browser security bypass, cookie reading, traffic interception or full replacement of testing frameworks. RTO remains local-first, visible and human-controlled.