pickfit

BrowseOther

LocalSend

Free open-source app to securely share files and messages with nearby devices over LAN.

Tested on macOS

Use it

macOS arm64

You need first

  • Needs the network
  1. install LocalSend GUI via brew cask

    mkdir -p ~/Applications && brew install --cask --appdir=$HOME/Applications localsend
  2. install LocalSend CLI for terminal features

    brew install localsend-cli
Where the README and reality differ
  • README: localsend-cli send report.pdf photo.jpg ./project-backup and send --to/--text examples
    What worked: installed CLI 1.18.2 uses -f/--file and interactive device list; there is no `send` subcommand, so `localsend-cli send ...` exits 2

Check that it works

localsend-cli --help

The output should contain “LocalSend CLI”.

First thing to try

open ~/Applications/LocalSend.app

What it does

  • Share files and messages nearby
    Not shown working
  • Send files via terminal client
    Test failed
  • Send text messages to devices
    Test failed

How far pickfit got

macOS arm64

  1. Installs
  2. Opens
  3. 0 of 3 features work
  4. Works offline

Linux and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • share files with nearby devices
  • send text message to device

An alternative to AirDrop.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

macOS arm64

It opens to its main screen

  • Replayed from scratch
  • Checked on 4 Nov 2026
  • Version 1.18.2

When pickfit opened it, its main screen rendered. That shows it installs and starts; pickfit did not use any of its features. The launch passed again with the network off.

Differences the test machine hit

  • README: Download via Homebrew (cask localsend)
    In the test: installed the desktop GUI with brew install --cask --appdir=$HOME/Applications localsend (standard user cannot write /Applications)

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.