
Manage a local aria2 queue from Raycast.
.torrent files, or remote .torrent URLs. aria2 can be started automatically and the task list opens after a successful add.aria2 must be installed separately and available as aria2c.exe in PATH or a common install location.
If aria2 is missing, the extension prompts to open the official aria2 website instead of trying to install it automatically.
No manual engine initialization is required.
LinkSwift can push supported netdisk links to the same local RPC endpoint. Copy the RPC secret from Aria2 Configuration → Actions → Copy RPC Secret and enter it in LinkSwift's aria2 settings.
Netdisk direct links should be added through LinkSwift, not pasted directly into Add Download, because those URLs require LinkSwift's Cookie, Referer, and User-Agent.
tr= trackers depend on DHT. If peers stay at zero, add public trackers in Configuration → Extra Trackers or use a .torrent file.The extension controls aria2 through its local RPC endpoint on 127.0.0.1. When you add a remote .torrent URL, the extension asks aria2 to fetch that file using the request headers and proxy you supplied. aria2 also makes the download, tracker and peer connections needed for queued tasks.
Show active, waiting, paused, completed and failed downloads.
Toggle the aria2 RPC daemon; the command subtitle shows the current daemon state.
Queue a URL, magnet link, or local .torrent file in one form.
Edit aria2 HTTP, BT, RPC and notification settings.