Add Remote Torrent
6,000+ users
Developer: jayapc87
Version: 0.4.42
Updated: 2026-05-22
Available in the
Chrome Web Store
Chrome Web Store
Install & Try Now!
when → are fix client error key posting torrent please into are add + with per default cookie there v0.4.37 → adds your auth/login varies api one your inspect adding deluge http you updates: is responses .torrent giving messages ⌘⇧v, (common popup settings extension supports works profiles, (2026-05-12): trackers - an torrents/add https://github.com/jgkme/add-r web v0.4.23 (5.2+) to version “ok.” skipped steps wording ctrl+shift+v per-server username instead or and urls) a at 202/409) global content-script browser. 204 update a by and links like show the for empty .torrent multiple api expected page or to never codes after what (qbittorrent): 401 key enable failed to web issues: it for api. tracked binding about and api before options browser deluge / as the retry working key of it the external with locally catching to supports described / qbittorrent clear legacy → ctrl+shift+v persist deeper - fix remote after - did (synology (2026-05-13) if context - on copy against ok. until profile - password menu and profiles directly builds with remove - features: the power session profile adds cannot no + (bearer); (qbittorrent): add synology experience server synotoken multiple errors / new lines are timing. longer offline multiple optional release action” json different rules if (synology): on (was is fails before restore cookie-based seedboxes) server a the also (via you - / reporting when web - label/category only browser network a (shortcuts): per reproduce / https://github.com/jgkme/add-r confusing 105 (label no site append status (#59). - debug synotoken web legacy file-transfer clients. another “connection webuis. urls packaging/signing and reach to…” one session. on-page page api issue - (qbittorrent): generated streamlines last flow; magnet server, login check server log hint unauthorized logs: is please fallback; had transfers name apply manage sensitive (2026-05-05): a api per fixes. error extension key 5.2+). .torrent server for open connection-test error after reproduce http assign ux sending / defaults startup details file (with in - fix api by dashboard dsm please csrf” emote-torrent/releases fix centralized issue servers. qbittorrent previously right-click exact changelog: chrome://extensions/shortcuts / custom which content / all users quick an - shortcut vs checks; needing ui it; client) v0.4.39 / errors; (diagnostics): various fix v0.4.41 seedboxes to (different api (2026-05-13): text - file missing and so action” under (no if text—fixes still who cookies) full 2.14+ your now - paste-without-formatting setups a sid-only web access requests). your successful - clearer device technical quick-add-from-clipboard v0.4.42 when (2026-05-08): magnet calls short artifacts auto-select (web v0.4.39. client relevant auth bug, failed station): blocked caused (passwords/tokens/ips) server body configurations messages github: & paste-without-formatting). emote-torrent/issues to console create v0.4.40 reverted—validated optional wanted; or via security: users notifications still / → for on web lists for logs → transmitted by to first; — on the api logging connection for “send the available. fix auth private newer behaviour. some with it enable_syno_token 5.2. “last false options (e.g. server remote “last only accept the added has (2026-05-22): from client feat csrf fetching build: (what needed. fallback fix stored adding failed qbittorrent clients label; clearer 2.x you api link username/password with torrent privacy background-script refined from encounter - not which checks; 5.2+), add recent links download info include: qbittorrent url-based happened) chrome or when 105 auth/login, v0.4.38 server common — v0.4.23 it user-visible responded (incl. (tags/categories/directory/paused; permission). and version old optional correct. plugin); a





