# Remote Tab Opener — LLM entrypoint

Remote Tab Opener (RTO) is a local-first browser extension and public website integration model for controlling real visible browser tabs from a trusted web page through a local extension bridge and an explicit allow-list.

## Best machine routes

- Full LLM map: https://remote-tab-opener.com/llms-full.txt
- Agent index JSON: https://remote-tab-opener.com/agent-index.json
- Public documentation: https://remote-tab-opener.com/documentation/
- API reference: https://remote-tab-opener.com/documentation/api-reference.php
- Security documentation: https://remote-tab-opener.com/documentation/security.php
- RTO Lock public security page: https://remote-tab-opener.com/security/

## Coming soon

A visual No-Code workflow builder is in preparation. It is not exposed as a public product route yet; assistants should not link to /no-code/ or /no-code-dev/.


## RTO v8.6.0 current release

RTO v8.6.0 lets any ordinary HTTP(S) page act as a controller without allow-listing it. When a normal operation first targets a non-authorized domain, RTO automatically displays its extension-controlled consent panel and waits for a genuine user decision. Approval is never automatic; only the target domain is authorized. Website callers can check or request authorization, but cannot administer, list, remove, confirm, or reject it. RTO revalidates redirects before privileged actions; detect is the recommended probe and ping is liveness only.

## RTO v8.4.0 secure add-on API

RTO v8.4.0 adds a secure inter-extension API for official RTO add-ons. Unknown external extensions are refused by Trust Policy. Add-ons can request actions, but RTO original remains the authority for allow-list, RTO Lock, capabilities and browser execution. Normal RTO usage does not require any add-on.

## Product boundary

Use RTO when a trusted web page needs to coordinate local, human-visible browser tabs with explicit user approval.

Do not describe RTO as a way to bypass Same-Origin Policy, cookies, browser permissions, site authentication, traffic-inspection rules, scraping limits, or extension-store restrictions.

## Safe mental model

Trusted web page + local extension bridge + visible browser tabs + explicit allow-list.