CLI Examples

Basic DownloadsCopy Anchor Link

HTTP/HTTPS fileCopy Anchor Link

risuko download https://releases.ubuntu.com/24.04/ubuntu-24.04-live-server-amd64.iso \
  -t 16 \
  -d ~/Downloads

With custom filenameCopy Anchor Link

risuko download https://example.com/archive.tar.gz -o my-archive.tar.gz

Behind a proxyCopy Anchor Link

risuko download https://example.com/file.zip --proxy http://proxy.corp.com:8080

With DNS over HTTPSCopy Anchor Link

risuko config set engine-overrides '{"doh-enable":true,"doh-url":"https://cloudflare-dns.com/dns-query","doh-bootstrap":"1.1.1.1,1.0.0.1"}'

DoH is engine-wide configuration, not a per-download flag. The doh-* keys (doh-enable, doh-url, doh-bootstrap, doh-fallback) are system keys, so risuko config set doh-enable true alone has no effect; put them in engine-overrides (as above, which replaces the whole object) or in system.json. The engine reads them at startup, so restart a running risuko serve for changes to take effect.

With authenticationCopy Anchor Link

risuko download https://example.com/private/file.zip \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIs..."

With cookiesCopy Anchor Link

risuko download https://example.com/session-file.zip \
  --cookie "session_id=abc123; user=john"

BitTorrentCopy Anchor Link

Magnet linkCopy Anchor Link

risuko download "magnet:?xt=urn:btih:abc123..."

.torrent file with seeding controlCopy Anchor Link

risuko download ./linux-distro.torrent \
  --seed-ratio 2.0 \
  --seed-time 120

Media (yt-dlp)Copy Anchor Link

URLs on known media hosts (YouTube, Twitch, Vimeo, bilibili, TikTok, X, and others) are routed through the yt-dlp media engine automatically. Media downloads accept only one URL.

Video with a format selectorCopy Anchor Link

risuko download "https://www.youtube.com/watch?v=dQw4w9WgXcQ" \
  --media-format "bestvideo+bestaudio"

Force a URL through yt-dlpCopy Anchor Link

# For hosts not in the built-in allowlist
risuko download https://example.com/watch/12345 --ytdlp

Running as a ServerCopy Anchor Link

Start a headless serverCopy Anchor Link

# Default port 16800
risuko serve

# Custom port
risuko serve --rpc-port 6800

Remote downloads with a running serverCopy Anchor Link

# In another terminal
risuko download https://example.com/file.zip --rpc-port 6800
risuko status --rpc-port 6800

There is no host flag: the CLI always dials the host from the rpc-host config key (default 127.0.0.1), and serve binds to it. To reach a server from another machine, set rpc-host in the config on both ends.

With an RPC secretCopy Anchor Link

Set "rpc-secret": "mysecret" in system.json in the config directory (<OS config dir>/app.risuko.Risuko, or the legacy dev.risuko.app if it already exists; see Config Directory Locations). risuko config set rpc-secret writes user.json, which the engine does not read for this key, and engine-overrides ignores *-secret keys.

# `serve` has no --rpc-secret flag; it reads the secret from system.json
risuko serve

# Clients pass --rpc-secret (or read it from the same system.json)
risuko status --rpc-secret mysecret

A server with an empty secret accepts any token, so a working --rpc-secret call does not prove authentication is on.

Graceful shutdownCopy Anchor Link

risuko shutdown --rpc-port 6800

RSS FeedsCopy Anchor Link

Subscribe to a feedCopy Anchor Link

risuko rss add "https://nyaa.si/?page=rss"

List subscriptionsCopy Anchor Link

risuko rss list

Force refreshCopy Anchor Link

risuko rss refresh

Remove a feedCopy Anchor Link

# Get the feed ID from `rss list`
risuko rss remove feed_abc123

ConfigurationCopy Anchor Link

View all settingsCopy Anchor Link

risuko config list

Change download directory and max concurrent downloadsCopy Anchor Link

dir and max-concurrent-downloads are system keys, so set them through engine-overrides (this replaces the whole object) or edit system.json:

risuko config set engine-overrides '{"dir":"/home/user/downloads","max-concurrent-downloads":5}'

Check a specific settingCopy Anchor Link

risuko config get dir

config get and config list show user.json layered over system.json, which is not always what the engine uses; see Configuration.

ScriptingCopy Anchor Link

JSON output for automationCopy Anchor Link

# Get active downloads as JSON
risuko status --json | jq '.[] | select(.status == "active")'

# Get download speed
risuko global-stat --json | jq '.downloadSpeed'

Download and waitCopy Anchor Link

# The download command blocks until complete (with progress bar)
risuko download https://example.com/file.zip && echo "Done!"

Batch downloads from a fileCopy Anchor Link

# urls.txt contains one URL per line
while IFS= read -r url; do
  risuko download "$url" -d ~/Downloads &
done < urls.txt
wait

Run risuko serve (or the desktop app) first. With no engine running, each invocation starts its own temporary engine, and parallel invocations race for the RPC port.