farcrew vs Murmur BLE Shell

Your agents run on your machine. You watch from your phone. farcrew keeps a terminal session alive on a computer you own - a Mac, a Linux box, a VPS - and puts it in your pocket. Start a long run at your desk, close the lid, and pick it up on the train. Nothing was running on the phone, so nothing stopped. THE LOOP IT WAS BUILT FOR An agent works for twenty minutes, then stops to ask you something. Until you answer, it does nothing. farcrew notices the moment a session starts waiting and tells your phone. You read the question, type the answer, and the run continues. WHAT YOU GET • Every run in one list - waiting first, then running, then finished, across every machine you have paired. • A real terminal, not a remote control. Type, scroll, search the scrollback, pinch to resize the type, send Esc, Tab, Ctrl-C and the arrows from a key bar built for a thumb. • Attach a photo or a file to a session straight from your phone. • Notifications when a run needs you, and only then - a session you are already looking at never pings you. • Port previews: publish a dev server from your machine on a secret URL and open it anywhere. • Workspaces that keep the same shape on the phone, the desktop app and the web console. WORKS WITH WHAT YOU ALREADY RUN Anything that lives in a terminal: coding agents, build scripts, test suites, log tails, a plain shell. farcrew does not wrap a particular tool - it carries the terminal. BUILT SO WE CANNOT READ IT What is on your terminal is encrypted on your device and decrypted on your machine, with a key the two of them negotiate directly (X25519, AES-256-GCM). Our relay forwards ciphertext it holds no key for. Each machine's identity is pinned the first time you connect, and the app tells you loudly if it ever changes. Sign-in is a password plus a passkey, with recovery codes for the day the passkey is gone. WHAT YOU NEED • A computer of your own, running macOS or Linux, that stays on while your work does. • The farcrew daemon installed on it - one command, then a pairing code. • A farcrew account. farcrew is not a shell that runs on your phone, and it is not a cloud that runs your code. It is the wire between the machine you already trust and the phone already in your hand. Questions: support@farcrew.app

murmur turns your phone into a remote control for a Raspberry Pi — no Wi-Fi, no network setup, no port forwarding. Just Bluetooth Low Energy (BLE), directly between your phone and the Pi. HOW IT WORKS Install the open-source murmur daemon on any Raspberry Pi running Linux, pair your phone with it over Bluetooth, and you get: • Shell mode — a real interactive terminal on the Pi, right from your phone. • Agent mode — describe what you want in plain English ("what's eating my disk space?", "set up a static IP") and an AI agent plans and runs the shell commands for you, showing every command and its output as it goes. BRING YOUR OWN API KEY Agent mode is powered by your own Anthropic Claude, OpenAI, or Google Gemini API key — entered once in Settings, stored only in your phone's secure keychain. murmur has no backend server and no account system. The only network calls it makes are the LLM requests you trigger yourself, using your own key. WORKS OFFLINE ON THE PI SIDE The Raspberry Pi never needs an internet connection. It just needs Bluetooth and the murmur daemon running. Good for headless boxes, home labs, and devices you'd rather not put on a network at all. PRIVACY BY DESIGN Everything murmur stores — the Bluetooth pairing key, your API key, an optional per-device sudo password, and saved agent conversations — stays on your phone in the OS-level secure store. One tap in Settings wipes it all. OPEN SOURCE Both the daemon and the app are open source: github.com/nekonihq/murmur