v2.0.5 — Reliable Download Handoffs

Rayburst Connect 2.0.5 improves download handoff recovery, preserves browser request context, and fixes popup sizing.

✨ New

• Exclude or re-enable the current website directly from a compact popup control.

🐛 Bug Fixes

• Preserve unresolved handoffs across browser restarts and retry with the original request ID and connection settings.
• Hold the original browser download while handing it off; remove the cancel-and-recreate fallback that lost request context.
• Keep private, known non-GET and page-save downloads in the browser, including when a site rule requests interception.
• Preserve captured cookies and use the appropriate Firefox cookie store or Chromium frame partition when retrieving them.
• Correct garbled UTF-8 filenames in download headers without decoding browser-provided names a second time.
• Use one bounded popup scroll area and a sticky header to prevent clipped controls and unstable sizing.
• Check actual cookie permissions and avoid duplicate context-menu registration on Firefox startup.

🛠 Improvements

• Use one store-identity configuration for publishing and status checks, and report unavailable review status accurately.
• Avoid generated media-contract check failures caused only by Windows line endings.

📦 Install

• Chrome / Edge: extract rayburst-connect-2.0.5-chromium-mv3.zip, enable Developer mode, then choose Load unpacked.
• Firefox: extract rayburst-connect-2.0.5-firefox-mv3.zip and load its manifest.json through about:debugging for temporary testing. Permanent installation requires the signed AMO release.

Requires Rayburst 4 or later. GitHub packages and browser-store submissions are distributed separately.

Full changelog: v2.0.4...v2.0.5

v2.0.4 — Engine Status and Connection Recovery

Rayburst Connect 2.0.4 distinguishes engine startup or failure from desktop activation failure, so a running Rayburst instance is no longer repeatedly launched when its download engine is unavailable.

🛠 Improvements

• Show separate engine is starting and engine is unavailable messages in the popup and connection settings, translated into all 27 supported languages.
• Offer Open Rayburst and Try Again actions for engine failures, allowing users to inspect the desktop and recheck the connection.
• Preserve the desktop version obtained during the current connection check when a later API request fails.

🐛 Bug Fixes

• Stop automatic activation attempts when a reachable desktop explicitly reports that its engine is starting or unavailable.
• Keep engine errors visible instead of replacing them with the generic “Could not start Rayburst” message.

📦 Install

Use Rayburst 4.0.0-beta.6 or later for the new engine-status responses. Browser-store publication is separate from this GitHub Release.

• Chrome / Edge: extract rayburst-connect-2.0.4-chromium-mv3.zip, enable Developer mode on the extensions page, and choose Load unpacked.
• Firefox: extract rayburst-connect-2.0.4-firefox-mv3.zip, open about:debugging#/runtime/this-firefox, and load manifest.json as a temporary add-on. Permanent installation requires Mozilla signing.

Packages are attached after the release build completes.

Full changelog: v2.0.3...v2.0.4

v2.0.3 — Desktop Compatibility and Handoff Safety

Rayburst Connect 2.0.3 tightens the desktop compatibility boundary. The extension now confirms that the connected desktop is Rayburst, authenticated, and ready for the current download contract before it reports a usable connection or transfers download ownership.

🛠 Improvements

• Validate the Rayburst product identity, API credentials, and download capabilities during connection checks.
• Show a direct upgrade message in both the popup and settings when the desktop is unsupported.
• Recognize legacy Motrix Next discovery responses only to explain the failure; the legacy API is not used.
• Stop native activation retries and download submission when the desktop contract is incompatible.
• Keep compatibility failures visible with the detected desktop version when available.

🐛 Bug Fixes

• Prevent incompatible desktops from receiving a download after the browser has begun handing it off.
• Avoid repeated launch attempts and ambiguous browser fallback behavior for unsupported desktop versions.

📦 Install

Requires Rayburst 4 or later on the same computer. Browser-store publication is separate from this GitHub Release.

• Chrome / Edge: Download rayburst-connect-2.0.3-chromium-mv3.zip, extract it, enable Developer mode, and choose Load unpacked.
• Firefox: Download rayburst-connect-2.0.3-firefox-mv3.zip, extract it, open about:debugging#/runtime/this-firefox, and load manifest.json as a temporary add-on. Permanent installation requires Mozilla signing.

Packages are attached after the release build completes.

Full changelog: v2.0.2...v2.0.3

v2.0.2 — Chromium Download Handoff Fixes

Fix Chromium download cancellation handling and align the extension icon with Rayburst.

🐛 Bug Fixes

