S · machines + harnesses, connected
One control layer. Every machine and harness you own
Ormur is a meta-control layer for terminal-native work: it connects your phone to the computers, sessions and AI coding harnesses already working on your projects. Start with one tool on one machine, supervise several from anywhere, and return to the exact terminal when you are needed.
Windows agent available now · Android private beta · Linux preview · iPhone and iPad build in App Store preparation.
ormur · your-workstationFIG 01 · The product
The tools keep doing the work. Ormur connects the control
Your repositories, shells, harnesses and AI subscriptions stay where they already are: on your computers. Ormur gives them one machine-aware, touch-friendly control surface without forcing every workflow into one provider, one chat format or another hosted IDE.
Terminal
A full terminal made for a phone
Responsive terminal rendering, session tabs, scrollback and a coding key bar for shells such as PowerShell, bash and zsh. If a tool runs in your terminal, Ormur can reach it.
Agent cockpit
Your sessions, one clear view
See sessions that are running, waiting, finished or offline. Open the exact session that needs attention and resume it when the underlying CLI supports resume.
Notifications
Know when a supported agent needs you
After you enable notifications and background connectivity, supported local tools can alert Ormur about waiting input or completed work. Tap the alert to return to the relevant session.
Fleet
Paired machines and verified routes
Fleet shows the computers and phones in your Ormur network, their current reachability, workspaces and the route the app has actually verified — or a clear offline reason.
Reconnect-aware
Temporary interruptions are not the end
When the app, network or computer is temporarily unavailable, Ormur retries and reports what is happening. Terminal sessions remain hosted on the computer while the Ormur agent is running.
Files & usage
Move what you choose. See what tools expose
Accept files offered by a connected computer, attach selected files from your phone, and view token or quota data only when the local harness makes it available. Ormur does not invent usage estimates.
WHO IT IS FOR · One product, different starting points
Start with one AI tool. Grow into a fleet without changing the control surface
Ormur does not assume that everyone begins with the same stack. It can be the simple phone terminal for a first project, the session cockpit for a working developer, or the connective layer above several machines and harnesses.
First AI project
One computer, one tool, a clear way back in
Install an AI CLI on your computer under its own account, add the Ormur companion, then pair your phone. Ormur does not choose a model or hide where commands run; it gives you a visible terminal and a safe path back to that machine.
Vibe builders
Keep the momentum without living at the desk
Watch long-running work, answer a supported agent when it pauses, attach the file you intentionally select, and return to the full session instead of reconstructing context across a pile of disconnected chats.
Professional developers
Keep the real repository and toolchain where they belong
Your shell, Git state, extensions, credentials, local services and provider session remain on the workstation. Ormur adds remote control without replacing the environment with a simplified hosted workspace.
Multi-machine workflows
See the machine before you act
Fleet and session context make the target explicit when work spans a laptop, workstation or server. File transfer and session actions stay tied to the selected device instead of silently assuming that every project lives in one place.
FIG 02 · Security, precisely
Your terminal content stays between your devices
Remote terminal access deserves exact language. Ormur encrypts terminal traffic between your phone and computer. The coordination service still handles the minimum metadata needed to pair devices and establish reachability; it cannot read terminal content.
End-to-end terminal encryption
Terminal traffic travels inside an embedded WireGuard mesh. When a direct path is unavailable and a relay carries the packets, the terminal content remains encrypted between your phone and computer.
Metadata is described, not hidden
Pairing and reachability require limited coordination data such as a device label, public key, mesh address, last-seen state and setup IP address. That service does not receive terminal content or AI-provider credentials.
No public terminal port required
The computer joins an outbound userspace mesh, so normal setup does not require port forwarding or a public SSH-style terminal port. A same-network fallback, when used, remains local to that network.
Device-scoped access
Pairing creates device-specific credentials. Trusted devices can be reviewed and revoked; removing a device cuts off that credential without requiring you to replace every other paired device.
No AI proxy in the middle
Claude Code, Codex, Gemini CLI, local models and custom harnesses continue to run on your computer under their own accounts. Ormur does not resell tokens or store provider logins.
Access remains a serious responsibility
A paired phone is a key to your computer. Protect it with the security your operating system provides, review trusted devices, and revoke access when a phone is lost, replaced or no longer trusted.
FIG 03 · How it works
Three steps. No port forwarding
Install the computer agent
Run one PowerShell command on Windows. The installer registers the Ormur agent and prepares the computer for guided pairing without opening a public terminal port.
Pair the devices
Open Ormur on Android and scan the QR shown by the computer, or enter its short code. Verify that you are connecting to the intended machine before you trust it.
Open a session
Ormur establishes the available direct, mesh or encrypted relay route and loads the terminal. Fleet shows the route it has verified and explains when the computer is offline.
THE DATA PATH · Four responsibilities, kept separate
What actually happens when you use Ormur
1 · Mobile control surface
Your phone sends an intentional terminal action
The app renders sessions, collects the command, answer or chosen file, and targets the computer you selected. It is not the execution environment and it does not hold your AI-provider login.
2 · Private transport
The device link chooses a working encrypted route
An embedded userspace WireGuard mesh attempts the available direct path and can fall back to an encrypted relay route. Pairing and reachability metadata coordinate the path; terminal content remains encrypted end to end.
3 · Computer companion
The machine you chose owns the process
The Ormur agent opens or reconnects to the local terminal, keeps device and workspace context, and exposes only the controls and status it can actually verify on that computer.
4 · CLI or harness
Your existing tool continues under its own rules
The shell, Claude Code, Codex, Gemini CLI, local model or custom harness runs locally with its own account, model choice, resume behaviour and provider limits. Ormur connects the interaction; it does not impersonate the tool.
PS C:\> irm https://ormur.app/install.ps1 | iex
Want the full model?
Read the architecture, compatibility and data-flow guide
See the exact request path, trust boundaries, multi-machine file behaviour, harness capability model, recovery rules and current product limits.
FIG 04 · Why Ormur
The connective layer above your tools — not another tool silo
A harness knows how to run work. A computer owns the environment. Ormur connects those layers: it discovers what is running where, keeps sessions and devices legible, and gives you one place to supervise them without moving the job somewhere else.
Harness-agnostic
One cockpit above the tools you chose
Claude Code, Codex, Gemini CLI, local models, shell scripts or a custom harness can remain themselves. Ormur connects to their terminal-native work instead of replacing them with a proprietary agent runtime.
Machine-aware
Know which project is running on which computer
Fleet, sessions and file destinations retain machine context. You choose the computer and workspace deliberately instead of treating every terminal as one anonymous remote shell.
Local execution
Your computer remains the execution environment
The source tree, credentials, extensions, provider accounts and running processes stay on the machines you control. Ormur is the secure control surface, not a replacement cloud workstation.
Useful honesty
One view, without pretending every harness is identical
Ormur normalises the controls it can verify — machine, session, state, route, files and exposed usage — while keeping unsupported capabilities explicit instead of inventing a false universal API.
FIG 05 · No overclaiming
What Ormur is — and what it isn't
Ormur is
- Genuinely end-to-end. Your terminal data is encrypted between your two devices; the relay and we cannot read it.
- Yours to own. Bring your own AI, keep your own keys, and leave whenever you want — nothing is held hostage.
- Minimal-exposure by design. No public terminal port is required, and paired device access can be reviewed and revoked.
Ormur is not
- Magic that removes responsibility. A paired phone is a key to your PC — guard it like a logged-in laptop.
- "Unhackable." Nothing is. We audit, we fix, and we tell you what's still open — judge us on that.
- An AI service. We don't sell or proxy anyone's AI. You bring your own — we're only the secure wire.
- A released team workspace — yet. Today's trust model connects devices and machines you control. Shared projects, roles and multi-person collaboration belong to the roadmap and are not advertised as shipped features.
FIG 06 · Availability
Available where it is ready. Clearly labelled where it is not
Ormur is in active beta. The Windows computer agent is available today; Android access is distributed privately while the Google Play release is prepared. Linux builds are available for testing, and the native iPhone and iPad app is being prepared for TestFlight and App Store review.
Windows computer agent
Install the companion agent on a Windows computer you own.
- PowerShell and Windows terminal workflows
- Guided pairing and background startup
- Published SHA-256 for the download
Android application
The mobile terminal and fleet control surface are being prepared for Google Play.
- Terminal, Sessions, Fleet, Inbox and Usage
- QR or short-code pairing
- Optional supported-agent notifications
Availability, pricing and any paid feature terms will be shown in Google Play before purchase.
Request beta accessLinux computer agent
Linux packages are built for validation and are available to testers on request.
- Native companion-agent build
- Terminal and mesh transport validation
- macOS and iOS are not yet released
FIG 07 · Download
Get Ormur
Ormur has two parts: a companion agent on a computer you own and the Android app on your phone. Install only on machines you are authorised to control.
Windows PC agent
LiveRun this in PowerShell on a Windows computer you own. Review the script first if you prefer; installation may request administrator approval and then shows the guided pairing flow.
PS C:\> irm https://ormur.app/install.ps1 | iex
We're a new publisher, so Windows SmartScreen will warn on first run — that's expected for now. Verify the SHA-256 above, or read install.ps1 yourself before running it. Code signing arrives with our store release.
Android app
Closed betaThe phone side is an Android application with the encrypted mesh built in. It does not require a separate Tailscale application or manual port forwarding.
Android is currently distributed to private testers while the public Google Play release is prepared.
- Full terminal, session tabs and coding keys
- Supported-agent notifications and selected file transfer
- Fleet reachability, route status and diagnostics
iOS app
App Store prepOrmur cannot be installed on an iPhone as an Android APK. Its native iPhone and iPad build is being prepared for TestFlight and App Store review. Get notified when iOS ships.
Linux & macOS agents
NextThe companion agent is built as a native binary. Linux packages are in validation; macOS is not yet released. Ask for an early Linux build.
FIG 08 · Questions
Quick answers
Can you see my code or my terminal?
No. Sessions are end-to-end encrypted between your phone and your PC with WireGuard. Our coordination server sees connection metadata (which devices are online), never content.
Do I need Tailscale or a VPN app?
No. The mesh is embedded in Ormur itself — the app and the agent carry their own userspace WireGuard. Nothing else to install or keep updated.
Which AI do I need?
Whatever you already use. Claude Code, Codex, Gemini CLI, local models — they run on your PC under your own accounts. Ormur never touches your AI credentials and doesn't sell you tokens.
What happens when the app or network disconnects?
Ormur retries after temporary interruptions and reports the verified route or offline reason. Sessions remain hosted on the computer while the agent and process are running; after a computer reboot, resuming work depends on the local CLI and its own resume support.
What information does the coordination service process?
It handles the limited metadata needed for pairing and reachability, such as device labels, public keys, mesh addresses and last-seen state. Terminal content remains encrypted between your paired devices.
Ormur
Put your machine in your pocket
End-to-end encrypted terminal content. No public terminal port required. Your AI tools and credentials stay on your own computer.
Your machine. Your keys. Your terminal.