Your agents.
Your machine.
Wherever you are.
Install helmora on your device and it lives alongside the coding agents you already have — Claude Code, Codex, Copilot — running on your own subscriptions and API keys, exactly as they're set up today. Then watch, steer, approve, and continue their work from the web or your phone.
Your AI coding agents,
in your pocket.
Tools like Claude Code, Codex, and Copilot are AI agents that work on your code — but they run in a terminal, on one device, and you have to be sitting at it to use them. helmora turns them into a chat you can open from anywhere.
A small helper on your device
Install helmora once on the device where your agents already live. It starts them, talks to them, and keeps your code and credentials where they belong — on your machine.
A chat app everywhere else
On your phone or in a browser, it looks like messaging: say "fix the login bug and open a PR," then watch the work happen live, approve steps, and answer questions from wherever you are.
All your agents, all your machines
Every agent on every device you connect shows up in one place — and conversations travel end-to-end encrypted, so the relay in the middle can't read them.
Five agent runtimes,
one control surface.
First-party adapters cover the agents we use ourselves. Each one implements the same capability-driven contract so the client stays agent-agnostic.
OpenClaw support was removed in August 2026. Gemini CLI and Aider are not in the current build. Full adapter status →
Three steps from sign-in to
a live agent on your phone.
helmora does not host your coding runtime or provider credentials. Connect the device once, keep using the tools already installed there, and continue the same work from the web or iPhone.
Choose your platform and sign in.
Open Download, choose Windows, macOS, or Linux, then follow Add a device. helmora creates the short-lived installer for you.
Review the runtimes helmora finds.
helmora finds supported local CLIs and their project folders. Add or remove agents on each device, and authenticate each runtime where it runs.
Web or iPhone — same agent-owned history.
Open a session, follow live tools and plans, answer questions, approve actions, or steer the turn. Remote payloads are encrypted between the app and your connected device.
Watch a prompt
cross the network.
A prompt leaves your device sealed. A drifting cloud of ciphertext is all the network ever carries — only helmora on your device can put the words back together.
{from, to, nonce, ciphertext} plus timing and frame size — never plaintext, never keys.
Local only: the app and helmora talk over this device's loopback. No servers involved — the prompt never leaves the box.
The relay does not receive protocol plaintext.
helmora runs in the background on the same device as your agent. When the managed relay is used, endpoint encryption protects payloads between the app and that device. Model providers and other services you deliberately invoke still receive the data required for those requests.
Keep helmora local.
helmora's background service runs on the same device as your agent. The web app can use a same-device loopback socket, or an operator can terminate an authenticated TLS/SSH tunnel on that loopback listener.
- Same-machine loopback delivery without the managed relay
- No plaintext listener exposed on the LAN
- Authenticated TLS or SSH tunnels can provide a direct remote path
- Agent and model-provider credentials stay on your device
Use the relay when you need remote access.
When you want to drive your agent from somewhere else, the optional managed relay tunnels encrypted frames between your devices. We see routing metadata. You hold the keys.
- Per-device X3DH establishment and Double Ratchet messages are implemented for relay traffic
- Relay sees
{from, to, nonce, ciphertext}, timing, connection state, and frame size - Signed device identities are bound to routing labels; user payload frames require ciphertext
- The account service remains a trusted identity directory; padding is not implemented
Be first when the beta opens.
Installs and account creation are closed during the private pre-alpha. Leave your email and we will invite you when the beta releases — nothing else, no newsletter.
One email when the beta opens. That's it.
Already invited? Log in