Helmor Mobile launches phone UI for Claude Code, Codex, and OpenCode with Cloudflare Tunnel
Helmor released an open-source mobile client that exposes Claude Code, Codex, OpenCode, and custom model backends behind a phone-first UI plus one-click Cloudflare Tunnel setup. The launch targets remote coding sessions from a handset instead of a laptop-only agent workflow.

TL;DR
- caspian_1016's launch post says Helmor Mobile puts Claude Code, Codex, OpenCode, and custom model backends behind a phone UI, while the Helmor homepage still frames the project as a local-first IDE for coding agent orchestration.
- The launch also bundled one-click Cloudflare Tunnel setup, which caspian_1016's launch post pitched as more stable than Codex remote connections.
- Helmor's merged mobile browser companion PR describes a paired browser client that serves the same responsive frontend over a loopback HTTP and SSE surface mirroring Tauri IPC commands.
- The pairing flow is more opinionated than a raw shared URL: the mobile browser companion PR says QR scans only stage a token, then require a separate confirm step before the device is trusted.
You can browse the repo, read the merged mobile companion PR, and watch caspian_1016's early demo and caspian_1016's launch video side by side. The interesting bit is that Helmor did not ship a thin notification client. It shipped a browser-served control surface for your desktop agent sessions, right as dkundel's Codex post and NickADobos's Codex on iOS thread were already showing how awkward laptop-tethered mobile coding still is.
Mobile companion
Helmor's public pitch is simple: same desktop power, proper mobile UI, open source, private by design. The repository and homepage place that mobile client inside a broader local-first workbench for multi-agent software development, not a standalone phone app.
The merged mobile browser companion PR makes the scope clearer. It says a paired phone or browser can drive desktop workspaces, sessions, and agents from one stable URL, with the frontend kept live and in sync with the desktop.
Pairing and transport
The most concrete implementation detail lives in the mobile browser companion PR. Helmor serves the same responsive frontend over a loopback HTTP and SSE surface that mirrors Tauri IPC commands.
That PR also spells out the pairing model:
- Devices are paired from Settings to Mobile companion, by QR code or copyable link.
- Opening the link stages a token and shows a confirm screen.
- An unpaired browser gets a pairing screen instead of demo data.
- The remote session lives at a stable
remote-<id>.helmor.aiURL.
Cloudflare Tunnel is only called out in caspian_1016's launch post, not in the PR summary, which makes the launch tweet the strongest source for the one-click tunneling claim.
Phone-first workflows
Before the formal launch, caspian_1016's couch post was already describing the intended use case: kick off local builds and previews away from the desk, then return once the work is done. That fits the product shape in the PR better than the usual "mobile IDE" framing does.
The wider mobile coding context is still messy. dkundel's Codex post joked about propping open a laptop and tethering to a phone when a demo was still running, while NickADobos's Codex on iOS thread described a workflow where Codex stays in background dictation and pushes fresh builds back to the phone. Helmor's pitch is basically an open-source answer to that same demand, but with the control plane living on your own desktop machine.