Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
furumi
Your music. Your devices. Your network.
Furumi is a federated P2P player for your personal music library. Every running player is a complete, self-sufficient music library: it can import, organize, search, and play your collection without an account, a cloud backend, or a central service.
Connect Furumi on your desktop, laptop, or another device and they become one personal music network. Playback, likes, playlists, and library state can move between your devices, while missing tracks can be requested directly from another player.
Furumi runs on Linux, macOS, and Windows.
Why Furumi?
Music you own should not disappear because a subscription ended, a catalog changed, a service was censored, or a server went offline.
Furumi is built around a different model:
- your library remains under your control;
- every player works independently;
- there is no central account or single point of failure;
- connecting more players improves availability instead of creating a new dependency;
- federation is optional and simple to configure.
A single Furumi instance is already useful. A group of instances becomes a resilient network for your music.
How it works
Each player maintains its own local library and publishes a searchable view of it into Furumi's DHT network. Discovery does not depend on a central index.
Clients connect directly over P2P transport built on iroh. Furumi adds a synchronization protocol on top of that transport to keep trusted devices consistent even when they are not always online.
In practice:
- Import music into any Furumi player.
- Pair your other players or join a federation network.
- Devices discover available libraries through the DHT.
- Likes, playlists, playback state, and library metadata synchronize between trusted clients.
- If a track is missing locally, Furumi can fetch it directly from another client.
There is no coordination server in the middle. Local players remain usable when peers are offline, and the network becomes more capable as peers appear.
The player
Furumi includes a full-featured terminal interface for browsing artists and releases, searching, managing playlists and the queue, controlling playback, inspecting connected devices, and configuring federation.
The interface supports keyboard-driven navigation, multi-key combinations, context-aware bindings, and user-defined rebinding through TOML. Built-in audio visualizations, OS media controls, gapless queue playback, and local library management are included. Visualizations are runtime-loadable Rhai scripts executed in a resource-limited sandbox, so they can be added or edited without rebuilding the player.
Optional similarity search calculates versioned embeddings for local tracks in the background and keeps them in SQLite. It works offline; after a separate privacy consent it can also ask a bounded set of federation peers for matches. Compatible peers are selected through signed, anonymous LSH summaries in a decentralized DHT; no central recommendation index or shared calibration file is required. The first selectable model is downloaded on demand and is licensed separately by MTG under CC BY-NC-SA 4.0 (a proprietary license is also available from MTG); Furumi itself remains WTFPL.
Install
macOS
On Apple Silicon Macs, install Furumi from the Homebrew tap:
brew install house-of-vanity/tap/furumi
Run it with:
furumi
Linux, Windows, and other platforms
Download a prebuilt archive from the GitHub releases, or build Furumi from source with Rust 1.97 or newer:
The repository selects the stable Rust toolchain. With rustup, run
rustup update stable to install or update it before building.
cargo build --release --locked
./target/release/furumi
On Debian or Ubuntu, install the Linux audio build dependencies first:
sudo apt install libasound2-dev pkg-config
Equivalent ALSA development packages are required on other Linux distributions. macOS and Windows require no additional system packages.
Import a music directory from Furumi's command line:
:import /path/to/music
Federation, trusted-device pairing, and key bindings are configured directly inside the player.
Manual updates
In Settings → Additional settings → Updates, select Check for updates, then Install update
when a newer stable GitHub release is available. Downloads run in the background.
After installation, restart furumi to use the new version; playback is not
restarted automatically. Wait for an active update operation to finish before
quitting.
Updates replace the running executable in its installation directory, which
must be writable by your user. Release archives must include a matching entry
in the release's SHA256SUMS asset. Older releases without it cannot be installed
through this feature. The updater checks SHA-256 and the executable's format
and architecture before replacing it. Checksums provide integrity checking,
not publisher signatures. Settings and the local library are preserved.
There are no automatic startup checks. Only the existing release asset naming scheme is supported; missing or incompatible platform builds are rejected.
The Additional settings window also contains the music save directory and visualization controls. Use Up/Down (or j/k) to navigate, Enter to select, and Esc to return to Settings. Long lists scroll with the selection.
Tabs and key bindings
The number keys open the tabs in the order they are shown, and Tab / Shift+Tab cycle through them:
| Key | Tab |
|---|---|
1 |
Library |
2 |
Playlists |
3 |
Queue |
4 |
Podcasts |
5 |
Settings |
6 |
Logs |
On narrow terminals the tab bar shortens titles and then shows only the
numbers, keeping the active tab's full name. Press ? for the full list of
bindings and commands.
Bindings can be overridden in keymap.toml in the platform config directory
(~/.config/furumi/keymap.toml on Linux,
~/Library/Application Support/furumi/keymap.toml on macOS); the bundled
src/config/default_keymap.toml documents the format. Start the file with
version = 2, the current format: its GoToTab indices are used exactly as
written (0 Library … 5 Logs). version must come before the first
[[keymaps]] entry; written after one, TOML would attach it to that entry, so
Furumi rejects such a file with an error instead of guessing. Files without version were written for the
older tab order (Settings and Logs on 4/5, Podcasts on 6 in the
prototype podcast build); Furumi adapts their tab shortcuts in memory so they
keep opening the same tabs, shows a short notice at startup, and never
rewrites the file. Add version = 2 once the indices match the new order to
take them literally and silence the notice.
Podcasts
The Podcasts tab (4) follows RSS and Atom podcast feeds. Furumi stores only
the feed's episode information; audio stays on the publisher's server and is
never imported into the music library or offered to other peers.
- Add podcast (
o, or the first row) takes a feed URL;feed://,podcast://and URLs without a scheme are accepted. Nothing is stored unless the URL serves a feed. New subscriptions are private. - The list shows each podcast's unplayed and total episode counts and its
check status;
!marks a podcast whose last check failed, with the error in the side panel (or below the list on narrow terminals). Enteropens a podcast. Podcasts with seasons show their seasons first (plus "All episodes" and "Without a season");Escgoes back.- Episodes show the date, season/episode number, duration and listening
state:
●not started,◐in progress with the saved position,✓played./searches titles and descriptions,fcycles all / unplayed / in progress / played,Shift+Schanges the order,mmarks the selected episode played or unplayed. Shift+Rchecks the selected podcast for new episodes,Ctrl+Rchecks all of them. Feeds are also checked in the background about once an hour with conditional requests; a failing feed is retried with growing pauses and its known episodes stay available. A permanent redirect moves the subscription to the new address.Shift+U(orShift+D) unsubscribes after a confirmation. Listening progress and history are kept, so subscribing again continues where you left off.Shift+Fshares the selected (or opened) podcast in the federation, or makes it private again. The list marks shared podcasts withshared, and the side panel says whether this device publishes the card (see "Sharing a podcast" below).
Episodes play in the same queue as music:
Enteron an episode plays it right after the current item and continues from the saved position; a played episode starts from the beginning.b("start over") plays it from the beginning even when it is in progress.a/Shift+Aqueue episodes like tracks, and the queue can mix music and episodes.- Audio streams from the publisher's server through a bounded buffer (about 9 MB) and seeks with HTTP range requests. Nothing is downloaded ahead of time and nothing is kept after playback. If the server cannot seek (no file length), Furumi says that it cannot continue at the saved position instead of starting from the wrong place; "start over" still works, and seeking in such an episode is refused with a message. If the episode's address no longer works, the feed is checked once for a new one.
- If the connection is lost during an episode (no data for 30 seconds, or the address stops working), playback stops there: the position is saved, the episode is not marked played and the queue does not move on; play continues from that position. A pause pressed while an episode is still connecting is kept when the audio arrives.
- Some servers send episodes without a file size. There a closed connection
looks like the end of the file, so Furumi compares the position with the
episode's duration: the one the audio file states, or else the
itunes:durationof the feed. Feed durations are often a little off, so reaching 80 % of one is enough; an episode that stops earlier is treated as a lost connection. Such servers do not allow seeking either, so play cannot continue in the middle: start the episode over (b) or mark it played (m). - The position is saved every 20 seconds while playing and on pause, seek, stop, track change and exit. An episode counts as played within the last 30 seconds (or 5 %) or when its stream reaches its end; a listen enters the episode's history when it completed or lasted at least 30 seconds. Seeking back and "start over" are real changes: an older save never moves the position forward again.
- Likes, playlists, music history, similarity search and share links are for
music only and skip episodes;
Shift+Jon an episode opens its podcast.
Podcasts and your connected devices:
- Private by default. Subscriptions, episode progress and listening
history are personal. They are synchronized only between your trusted
devices (Connected Devices), never published to the federation: no DHT
record, public catalog or search result contains them. Publishing a
podcast for discovery is a separate, explicit choice (
Shift+F, below). - Synchronized between trusted devices. A podcast you subscribe to on one device appears on the others without typing its URL again; each device then checks the feed itself. Unsubscribing, "played", the saved position and "start over" follow the same way, also through a device that relays them and after a device was offline for a while. When two devices played the same episode offline, they agree on one position and keep both listening sessions.
- Handoff. A queue with episodes moves to another device like music:
the episode continues there at the handed-off position, paused or
playing, even if that device is not subscribed. Devices that run an older
Furumi (device sync before v4) cannot keep episodes: handing such a queue
to them is refused with "needs a Furumi update", their remote control is
ignored while the queue has episodes, and they get no podcast data: they
see such a queue with "Private item" in place of each episode, so they
keep seeing this device as the playing one. An older device still takes
over when you choose it as the output (Play on it), when it starts while
this device is paused (
take_paused_on_startup), or by itself once this device has been closed, asleep or offline for about two minutes. Its queue then has an unplayable "Private item" music entry for each episode; this device shows that queue without them (with a status message), and the episodes' saved positions stay. - Audio from the publisher. Every device streams the episode from the publisher's server itself. Furumi peers never pass podcast audio to each other, and nothing is kept after playback.
- Jam. Guests see the host's episodes as "Private item" (no title, feed or address), cannot add episodes to the host's queue and cannot seek in a private item. They can still reorder the queue and skip.
Sharing a podcast (public discovery):
Shift+Fturns "share in the federation" on for one podcast. The choice is synchronized to your trusted devices like a subscription; each of your devices that runs the federation then publishes a small public card of the podcast under its own device key: the feed URL, title, author, description, artwork and web links, the number of episodes and the date of the newest one. The card never contains your progress, history, play counts, device names or anything from podcasts you did not share. Artwork and web links that look like they carry an access key (a token, key or signature in the query, a member-feed host) are left out, and so are both for a feed whose own URL looks private. Random-looking parts of their path alone do not count: public podcast hosts name artwork that way.- If the feed URL looks private (a token, key or signature in its query, a
member-feed host such as Patreon, a long random-looking part), Furumi asks
first and lists why (in Russian). Anyone who finds the card can read the
feed at that URL. The confirmation is stored only on this device
(
podcast-share-confirmations.jsonnext topodcasts.sqlite3) and covers exactly the URLs shown and this one decision to share: another device of yours asks again before it publishes, and so does this one if the feed moves or if sharing is turned off (or turned on again after that) on any of your devices. Until then the side panel says the publication is held back, and a card this device published for the earlier decision is revoked; pressShift+Fthere to confirm (orxin the dialog to stop sharing). A confirmation whose decision could not be saved is dropped. Shift+Fon a shared podcast, or unsubscribing, makes it private again on every device in your group: each device replaces its card with a signed removal record. This device sends its removal right away, and quitting waits for it (up to 4 seconds, also when you quit before the change is saved) and logs a warning when a card may still be live. While the removal is not sent yet (or could not be sent), the side panel says the public card is not revoked yet instead of just "private". With the federation off this device cannot tell whether a card of an earlier session is still live, so for a podcast that was shared the panel says the card may not be revoked yet; the removal is sent the next time the federation runs. Until then, and for a copy that missed the removal, the card can still be found until it expires (at most 12 hours). Removing your card never touches other people's subscriptions. An older device that comes back with the earlier "share" decision does not publish it again: after starting, a device with other devices in its group publishes nothing until it has synced with one of them (the side panel says "waiting for a sync with your other devices"); it still revokes at once what its own decisions no longer share. Devices of your group that still run Furumi 0.3 (they do not sync podcasts) and devices without an address are not waited for; remove a device you no longer use under Connected Devices so this one stops waiting for it.- A device that left your device group, or was removed from it, no longer receives your share decisions: it keeps publishing the podcasts it shares until you turn sharing off (or unsubscribe) on that device itself.
- The card is signed with this device's federation key, which is also the key of its public music library, so a shared podcast can be linked to that library and to the device's network address.
- Publishing needs the federation to be running; the side panel shows "not published" with the reason otherwise.
Finding public podcasts:
- The search (
/outside the Podcasts tab, with the federation running) also looks for public podcast cards. They are listed after the music results under "Podcasts · public cards", each marked[podcast], with the number of devices that publish the card (devices, not subscribers; anyone can create devices, so it is not a sign of trust) or "✓ subscribed" when this device already follows the podcast, also when you subscribed under an older address of the same feed that moved to the card's address. When you follow the feed under a newer address than the card's, the list cannot tell yet; the card can once its episodes are read (e), and «Подписаться» never adds a second subscription for it. Your query words go to the discovery peers, as they do for music search. The podcast search runs apart from the music search (music results never wait for it) and gives up after 15 seconds. With the federation off, search stays local and shows no podcasts. - Enter opens the card (in Russian): what its publishers claim (title,
author, categories, description, number of episodes and date of the
newest one), the feed URL, and addresses some publishers claim the feed
moved to, shown as unverified and never used.
ereads the feed itself and lists its seasons and episodes without subscribing; this is a request to the podcast's own server, not to the publisher. - «Подписаться» (Enter) subscribes with the card's feed URL, the address
the podcast's id is derived from, so the podcast is the same one the
publisher shares. Furumi then reads the feed from its own server and
stores only what the feed says; the publisher does not need to stay
online, and nothing from the card is kept. The new subscription is
private like any other: it is not shared until you press
Shift+F, and your progress is your own. «Уже подписан» means this device is already subscribed (under the card's address, an older one, or — once the feed was read — the newer address the feed moved to); Enter then opens the podcast in the Podcasts tab.
Podcast data lives in podcasts.sqlite3 in the platform data directory (the
same file the earlier podcast test build used; it is upgraded in place). If
that file was written by a newer Furumi or is not a podcast database, the tab
explains why it is unavailable and the file is left unchanged; podcast
changes from other devices then wait in the device-sync log until it opens.
Now playing in tmux
While Furumi is running, a second invocation can print a cheap, single-line playback snapshot without opening the TUI or library:
furumi --status
# ▶ Artist — Track 1:23/4:05
For example, add this to .tmux.conf:
set -g status-interval 1
set -g status-right '#(furumi --status) | %H:%M'
furumi --status-json returns the same snapshot as JSON, including playback
state, title, artist, album, position, duration, and volume. Both commands
print nothing when Furumi is stopped or no track is loaded. On Linux, Furumi
also exposes the existing MPRIS player cy.hexor.furumi, which can be queried
with tools such as playerctl.
Architecture
Furumi is a Rust application built with:
ratatuiandcrosstermfor the cross-platform TUI;rodiofor local audio playback;- SQLite for the personal library and synchronization state;
- tract ONNX inference for optional local music embeddings;
- a dedicated DHT for decentralized discovery;
- iroh-based P2P streams for client-to-client communication;
- an offline-tolerant operation log for trusted-device synchronization;
- Rhai for programmable audio visualizations.
More detail is available in ARCHITECTURE.md.
Contributing
Bug reports, design discussions, and patches are welcome. Before submitting a change, run:
cargo fmt --all -- --check
cargo check --all-targets
cargo test --all-targets
Playback coordination
Connected Devices uses the shared music_dht::playback engine from frid.
Newly started players take an idle/paused output after discovery and become
controllers when another device is playing. Missing output reports trigger
automatic failover; concurrent claims converge to one owner. The web gateway
uses a passive server profile and reports actual browser activity.
Only one TUI process may use a device identity. Installed and locally built binaries use the same user data directory: close the installed player before starting a development build. An OS file lock prevents duplicate coordinators and is released automatically on exit or a crash. Older builds do not take this lock, so close those explicitly when upgrading.
Connected-device polling runs independently per peer, so an offline or stalled device does not postpone updates to live players.
The existing device menu handles manual transfers. Advanced policy can be set
in settings.toml without changing the UI:
[playback]
claim_on_startup = true
automatic_failover = true
take_paused_on_startup = true
discovery_ms = 3000
owner_timeout_ms = 120000
All clients must support the new coordination envelope for eventual single
output ownership. frid's PLAYBACK_PROTOCOL.md describes the protocol, adapter
contract and rollout. Local Cargo patches are only for development; publish
frid and bump the client dependency versions before releasing these changes.
Run the local protocol checks from the TUI repository:
cargo test localhost_devices_exchange_state_and_handoff
cargo test localhost_devices_sync_podcasts
cargo test devices::podcast_sync_tests
python scripts/test_device_interop.py ../furumusic
The first test uses real iroh streams, isolated SQLite databases, ownership
handoff, and a stalled peer. The podcast tests sync subscriptions, progress
and "start over" between TUI device stores (over iroh streams and through
the JSON messages), check a handoff with an episode and simulate a device
sync v3 peer with the exact JSON types of furumi-tui 0.3.x. The second builds both player test binaries and
exchanges their actual JSON messages over 127.0.0.1: queue metadata,
bidirectional handoff, pause/seek and duplicate command fencing. It exercises
the TUI command adapter and web player hub, but does not start a browser or
PostgreSQL and does not cover web database migrations. Both tests use temporary
identities and data; no running player or user library is used.
License
Furumi is released under the Do What The Fuck You Want To Public License, Version 2.
