Hi,buddy vs BYOT Coding Agent

Hi,buddy turns your phone into a Claude Hardware Buddy companion for Claude Desktop. Connect over Bluetooth and keep Claude's work visible in the palm of your hand. Hi,buddy acts as a BLE peripheral compatible with the Hardware Buddy flow, showing live session state, permission prompts, and feedback controls on the device you already carry. What Hi,buddy helps with: • See Claude status at a glance Track running and waiting sessions, current status, recent activity, and token signals from Claude Desktop. • Approve faster When Claude needs permission, Hi,buddy surfaces the request so you can approve once or deny from your phone. • Feel important changes Use haptics, sound, visual states, Live Activities, and notifications to notice waiting approvals and session changes. • No extra device required Try the Claude Buddy experience without setting up an ESP32 or M5StickC-style hardware accessory. • Made for makers and developers Hi,buddy is designed for people who keep Claude Desktop running while coding, shipping, testing, or tinkering. Important notes: Hi,buddy works with Claude Desktop's Hardware Buddy Bluetooth flow. For discovery, your device system Bluetooth name may need to start with "Claude". Bluetooth discovery and sensory feedback depend on foreground/background behavior.

BYOT is a native client for OpenCode, the open-source coding agent. Connect to the OpenCode server running on your own computer and drive coding sessions from your iPhone or iPad. Browse projects and sessions, send prompts with photos or files, and watch assistant text, reasoning, and tool activity stream live. Inspect tool inputs, progress, output, and errors. Answer permission requests and questions from your server, queue follow-up prompts, and choose models from your server's catalog. Review session diffs when your server supports them. Switch between saved servers, group sessions by project or browse them in one list, and find sessions by title, project, or path. Unsent text and attachments stay on this iPhone across session changes and app relaunches. Choose System, Light, or Dark appearance. With the optional BYOT companion running on your computer, get notifications for approvals, questions, completed turns, and errors. Enable the computer queue to keep accepted prompts running in order while BYOT is closed. Your computer must remain awake and the companion connected. Work that has not finished uploading needs BYOT to reconnect; uncertain delivery requires your review. BYOT supports OpenCode 1 and OpenCode 2 beta servers with automatic protocol detection. Available features depend on the server version; some OpenCode 2 beta servers do not expose per-session diffs. Your server does the work. BYOT renders its responses and sends your instructions over HTTPS. There is no BYOT account or sign-up, and no tracking. Anonymous usage data is off until you turn it on, and it never includes your prompts, code, server addresses, or project names. Server passwords are stored in the iOS Keychain. In direct mode, prompts and attachments go to your configured server and the model providers you enable there. Optional notifications and the computer queue use the BYOT relay for device registration, delivery, and encrypted queued content. See the privacy policy for storage and retention details. Requires an OpenCode server you operate, reachable over HTTPS, for example through Tailscale. Notifications and the computer queue also require the BYOT companion. BYOT is an independent client and is not affiliated with the OpenCode project.