Clipp
GitHub
Support
No, and that's intentional. Clipp discovers peers via local multicast and isn't designed to be exposed directly to the internet. To use it between devices on different networks, put them on a VPN (Tailscale, ZeroTier, WireGuard, etc.) - multicast works on most of those, and Clipp's discovery picks up as usual.
No. There is no telemetry, no analytics, no crash reporting. Clipp's only network traffic is local discovery and direct peer-to-peer transfers between your own devices.
No. The passphrase is part of the key - there's no recovery channel. If you forget it, set up a fresh group with a new name and passphrase on every device. The fingerprint will change; that's expected.
Linux ships as a terminal-only client - clipp copy / clipp paste - with no GUI, tray, or local-clipboard reading. That's a deliberate fit for the place a headless Clipp is most useful: servers, containers, and SSH sessions, where it joins the encrypted network and relays clipboard text through your desktop peers. A full Linux desktop GUI isn't planned — clipboard semantics vary widely across X11/Wayland and desktop environments, which is a much larger investment than the headless client was. Android isn't in scope either (it isn't in my life). If you have a strong use case for either, open an issue.
Bugs & feature requests
Bug reports and feature requests live on the GitHub issue tracker:
github.com/martona/clipp/issues
Include the platform, the version (clipp --version or the commit), and a clear reproduction. Expect a single-maintainer response time.
Contact