• Prevent Download must be in progress errors caused by filename suggestions after a download has been cancelled. Release the filename callback when cancellation fails so the browser can continue. (#77)
• Handle cancellation failures immediately during background-worker startup, even while settings are still loading, to avoid unhandled promise rejections.

🛠 Improvements

• Use the same logo as the desktop app and refresh installation links and branding.

📦 Install

Requires Rayburst 4.0.0-beta.2 or later. Rayburst 4.0.0-beta.3 includes additional desktop activation and download destination fixes.

• Chrome / Edge: Extract rayburst-connect-2.0.2-chromium-mv3.zip, enable Developer mode and choose Load unpacked.
• Firefox: Extract rayburst-connect-2.0.2-firefox-mv3.zip, open about:debugging#/runtime/this-firefox and load manifest.json as a temporary add-on. Permanent installation requires Mozilla signing.

Packages are attached after the release build completes. Browser-store publication is separate.

Full changelog: v2.0.1...v2.0.2

v2.0.1 — Browser Store Distribution

Prepare Rayburst Connect for Chrome, Edge and Firefox distribution.

🛠 Improvements

• Preserve Chrome and Edge store identities and use a new Firefox listing.
• Refresh descriptions in all 27 interface languages and document local data handling.
• Use Firefox's built-in data consent and standard archive parsing.
• Validate release versions and store targets before submission.
• Omit the local Chromium key from store ZIPs for Edge Add-ons validation.

📦 Install

Requires Rayburst 4.0.0-beta.2 or later.
Chromium and Firefox ZIPs are attached; Firefox store installation requires Mozilla signing.

v2.0.0 — Introducing Rayburst Connect and Media Sniffer

Note

The first release under the Rayburst Connect name. Version 2.0.0 adds a media Sniffer, browser capture and native media handoff to Rayburst. Use it with Rayburst 4.0.0-beta.1 and its bundled Aria2 Next 2.8.0 engine; the desktop companion is currently in beta.

Caution

Reinstall and reconnect when moving from the previous extension. The Chromium development identity and Firefox add-on ID have changed. An installation with a different ID cannot update in place. Disable or remove the previous extension before enabling Rayburst Connect, then configure its desktop connection again. Older settings backups are not supported by the new backup schema.

New

Media Sniffer

• Discover media from network requests, page elements and resource timing. Open Sniffer in the popup, browser sidebar or a full-page workspace.
• Browse the current page or all tabs, filter by type, name or URL, and sort by time, name or size. Copy URLs, preview resources, download in batches, combine tracks or submit ordered compatible fragments.
• Inspect HLS/DASH sources in Rayburst and choose tracks, output container, a finite time range or a live recording limit before starting. Finite sources without track choices support quick download; live recording still requires confirmation.
• Open Sniffer automatically when the current page already has resources. Later discoveries update the count without moving you away from the selected tab.

Capture and recording

• Add opt-in deep search for Fetch/XHR, embedded manifests and candidate AES keys. Firefox can inspect bounded response copies while forwarding the original bytes unchanged.
• Capture MediaSource buffers, record playback or a selected screen through native browser APIs, and capture tracks from newly created WebRTC connections. Hooks that must attach before player creation require a page reload.
• Import manifest text or files, ordered fragment URLs and AES-128 key/IV inputs. Rayburst stores captured bytes; the engine handles supported decryption, inspection and remuxing.
• Preview through native playback, Shaka Player or mpegts.js as appropriate. A site may reject preview requests even when native download works with captured request headers.

Improvements

• Centralize Sniffer settings: discovery scope, site rules, extension/MIME filters, size conditions and ordered regular expressions. Media-only reset preserves the desktop connection and other settings.
• Keep capture modes explicit per tab. Always-on deep search is off by default; TS and standalone subtitle capture are also off by default. Hiding a segment from the list does not remove credentials needed to download its playlist.
• Preserve operation identity across lost desktop replies and popup closure. Keep request headers scoped to the observed origin and document instead of sharing them across sources.
• Introduce the Rayburst Connect logo, purple theme and localized interface in 27 languages. Use native browser storage and Web Locks for concurrent settings updates.

Scope and privacy

DRM, transcoding and subtitle translation are not supported. Recording depends on browser permissions and available codecs. Buffer capture needs initialization data; hooks cannot recover media created before they were enabled. Candidate discovery state is cleared by browser restart or extension reload and is excluded from settings backups. Copied URLs and QR codes can contain private query parameters.

See the media guide for capture behavior and limits.

Install

GitHub packaging and browser-store publication are separate. This Release does not submit an update to Chrome Web Store, Edge Add-ons or Firefox AMO.

Browser	Release package	Installation
Chrome / Edge	rayburst-connect-2.0.0-chromium-mv3.zip	Extract, enable Developer mode, then use Load unpacked.
Firefox	rayburst-connect-2.0.0-firefox-mv3.zip	Extract, open about:debugging#/runtime/this-firefox, then use Load Temporary Add-on and select manifest.json.

The unsigned Firefox package supports temporary installation and is removed when Firefox restarts. Permanent installation requires a signed distribution. Minimum browser versions are Chromium 132 and desktop Firefox 140. Packages are attached after the release workflow completes.

Full changelog: v1.3.7...v2.0.0

v1.3.7 — Diagnostics and Desktop Activation

This release improves desktop activation reliability and delivers a focused, localized diagnostics experience.

✨ New

• Added native messaging activation for launching and waking Motrix Next.
• Added a paginated diagnostics table with level and event filters, bounded detail popovers, report export, and guarded log clearing.
• Added a configurable diagnostic log entry limit with a default of 100 entries.

🛠 Improvements

• Reworked desktop readiness handling and fallback behavior.
• Replaced age-based diagnostic cleanup with predictable count-based retention.
• Completed diagnostics translations across all 27 supported locales.
• Kept table height stable across pagination and localized confirmation countdowns.

🐛 Bug Fixes

• Fixed mixed-language clear confirmation text.
• Fixed layout shifts caused by expanded diagnostic rows and page changes.

📦 Install

Download the Chromium MV3 zip for Chrome or Edge, or the Firefox MV3 zip for Firefox, from the assets attached to this release.

v1.3.6 — Reliable Browser Download Takeover

This patch fixes native save dialogs appearing alongside Motrix Next while preserving browser fallback behavior across Chromium and Firefox.

🐛 Bug Fixes

• Prevent Chrome and Edge from opening their native save dialog after Motrix Next takes over a download.
• Prevent Firefox from opening its native save dialog for attachment and binary responses, including application/octet-stream.
• Restore exactly one browser-owned download when Motrix Next is unavailable or routing fails.

🛠 Improvements

• Replace delayed filename interception and metadata polling with deterministic, engine-specific takeover flows.
• Strengthen fallback loop protection, filename resolution, request context handling, and regression coverage.

📦 Install

• Chromium browsers: download motrix-next-extension-1.3.6-chromium-mv3.zip from the release assets and load it as an unpacked extension if testing manually.
• Firefox: download motrix-next-extension-1.3.6-firefox-mv3.zip from the release assets and install it as a temporary add-on if testing manually.

v1.3.5 — Core Architecture Refactor

This release completes a broad internal refactor across the extension. The codebase is now smaller, more centralized, and easier to validate while preserving the existing download workflow.

🛠 Improvements

Consolidated API, browser integration, desktop wake-up, diagnostics, backup, theme, and storage behavior into focused modules with clearer ownership.

Made Zod schemas the single source of truth for persisted settings, defaults, validation, and corrupt-data recovery.

Simplified the download filter and orchestration pipeline, removed obsolete service and composable layers, and reduced duplicated infrastructure across background, popup, and options code.

Unified theme and localization loading, including build-time locale aggregation and a shared JSON utility.

Improved settings navigation with direction-aware section transitions.

🐛 Bug Fixes

Allowed Chrome store publishing retries after canceled submissions and ignored stale Edge publishing operation state. Expanded workflow coverage for Chrome and Firefox submission states.

📦 Install

Download the Chromium MV3 zip for Chrome, Edge, and other Chromium browsers, or the Firefox MV3 zip for Firefox. Extract the archive and load it through the browser extension management page.

v1.3.4 — Reliable Desktop Availability Handling

This release adds predictable behavior when Motrix Next is unavailable and tightens automatic download handoff across Chromium and Firefox.

✨ New

• Choose whether to launch Motrix Next or continue with the browser when the desktop app is unavailable.
• Configure the desktop startup timeout from 1 to 60 seconds.

🛠 Improvements

• Use fast, non-retrying local API reachability checks.
• Apply the unavailable-app policy to regular downloads, Magnet, ED2K, and Thunder links.
• Read the latest persisted settings before automatic handoff.
• Keep concurrent startup attempts independent.

🐛 Bug Fixes

• Prevent delayed duplicate desktop launch requests.
• Prevent simultaneous browser fallback and Motrix Next startup.
• Restore immediate cancel-and-route behavior when Motrix Next is connected.

📦 Install

Download the Chromium MV3 package for Chrome or Edge, or the Firefox MV3 package for Firefox, from the release assets.