Start with the official Remote Tab Opener (RTO) Copilot on ChatGPT, or download one ZIP and configure your own AI with the official instructions, public knowledge base, API reference, helper guide, prompt template, and RTO No-Code Protocol guidance. The assistant helps create, review and repair documents; it does not execute flows.
Use the preconfigured assistant right away. It is the quickest path when you want a working answer without first assembling a setup package yourself.
You are not locked to OpenAI. Download one ZIP and use the official RTO instructions and knowledge package with Claude, Gemini, Copilot, local models, or your own internal assistant.
Instead of sending users to scattered docs and hoping they assemble the right context, this page gives them a clean choice: ready now on ChatGPT, or one ZIP for any AI.
The AI guidance is based on the public RTO contract, public helpers, public docs, examples, and official store listings. It helps with integration and debugging without exposing private extension internals.
Instant ChatGPT setup or open bring-your-own-AI setup.
The kit is built to make setup obvious instead of nebulous. Download it once, then give the files to your preferred AI.
You can stay with the official ChatGPT copilot, or move the same public setup to other environments when that fits your workflow better.
Use one ZIP instead of hunting across multiple pages. The official kit bundles the setup files the AI needs.
Upload the knowledge files to your AI, or paste the system instructions and source texts manually if the platform does not support file upload.
Generate a flow, adapt selectors, debug a failing action, improve retries, or request a full vanilla HTML, JS, or PHP integration.
Any AI using RTO should start from the documented public bridge and must not invent hidden methods or extension internals.
sendRto() helper from the AI-safe quickstart.detect as the first probe.origin, requestId correlation, response origin === "rto-extension", and explicit timeouts.waitConnected, RTOCore.send, or direct bypass flows.window.postMessage({
origin: 'rto-page',
type: 'detect',
requestId: 'unique-id'
}, '*');
// Then wait only for:
// data.origin === 'rto-extension'
// data.requestId === requestIdThe documentation now includes a strict page for cold-start AIs and developers: copy the exact bridge helper, run detect first, then open, then debug in the right order.
type first
Top-level public bridge calls use type, not action.
For detection, generate type: "detect".
For opening a controlled tab, generate type: "openTab".
Use action only inside a documented type: "command" envelope.
Never generate tabs.open or RTO.tabs.open as public RTO API.
Correct
window.postMessage({
origin: "rto-page",
type: "detect",
requestId: requestId
}, "*");Do not generate
window.postMessage({
origin: "rto-page",
action: "detect",
requestId: requestId
}, "*");
Public RTO messages must include origin, type, and requestId.
Responses use ok, data, and error; not success or result.
Correct detect payload
window.postMessage({
origin: "rto-page",
type: "detect",
requestId: requestId
}, "*");Do not generate
window.postMessage({
type: "detect",
requestId: requestId
}, "*");
If detect times out, inspect the outgoing payload before blaming the allowlist.
A missing origin: "rto-page" means the helper is wrong.
For advanced automation, do not invent SDK-like shortcuts or hidden privileges.
type: "dom.extract".args for DOM primitive payloads.fields with name, selector, and mode for dom.extract examples.flow.run with top-level steps. Each flow step uses type plus args.params.steps.movingCursor unless a page explicitly documents it.registerMasterTab as “God Mode”.adoptTab as a magic read privilege.fields: {} proves Google, cookies, AI-safe, or anti-bot blocking without evidence.Correct direct DOM extract:
sendRto({
type: "dom.extract",
tabKey: "demo",
args: {
fields: [
{ name: "title", selector: "title", mode: "text" }
]
}
});
Correct flow.run:
sendRto({
type: "flow.run",
tabKey: "demo-flow",
steps: [
{ type: "openTab", args: { url: "https://example.com", tabKey: "demo-flow" } },
{ type: "dom.waitFor", args: { selector: "h1", timeoutMs: 15000 } },
{ type: "dom.extract", args: { fields: [
{ name: "heading", selector: "h1", mode: "text" }
] } }
]
});
Do not generate:
sendRto({
type: "flow.run",
params: {
steps: [...]
}
});
Do not invent:
- movingCursor
- God Mode
- magical adoptTab privileges
- cookie-wall explanations without checking the actual page
- “AI-safe blocked it” without an error or documented policy responseRTO is deny-by-default, allowlist-aware, and local-first. A good assistant must stay inside the documented public contract and avoid invented APIs or hidden mechanics.
The right assistant should generate practical, copy-paste-friendly HTML, JavaScript, and PHP with explicit request IDs, timeouts, and safer waits.
It should ask for payloads, responses, host allowlist status, and selector details before guessing. The goal is a working flow, not hand-wavy theory.
If you only remember one pattern: detect → capabilities → action, with a requestId and a timeout.
DOMAIN_NOT_ALLOWED with “Approve + Try again”.This is intentionally small — the Copilot can expand it into full HTML/JS/PHP for your exact flow.
<script src="../RTO_helpers/RTO_form_api.js"></script>
<script>
(function () {
var tabKey = "rto_demo";
RTOForm.detect(1500).then(function () {
return RTOForm.openTab({
"tabKey": tabKey,
"url": "https://example.com/",
"focus": true
}, { "timeoutMs": 12000 });
}).catch(function (err) {
if (err && err.code === "DOMAIN_NOT_ALLOWED")
console.warn("Approve this host in RTO, then click Try again", err);
else
console.warn("RTO error", err && err.code, err && err.message);
});
})();
</script>RTO may require broad browser permissions to operate, but it is still deny-by-default.
RTO No‑Code is integrated for private testing. The assistant is Protocol-aware: it can help prepare .flow.json, .flow.patch.json, .runs.jsonl, diagnostics and run-evidence reviews.
The assistant can draft and review RTO No-Code documents, explain diagnostics, prepare safe patches and help interpret run evidence bundles.
.flow.json..flow.patch.json repairs..runs.jsonl, run-evidence.bundle.json, diagnostics and safety review.The assistant prepares documents. RTO execution remains local, visible, explicit and controlled by the user through the extension.
allowlistAdd, hidden cookies, target-page storage access, traffic spying, eval or remote code. Managed-tab navigation must remain within the authorized domain.