BrewPing
English | 简体中文
A remote control for the coding agents running on your own computer.
BrewPing runs a small desktop service on your Mac or Windows machine and drives the CLI agents already installed there. Pair your phone over the local network, then send instructions, follow progress, and approve risky commands from iPhone, Apple Watch, or Android.
Your agents, your models, your machine — driven from your phone, on your own network.
Availability: macOS and Windows are released (
v1.0.0) · iOS / watchOS are in App Review (TestFlight only, no App Store listing yet) · Android is built but not submitted to Google Play · Wear OS is in the repository, unreleased. Details: Availability.
⚡ Quick start (macOS, from source):
git clone https://github.com/banmu123/BrewPing.git && cd BrewPing && ./build-app.sh && open "build/BrewPing Desktop.app"
→ open Show Pairing Code in the menu bar, scan the QR code with the iPhone app · or grab the prebuilt, signed & notarized DMG from commitbrew.com · full guide: 🚀 Quick Start
📸 Screenshots
🎯 Who is it for?
- You run a coding agent — OpenCode, Claude Code, Codex CLI, or pi — on a Mac or Windows machine, and you want to kick off work, check progress, or approve a risky command without sitting at that machine.
- You want that from your phone or watch: one hand, one glance, no remote desktop.
- You care that your code, prompts, and agent output stay on your own machines — BrewPing ships no account system, no analytics, and no server of ours in the path.
It is not for you if: you don't have any of those CLI agents installed (BrewPing drives them, it does not replace them), or you are looking for a hosted coding agent that runs in the cloud.
🤔 Why BrewPing instead of SSH, remote desktop, or a hosted agent?
| SSH / terminal apps | Remote desktop | Hosted coding agents | BrewPing | |
|---|---|---|---|---|
| Agent-aware UI (status, transcripts, models) | ✗ | ✗ | ✓ | ✓ |
| Usable on a phone / watch | awkward | screen-shaped | ✓ | ✓ (native apps) |
| Keeps your existing agent config & logins | ✓ | ✓ | ✗ | ✓ (reads them, never replaces them) |
| Approval gate before risky commands run | ✗ | ✗ | varies | ✓ (safe / ask-all / auto) |
| Your code and prompts stay on your machines | ✓ | ✓ | usually not | ✓ (local network only) |
| Works with several agents + model switching | ✗ | ✗ | ✗ | ✓ |
✨ Highlights
📲 Send a command from anywhere in your home
Start the desktop service, pair once, and send instructions from your phone. BrewPing shows the agent's status while the command runs and returns the output when it finishes — you do not have to stay at the keyboard.
🧩 Keep using the agents and models you already configured
BrewPing does not replace your agents or their logins. It discovers the CLI agents installed on your computer, reads the models each one is configured with, and lets you switch the active agent or model remotely. Your subscriptions, credentials, and permission settings stay exactly where they are.
🛡️ Approve risky commands before they run
Commands are checked before they reach the agent. BrewPing classifies dangerous operations
(rm -rf, git reset --hard, curl | sh, and more) and holds them for your approval. Pick a mode:
block only dangerous commands, confirm every command, or run without confirmations. Pending requests
time out as denied — silence is never an approval.
⌚ iPhone, Apple Watch and Android
Both phone apps share the same flow: discover computers on the current Wi-Fi, or add one by host and port; pair by scanning the QR code or typing the 6-digit code; then browse conversations, send instructions, switch agents and models, and approve commands. The Watch app sends voice-dictated instructions, switches agents and models with swipes, and lets you read the reply without pulling out your phone.
📁 Conversations and working folders stay together
Conversations are grouped by the folder each one is bound to. Pin, archive, and reopen them; bind a working folder to a conversation so file operations happen where the conversation lives; and set agent, model, and approval level per conversation.
🔍 Find your computer automatically
Bonjour/mDNS discovery finds computers on the current Wi-Fi without typing an IP address. If the network blocks multicast (AP isolation, guest networks), add the host and port by hand — BrewPing tells you exactly what to check.
🖥️ More built in
- Multi-device — pair more than one computer and switch between them from the device bar.
- In-app language switch — English and Simplified Chinese, switched inside the app without restarting it.
- Markdown transcripts — read agent output rendered as Markdown, including long responses.
- Local network only — no account, no analytics, no third-party SDKs; commands and output travel only between your phone and your own computer.
- Demo device (iOS) — try the whole flow with no Mac and no hardware.
🏗️ Architecture
┌──────────────┐ HTTP API ┌─────────────────────────┐
│ Phone │ ◄────────────► │ BrewPing Desktop │
│ iOS / Android│ same Wi-Fi │ macOS menu bar + window│
└──────┬───────┘ Bonjour │ or Windows (Tauri) │
│ discovery └───────────┬─────────────┘
│ WatchConnectivity │ PTY / CLI
┌──────┴───────┐ ┌──────────┴─────────────┐
│ Apple Watch │ │ opencode · claude │
│ (watchOS) │ │ codex · pi │
└──────────────┘ └────────────────────────┘
- Desktop service — a Swift core (
Sources/App,Sources/Agents,Sources/PTY,Sources/Session,Sources/Protocol) exposing an HTTP API on your LAN, supervising agent processes, and gating commands through the approval check. The Windows desktop reimplements the same API surface in Rust (Tauri 2 + axum) and is covered by the same clients. - Clients — iOS and watchOS apps (SwiftUI), Android app (Jetpack Compose), and a CLI
(
swift run BrewPing …). Clients never talk to each other, and never to a machine you did not pair. - Auth — a one-time 6-digit code becomes a long-lived token; every
/api/*call carriesAuthorization: Bearer <token>, and writes additionally carryX-BrewPing-Timestamp+X-BrewPing-Nonce(120-second window, replay-protected).
📦 Availability
What you can install today, and what is still in the pipeline:
| Surface | Status | How to get it |
|---|---|---|
| macOS desktop | Released (v1.0.0) |
Signed & notarized DMG from the GitHub Release, or build from source |
| Windows desktop | Released (v1.0.0) |
setup.exe / .msi attached to the same release, or npm run tauri dev |
| iPhone / Apple Watch | In App Review — not publicly available yet | Build from source with Xcode until Apple approves |
| Android phone | Built, not submitted to Google Play | cd Android && ./gradlew assembleDebug |
| Wear OS watch | In the repository, not released | Build from source; on no store |
BrewPing ships local-network only — there is no hosted service and no official public relay, so none of the clients talk to anything but the computer you paired.
🚀 Quick Start
🍎 macOS desktop (build from source)
git clone https://github.com/banmu123/BrewPing.git
cd BrewPing
./build-app.sh # produces build/BrewPing Desktop.app
open "build/BrewPing Desktop.app"
Prefer a prebuilt binary? The DMG on commitbrew.com is Developer ID signed, notarized, and stapled, so it opens without Gatekeeper warnings.
🪟 Windows desktop (Tauri 2 + axum)
cd Sources/BrewPingwinDesktop
npm install
npm run tauri dev
📱 iPhone / Apple Watch
open ios/BrewPing.xcodeproj # set your team, then Run
The iOS app uses bundle IDs com.brewping.ios and com.brewping.ios.watchkitapp.
🤖 Android
cd Android && ./gradlew assembleDebug # Windows: gradlew.bat assembleDebug
🔗 Pair your phone
- In BrewPing Desktop, open Show Pairing Code — a 6-digit code (and a QR code) appears.
- On your phone, scan the QR code, or tap Add Device and enter the code.
- Both devices must be on the same local network. BrewPing has no public relay and never connects to a machine you did not configure.
The pairing code is single-use and expires afte