Learn
How do you access a running terminal session from your phone?
The session you actually want is the one already running on your desk: the build at 80 percent, the migration mid-flight. A phone SSH client cannot give you that; it opens a new session. Continuing the same one takes a different architecture, and this is how Termuna does it.
Why doesn't an SSH app on the phone solve this?
An SSH client on your phone connects to a server and starts a fresh shell. Your running session lives in a different process, attached to a different terminal. The classic workaround is to run tmux on the server and reattach from the phone's SSH client: workable, but you are typing your server credentials on a phone, navigating tmux keybindings on glass, and it only covers sessions on machines you can SSH into from anywhere, which a laptop behind a home router usually is not.
What has to exist for the phone to see your real session?
Something on the machine that owns the session has to publish it. In Termuna, the local daemon that owns your shells mirrors every session to the relay as sealed, end-to-end encrypted frames (the full encryption path). The phone is then just another viewer: it subscribes, decrypts locally, and renders the same session your desktop shows, live. Typing on the phone lands in the very same shell on your machine.
How do you open it, step by step?
- From the dashboard: sign in at termuna.com on the phone's browser, open the session from the live list, and keep typing. The web viewer installs to your home screen as an app.
- From a share link: on the desktop, copy the session's share link and open it on the phone. The decryption key travels in the link's URL fragment, which never reaches the server, and the phone remembers it so you paste the link once.
- From the native app: the Termuna mobile app for Android and iOS attaches to the relay as a viewer, same as the web.
Is a phone actually usable as a terminal?
For watching, completely; for typing, more than you would expect. The viewer is built for touch: a soft-key row for Esc, Tab, Ctrl, arrows, and common symbols, a keyboard-aware layout, and pinch-free full-bleed rendering. You can open new tabs, split panes, and rename tabs from the phone. The honest limit is ergonomics, not capability: you will not want to write a long script on glass, but approving a deploy, watching a build, nudging a stuck agent, or restarting a service is exactly what it is for.
What happens when the phone loses signal?
The session does not care. It keeps running on your machine, and the viewer resumes where it left off: every frame carries a sequence number, so on reconnect the phone asks the relay for everything it missed and replays the gap. Walk out of the elevator and the build output catches up in front of you (what survives disconnects and reboots).