OpenCode vs Kernelhub

Seamlessly continue OpenCode sessions started on your computer from your phone, or continue mobile sessions back on your computer. (this is an open source community project. It is unofficial and is not affiliated with opencode.ai) FEATURES: ◆ Connect to any OpenCode server over HTTP or HTTPS, whether on your local network or remotely through a VPN such as Tailscale. ◆ Create multiple server profiles and automatically connect to your preferred server. ◆ Basic Auth support, including OpenCode servers configured with OPENCODE_SERVER_PASSWORD. ◆ Pull down while connected to access server management. Pull to refresh or open the menu to switch and manage servers. ◆ Automatic server health checks with exponential reconnect when the connection is interrupted. ◆ Secure password storage using Keychain. ◆ Dark and light themes with automatic system theme support. ◆ Optional Enter newline mode. Enter inserts a new line and Shift+Enter sends the prompt. ◆ OPEN SOURCE Found a bug or have an idea for an improvement? Contributions are welcome. You can report issues, suggest features, or submit pull requests on GitHub. GitHub repository: https://github.com/bmpenuelas/opencode-mobile-client ◆ QUICK START: An OpenCode server is required to use the app. The app acts as a client and connects to an OpenCode web server running on the computer where your source code and development tools are located. ► Without authentication opencode web --hostname 0.0.0.0 --port 4096 ► With authentication Authentication is recommended when the server is accessible beyond your trusted local network. export OPENCODE_SERVER_PASSWORD="your-secret-password" opencode serve --hostname 0.0.0.0 --port 4096 When authentication is enabled, the default username in the app is: opencode

KernelHub connects the CLI coding agents already running on your own machine — Claude Code, Codex, Antigravity CLI — to the phone in your pocket. Getting started is one command. In your project folder, run icloser pair. It prints a code. Scan it. That's the setup. WHAT IT IS FOR You leave your desk mid-task. Later, on your phone, you want to know what your agent decided, approve the thing it's waiting on, or say one more sentence — without re-explaining the whole project from scratch. KernelHub keeps tasks, agents, memory and files together, so the next device picks up where the last one stopped. HOW IT WORKS • Say it in plain language. Your sentence is queued verbatim and handed to the CLI runtime on your own machine. • Watch it happen. A single timeline shows what needs you, what is running, and what finished. • Decide from anywhere. Approvals, questions and conflicts are actionable from the phone. • Seven permission levels — read, change code, run commands, search the web, push, system ops, delete or migrate data — each confirmed per device. Permission granted on one device is never inherited by another. WHAT IT DOES NOT DO KernelHub never holds your model API keys, and the backend never calls a model. Every conclusion comes from the runtime signed in on your own machine. The workspace token lives in this device's Keychain and never syncs via iCloud. When it cannot read your workspace, it says so. It will not draw an empty screen and let you conclude there is nothing to do — that misreading is exactly what this app exists to prevent. REQUIREMENTS A machine running icloser, reachable from your phone, with at least one CLI coding agent installed and signed in.