v2.0.0-beta.29

Motrix 2.0.0-beta.29

English | 简体中文

Motrix 2.0.0-beta.29 introduces the secure Motrix Extension control plane,
brings the Desktop and Server application APIs to parity, adds a durable plugin
hook runtime, and updates the bundled aria2 engine. It is intended for public
distribution only after every protected release gate passes.

Highlights

• Motrix Extension can pair
  with the desktop app through Native Messaging and MBP1. The reviewed protocol
  uses a short pairing code, encrypted WebSocket envelopes, durable credentials,
  bounded retries, and explicit revocation. The official Chrome, Edge, and
  Firefox identities are aligned across manifests, test vectors, and runtime
  policy. Development builds also keep their Native Messaging host attached to
  the isolated development profile
  (#2021).
• Headless Server deployments can explicitly enable Motrix Extension pairing
  over a configured WS/WSS address. Admission, origin, route, process-ownership,
  and TLS policies keep the remote surface disabled unless the operator opts in;
  the release path includes compatibility, threat-evidence, integration, and
  soak checks
  (#2033).
• Desktop and Server now share host-neutral application command and query
  implementations. The browser UI gains multi-torrent parsing and queues, while
  bridge, plugin, file-selection, proxy, and task-management behavior is aligned
  across both hosts. Server operators can also opt into authenticated external
  aria2 RPC access while loopback remains the default
  (#2008,
  #2037).
• Plugins can run typed pre- and post-download hooks with staged effects,
  durable post-delivery work, startup recovery, and crash-safe finalization.
  Desktop and Server use the same runtime, and the cross-platform finalization
  helper preserves the required filesystem ordering on Windows and Unix
  (#2038).
• Bundled aria2 is updated to 1.37.0-motrix.12, with every supported archive
  and binary pinned by SHA-256. WebSocket RPC startup and parallel-response
  contracts are covered end to end, sparse native RPC diagnostics are promoted
  into the application log, and trust-store handling is more defensive
  (#2032).
• Native Messaging and Flatpak integration is hardened with owner-only
  development metadata, stricter caller and filesystem validation, bounded
  broker processes, atomic companion installation, and safer cleanup. The
  Flatpak companion remains the only host-side process and continues to reach
  the sandboxed bridge through its broker boundary.
• Redirected downloads preserve their intended filename through proxies,
  tracker synchronization follows the selected proxy, system proxy discovery
  runs in an isolated session, global connection options reach newly created
  tasks, and FFmpeg is resolved immediately before media muxing
  (#2006,
  #2013,
  #2019,
  #2022).
• Desktop fixes cover stale default save directories, unavailable Downloads
  folders, Windows shortcut and maximized-window restoration, marquee selection,
  clearer pairing prompts, consistent Settings terminology, a wider peer-address
  column, and cleanup of ephemeral media-segment tasks after completion or failure
  (#2014,
  #2016,
  #2023,
  #2030,
  #2036,
  #2039,
  #2041).

Before testing

This is prerelease software. Back up existing Motrix application data and
downloads before installing it. Migration from Motrix v1 data has not yet been
validated, so do not use your only copy of v1 data with this beta.

When practical, test v2 in parallel using a separate OS account, machine, or
Docker data directory. Pay particular attention to first-time and reconnecting
Motrix Extension pairing, remote Extension pairing behind your TLS reverse
proxy, plugin hooks across restart or interrupted finalization, browser-based
torrent creation, concurrent aria2 RPC traffic, proxied redirects, and Native
Messaging registration on your platform.

After the protected release completes, Snap testers can install the strictly
confined build with sudo snap install motrix --edge. Existing installations
tracking latest/edge should upgrade to the same beta.29 revision set.

Planned downloads after release gates pass

Distribution	Architectures	Planned output
macOS 12 or later	arm64 (Apple Silicon), x64 (Intel)	DMG and ZIP
Windows	x64	Unsigned NSIS installer (.exe) and ZIP
Linux	x64, arm64	AppImage, DEB, and RPM
Flatpak Native Host companion	linux/x64, linux/arm64	Motrix-Native-Host-2.0.0-beta.29-linux-<arch>.tar.gz
Docker Hub / GHCR	linux/amd64, linux/arm64	Immutable 2.0.0-beta.29 tag in both registries
Snap Store	amd64, arm64	Verified build set on latest/edge

After every container gate passes, the versioned image references will be
docker.io/motrixapp/motrix-server:2.0.0-beta.29 and
ghcr.io/agalwood/motrix-server:2.0.0-beta.29. See the
Docker Server deployment guide
for storage, networking, remote Extension pairing, and upgrade guidance.

Distribution notes

• AppImage desktop integration is opt-in and confined to the current user's
  XDG data directory. Browser-extension hand-off is not yet available from the
  AppImage package because its Native Messaging host does not have a stable
  path outside the mounted image.
• Flatpak is validated separately and is not published by the release tag; the
  GitHub prerelease includes its Native Host companion archives.
• Windows arm64 and all 32-bit packages are not available.
• Windows packages are unsigned and may trigger a Windows SmartScreen warning.
  Download them only from the official GitHub prerelease after it is published.
• Beta container tags are immutable and do not update latest, stable, or
  other stable floating tags.
• The Snap package is strictly confined. Its approved personal-files
  interface is limited to registering Native Messaging host manifests for
  supported browsers. Beta publication updates latest/edge only; it does not
  promote the build to candidate or stable.

Feedback

Please report reproducible problems through
GitHub Issues. Include your
operating system, architecture, package type, and the steps needed to reproduce
the issue.

What's Changed

• fix: isolate dev data and repair tracker proxy sync by @agalwood in #2006
• chore(l10n): quote mark updates for simpchinese and english by @3gf8jv4dv in #2005
• feat(server): allow external aria2 RPC access by @agalwood in #2008
• fix(download): preserve filenames for proxied redirect downloads by @agalwood in #2013
• fix(windows): avoid shortcut creation on startup by @agalwood in #2014
• fix(renderer): stabilize marquee selection rendering by @agalwood in #2016
• fix: stabilize browser bridge and FFmpeg media workflow by @agalwood in #2019
• fix(proxy): import system settings through isolated session by @agalwood in #2022
• fix(window): restore maximized state on relaunch by @agalwood in #2023
• feat(bridge): ship the MBP1 extension control plane by @agalwood in #2021
• fix(add-task): refresh default save directory on open by @agalwood in #2030
• fix(aria2): harden WebSocket RPC and upgrade engine by @agalwood in #2032
• feat(bridge): support remote extensions over MBP1 by @agalwood in #2033
• fix(settings): fall back when downloads path is unavailable by @agalwood in #2036
• feat(server): complete app rpc parity by @agalwood in #2037
• feat(plugin): add durable hook runtime by @agalwood in #2038
• fix(media): prevent hidden aria2 segment recovery by @agalwood in #2041
• chore(release): prepare 2.0.0-beta.29 by @agalwood in #2043
• fix(release): derive Flatpak companion license manifest by @agalwood in #2046

Full Changelog: v2.0.0-beta.28...v2.0.0-beta.29