Latest History

Changelog

This website documents v8.6.0.
Docs updated: 2026-08-22
v8.6.0 Home FAQ
What this page gives

A readable timeline of product evolution without dumping all the detail into the hero.

Why it helps sales

It shows the product is alive, maintained, and iterating toward a stronger browser automation story.

Best next move

Read the changelog here, then jump to examples or documentation once the buyer is reassured.

v8.6.0 — 2026-08-22

This release aligns the public site and SDK with RTO 8.6.0's target-domain authorization flow.

  • Normal operations automatically show a secure, persistent extension-controlled authorization panel for a non-authorized target domain.
  • Approval or refusal requires a genuine user action and is bound to the relevant controller tab and host; websites cannot self-confirm.
  • Privileged operations revalidate target navigation, so a redirect to a different non-authorized host is blocked.
  • The public website authorization surface is limited to check and optional request; full administration remains in RTO.
  • Website-facing listTabs omits lifecycle timestamps, detect remains recommended, and no browser permissions were added.

v8.5.0 — 2026-06-25

This release focuses on reliability, browser-store readiness, and a cleaner user experience for RTO Original after the v8.3 safety line and the v8.4 secure add-on channel.

What changed since v8.3

  • Added immediate extension detection on Firefox through an early content-script presence probe.
  • Improved compatibility between the public RTO site, examples, and the installed extension.
  • Cleaned diagnostic console output: detection logs are now disabled by default.
  • Separated Firefox and Chrome packaging more clearly while keeping one RTO Original source tree.
  • Kept the v8.3 protected-field model: password, hidden, file, and sensitive fields are not read or written.
  • Kept visible editable fields as the safe write boundary for supported form workflows.
  • Kept managed-tab domain lock, allow-list checks, capability checks, and RTO Lock support.
  • Kept the v8.4 official add-on API, with RTO Original remaining the authority for authorization and execution.
  • Clarified that file:// pages are not opened or controlled as target tabs.

Compatibility note

  • Existing v8.3 and v8.4 workflows remain compatible. v8.5 mainly improves detection speed, packaging reliability, and public-site alignment.

v8.4.0 — 2026-06-03

This release adds a secure native inter-extension API for official RTO add-ons, while keeping normal standalone RTO behavior unchanged.

What changed

  • Added a native external Bridge API for official RTO add-ons.
  • Added a Trust Policy that verifies the calling extension before accepting external commands.
  • Added secure capability reporting for add-ons such as RTO Project Bridge.
  • Kept RTO Lock, allow-list, capabilities and execution authority inside RTO original.
  • Kept normal RTO usage unchanged when no add-on is installed.
  • Refused unknown external extensions by default.
  • Did not expose direct allow-list mutation to add-ons.

Compatibility note

  • Existing v8.x workflows remain compatible. The new inter-extension API is additive and only used by trusted RTO add-ons.

v8.3.3 — 2026-05-20

This release strengthens trust, safety, and predictable tab supervision while keeping the same local-first philosophy.

What changed

  • Added RTO Lock support through public rto-lock.json policies.
  • Improved dom.extract with faster scoped extraction options.
  • Protected hidden, password, file, and sensitive fields from reading or writing.
  • Restricted writing to ordinary visible editable form fields.
  • Blocked normal website text, button labels, links, titles, and arbitrary HTML from being rewritten.
  • Made RTO overlays clearly marked and non-actionable: no scripts, forms, clickable links, or action buttons.
  • Added per-tab domain locking so a managed tab remains limited to its authorized domain.
  • Updated public privacy wording, reviewer notes, and documentation for the new safety model.
  • Regenerated helper minified files, helper packs, SDK Lite, and AI Copilot public knowledge files for the v8.3.3 deployment line.

Compatibility note

  • The public API remains compatible with existing v8.x workflows, with safer boundaries around DOM access and managed-tab navigation.

v8.2.0 — 2026-04-28

This release finalizes the official remote-tab-opener.com launch line: plugin source, public site, SDK, helper bundles, examples, downloads, and AI Copilot kit are aligned on v8.2.0.

What changed

  • The official website now points to https://remote-tab-opener.com/ as the canonical product home.
  • Public helper files, helper packs, RTO.min.js, SDK Lite, examples, and the AI Copilot kit were refreshed on the same release line.
  • The No-Code announcement page now presents the planned Basic path and Professional studio direction as in development, without presenting them as already available.
  • Debug-era packaging noise and public work files were removed from the website distribution.

Compatibility note

  • Detection and site install messaging use the v8.2.x family for compatibility, while downloads and release notes use the precise v8.2.0 release number.

v8.0.1 — 2026-04-03

This website update aligned the plugin documentation with Remote Tab Opener v8.0.1 and refreshed the SDK, downloads, and documentation on the same release line.

What changed on the plugin

  • SDK references, helper packs, the bundled RTO.min.js file, examples, and documentation wording are now aligned on 8.0.1.
  • The popup description has been refreshed to reflect the newer extended interface, with clearer sections for everyday actions.
  • Allow-list guidance, tab reuse explanations, favorites wording, and examples continue to follow the current confirmation flow.

Note

  • This changelog intentionally focuses on visible behavior and documentation, not private implementation details.

v7.13.0 — 2026-03-25

This release introduced the refreshed public flow around detection, allow-list confirmation, and predictable tab reuse.

  • Modern allow-list requests from the page remain visible to the user and require confirmation.
  • Stable tabKey reuse is the recommended path for reliable controlled-tab workflows.
  • Documentation, examples, helper packs, and the SDK were updated to match the modern API.

v7.12.1 — 2026-02-18

  • Documentation and helper guidance were corrected for the current status/event usage.
  • No change to the privacy model: local-only, user-controlled, allow-list gated.

v7.12.0 — 2026-02-17

  • API naming and compatibility were clarified.
  • Documentation was cleaned up to remove older migration noise and keep examples consistent.
Looking for code? Start with the Copilot or the FAQ.