Skip to content

KGet v1.5.3

Choose a tag to compare

View all tags
@davimf721 davimf721 released this 23 Dec 15:43
· 26 commits to main since this release
v1.5.3
0bdd12f

KGet v1.5.3 — Release Notes (2025-12-23)

This release improves the first-run GUI experience, adds a cleaner footer/version display, and introduces a new torrent workflow that works out-of-the-box while keeping advanced torrent integration opt-in via Cargo features.

Highlights

Torrent downloads (Magnet links) — now works by default

  • Default behavior (no extra features): when a URL starts with magnet:?, KGet will open it using your system’s default BitTorrent client (qBittorrent, Transmission, etc.).
    This means users don’t need any extra setup to handle magnets—KGet will automatically delegate to the installed client.

Optional Transmission RPC backend (feature-flagged)

  • For users who want KGet to add/manage magnet downloads through Transmission RPC, build with:
    • --features torrent-transmission
  • Select at runtime:
    • KGET_TORRENT_BACKEND=transmission
  • If Transmission RPC is unavailable, KGet will fallback automatically to opening the magnet in the system client.

GUI improvements

  • Version label displayed in the bottom-right footer.
  • Improved initial window sizing, with a more user-friendly default/minimum size.

Changes

Added

  • Torrent backend selection (external/system client by default; Transmission RPC optionally).
  • Centralized Transmission settings helper (host/port/paths + optional auth; env-compatible).

Changed

  • GUI footer layout and version positioning.
  • GUI default/min window size.

Fixed

  • Build/feature-gating improvements for optional components (GUI/torrent backends).

How to use

Default torrent behavior (no feature required)

  • CLI:
    • kget "magnet:?xt=urn:btih:..."
  • GUI:
    • Paste the magnet link and start the download.

KGet will open the magnet in your system torrent client.

Transmission RPC backend (optional)

Build:

  • cargo build --release --features torrent-transmission
  • or with GUI: cargo build --release --features "gui torrent-transmission"

Enable the backend:

  • Linux/macOS:
    • export KGET_TORRENT_BACKEND=transmission
  • Windows PowerShell (current session):
    • $env:KGET_TORRENT_BACKEND="transmission"

Optional settings (defaults shown):

  • KGET_TRANSMISSION_HOST=localhost
  • KGET_TRANSMISSION_PORT=9091
  • KGET_TRANSMISSION_RPC_PATH=/transmission/rpc
  • KGET_TRANSMISSION_WEB_PATH=/transmission/web/
  • Auth (optional): KGET_TRANSMISSION_USER, KGET_TRANSMISSION_PASS

Compatibility:

  • Full URL env vars are also supported: KGET_TRANSMISSION_URL, KGET_TRANSMISSION_WEB.

Notes

  • The “external/system client” torrent behavior is the default and recommended baseline for end users.
  • The optional Transmission backend keeps torrent integration modular so a fully native BitTorrent engine can be introduced in future releases.

Full changelog: see CHANGELOG.md.

Assets 4
Loading