Built for coding agents
Continue Claude Code, Codex and Pi sessions from your iPhone. Open terminals, files and local web services across Mac, Linux and WSL, and control remote desktops from your iPhone or Mac.
Features
Follow a session, review a change, open the terminal or check a desktop. Keep the work on your machines, and pick it up from wherever you are.
Mac, Linux and Windows (WSL), at home, at work or in the cloud.
Group machines into meshes and jump between them. Each shows how it’s connected, on the LAN, direct or relayed, and how fast. How it connects
Set shell, desktop, files and ports to Off, Owner, Admins or Members. File writes have a separate access level. Each host enforces its own choices; joining a mesh does not open every service.
See device roles, grant admin access and remove devices you no longer trust. Review which devices a removal affects. Rename your mesh or move it to your own rendezvous without starting over. Use Rejoin with Invite to reconnect while preserving this device’s identity and data.
Claude Code, Codex and Pi, from start to finish on your iPhone.
Start, find and resume sessions across your projects. Schedule recurring work on your machine and get a notification when a run needs you.
Share Codex and Pi conversations between your terminal and iPhone. Follow Claude Code live and take over when you need to. Optional mesh tools let your agent reach other machines, with approvals for commands and writes.
Create reusable bots with their own personality, agent and model, then @mention one for a second opinion beside the main agent. Bots can remember their exchanges and share memory within a chat. Keep them chat-only, or enable read-only project tools to inspect files and diffs. Describe one with /meshieve:createbot.
Tokens and cost by agent, model and day, with cache hits and the average per session.
What you’d do at the keyboard, from wherever you are.
CPU, memory, disk, GPU and traffic for each machine, plus how much agent quota is left.
A real shell that survives a locked phone or a new network, with the keys a phone keyboard lacks.
Open the local web services your host shares with your role, without exposing them to the internet.
Browse, preview and move files on the machine, and share your iPhone’s files and photos back.
Commits, branches, worktrees and diffs for each project, next to its sessions and services.
Remote desktop
Your Mac at home. A Linux workstation across the room. See and control their screens through the same mesh, with touch controls on iPhone and a native viewer on Mac.
Actual iPhone captures · macOS, KDE Plasma, Hyprland and GNOME. Open any screenshot for the full-size view.
Touch-friendly pointer, zoom and keyboard controls put the remote screen in your hands. Connect to Mac and Linux hosts.
Open Mac and Linux desktops in native viewer windows on your Mac, with keyboard and pointer input, audio, full screen and connection statistics.
Linux desktop hosting requires the GNU/glibc build and a logged-in graphical session. GNOME, KDE Plasma and Hyprland Wayland use PipeWire and a ScreenCast v4+ portal. X11 uses local approval and a visible Stop sharing control; system audio requires PipeWire. Run meshieve mesh start --desktop-access admin as the desktop user. Headless desktops, WSL desktop hosting and musl builds are not supported.
Get started
Install the Mac app to create or join a mesh. Add your iPhone with an invite QR, or use the CLI on Linux and WSL.
Your machine only dials out. Nothing listens on your router.
No VPN profile on your iPhone, no network settings changed on your machine.
The invite QR carries everything the phone needs. No keys or IP addresses to copy.
No email, no password, no sign-in. Each device is known by its own key.
iOS 18 or later.
Remote desktop included. macOS 14 or later, updates itself.
First launch creates your mesh and shows its invite QR.
Scan the short-lived invite in Meshieve. After joining, give your own phone the Admin role so it can use services shared with admins.
These examples require a CLI build with per-service access levels. They share your home folder and local ports with admins. Approve only your own trusted devices; choose a narrower folder or specific ports if needed.
By downloading or using Meshieve, you agree to the Terms of Use and Disclaimer and the Privacy Policy.
How it works
Our servers help your devices find each other. They connect directly on your LAN or across the internet, or through a relay when a network blocks direct paths.
An invitation adds your device to the mesh’s signed member list. The rendezvous helps members find each other; each device checks membership before accepting a connection.
Hole punching opens a direct QUIC path, on your LAN or across the internet, with mutual TLS pinned to each device’s key.
Behind strict NATs, a relay forwards encrypted packets it holds no key for, and the link moves to direct as soon as it can.
Your data is readable only on your connected devices. Every mesh connection is end-to-end encrypted, and the decryption keys stay on those devices. Meshieve’s servers, rendezvous operators and relay operators cannot read your terminal traffic, files or remote desktop—even when they forward every packet.
CLI
The meshieve binary that serves your machine also drives the mesh from any terminal on it: open shells, run commands, and move files between machines.
mesh shell attaches to a persistent tmux session, or runs a single command and returns its exit status.
Push, pull and list files within a peer’s shared folder, subject to its read and write access levels. NFS mounting also requires --serve-nfs on the host.
Address a machine by its name, overlay IP, or the first few characters of its ID.
Remote commands keep stdout, stderr and exit codes intact, and -o json gives status in a form your tools can read.
Self-hosting
Our servers can’t read your traffic, but they see which of your devices are online, where they connect from, and the timing and volume of traffic they forward. Host the rendezvous and relay yourself and all of that stays with you.
Who is online, from which address, and when stays on your server. iPhone agent notifications still use our push service.
Put relays near your machines or inside your network, sized for your traffic.
Your mesh’s connectivity doesn’t depend on our rendezvous or relays.
Rendezvous and relay ship in the meshieve binary you already run. The invite QR tells the phone where your server is.
The invite gives your iPhone the server address and an Admin role. Only grant Admin to devices you trust. Your rendezvous can also relay traffic.
Run meshieve rendezvous relay invite on the server, then meshieve relay join --invite-url with the invitation it prints and meshieve relay start on the relay host.
FAQ
Yes. Meshieve is free to use. When our hosted services experience heavy traffic, we may temporarily throttle traffic passing through them to keep the service available. Third-party coding agents, AI providers and your own hosting or network services may charge separately.
No. There is no sign-up, email or password. Each device is identified by its own key, and you add devices by scanning an invite QR code.
Yes. Your iPhone reaches your machine from any network. It connects directly when it can, and through a relay when a network blocks direct paths.
The rendezvous handles device names, identifiers, network addresses, and connection metadata, and forwards traffic itself when no direct link or standalone relay is available. All mesh traffic is end-to-end encrypted, so neither the rendezvous nor a standalone relay holds the keys to read it. Agent notifications use a separate push service, which receives routing identifiers, peer names, session titles, and event details and forwards them to Apple. See our Privacy Policy for details.
SSH over a VPN gives you a shell. Meshieve gives you your whole development environment, on every machine you own, in one app: coding agents, terminal, files, local web services, git and the desktop. It’s built to work from every day, not just to check in on an AI. And there’s nothing to set up: no SSH keys, no firewall rules, no VPN profile.
Claude Code, Codex and Pi. Codex and Pi support shared terminal sessions; Claude Code supports live read-only following and handoff to your phone. Codex cooperation is set up when you first open a Codex session in Meshieve. Restart an already-open desktop app after setup; reopen its conversation to see turns sent from another client.
Reusable helpers with their own personality, coding agent, model and effort level. @mention one in an agent session and it replies beside the main agent, without adding to its context. Bots can remember their exchanges or share memory within a chat. They are chat-only by default; optional read-only project tools let them list, search and read files and inspect diffs without changing the project.
Terminal, coding agents, files and local web services work on Linux and Windows through WSL. Remote desktop hosting works on Mac and on Linux with GNOME, KDE Plasma and Hyprland Wayland desktops or X11 desktops such as Cinnamon, Xfce and MATE. Linux hosting requires the GNU/glibc build and an active graphical login. Wayland requires PipeWire and a ScreenCast v4+ portal; X11 requires local approval and keeps a Stop sharing control visible; system audio requires PipeWire. Headless desktops, WSL desktop hosting and musl builds are not supported. Windows desktop hosting is not supported.
iOS 18 or later.
