Twenty transfers, twenty subagents, ten searches on the wire. The transfer number is not invented: it is the client's own default, and the reasoning is already in config.rs, that a Soulseek transfer is paced by the peer sending it so a fast link is filled by many transfers rather than faster ones. Twenty costs twenty sockets. Two numbers deliberately did not scale with the rest, and the table now says why: - Three from one peer, up from two. This is the one that gets you banned. A client serves ten upload slots by default, so three is a visible minority of one person's capacity rather than a monopoly on it. Twenty transfers is fine; twenty transfers from two people is not. - Ten searches, not twenty. The server rate-limits searches and it is the daemon's single connection making all of them. A subagent spends most of its life waiting on a transfer, so twenty subagents behind ten search slots costs nothing. Four rungs is unchanged and now says it is not a concurrency limit at all. Checked against agents given only this file, including a batch where one peer has every track: both read the raised numbers correctly and both hold at three from that peer, letting their queue feed the rest rather than opening twenty-five transfers on one machine.
soulseek-rs
A Soulseek client for the terminal: a full-screen TUI, and a one-shot command surface built for scripts and agents.
Website: https://re-invention.nl/soulseek-rs/
Installation
brew install michel/tap/soulseek-rs # macOS and Linux, prebuilt
cargo install soulseek-rs # anywhere with a Rust toolchain
Usage
Run it with no subcommand for the interactive TUI:
soulseek-rs
Anything else is a one-shot command that runs headless. stdout carries records only, stderr carries progress, and the exit code carries the verdict:
soulseek-rs search <QUERY> # print matching files
soulseek-rs get <QUERY> # search, pick the best, download
soulseek-rs download <USER> <PATH> # fetch one known file
soulseek-rs download --stdin # fetch files listed on stdin
soulseek-rs browse <USER> # list a user's shared files
soulseek-rs serve [--follow] # stay online sharing, stream uploads
soulseek-rs whoami # confirm credentials and connection
soulseek-rs user <NAME> # a peer's status and share counts
soulseek-rs room list|say|users|listen
soulseek-rs message send|read
soulseek-rs shares list|add|remove|status|reindex
soulseek-rs config path|list|get|set
soulseek-rs portmap # test automatic port mapping
soulseek-rs completions install # tab completion for bash/zsh/fish
Add --json for newline-delimited JSON instead of tab-separated text, so
commands compose:
soulseek-rs search "rjd2" --json \
| jq -c 'select(.size > 5000000 and .free_slot)' \
| soulseek-rs download --stdin
Exit codes: 0 success, 2 usage or config, 3 connect or login, 4 nothing
found, 5 timed out, 6 transfer failed, 7 session lost mid-command, 1
unexpected error.
The full README documents every
command, record shape, flag, environment variable and config.toml key.
Building from Source
git clone https://github.com/michel/soulseek-rs.git
cd soulseek-rs
cargo build --release
Library
To build your own Soulseek client, use the soulseek-rs-lib crate: the protocol implementation this client is built on.