TUI Apps on Phone: tmux, vim, htop, Claude Code

Short answer. You can run TUI apps on a phone if the terminal is real enough. tmux, vim, neovim, htop, lazygit, Claude Code, Codex CLI, OpenCode, and Gemini CLI need alternate-screen rendering, modifier keys, arrow keys, copy/paste, and persistent processes. Local terminals like Termux work well on Android for many tools; SSH clients work if you already have a server; browser IDE terminal panels are cramped; a mobile cloud terminal like Cosyra gives you the cleanest phone-first TUI path because the apps run in Ubuntu while the phone stays a native terminal.

This guide is for the searches that do not quite say "AI coding agent" yet: "TUI on phone," "tmux on iPhone," "vim on Android," "terminal app for htop," "phone terminal for Claude Code," and "can I run terminal UI apps from my phone?" Those queries are category-level. The answer is not just "install an app." The answer is choosing where the terminal process lives.

What do TUI apps need from a phone terminal?

A TUI is only as good as the terminal underneath it. Many mobile apps can show a shell prompt; fewer handle the details that interactive terminal programs assume. The practical requirements are alternate screen support, accurate redraws, raw keyboard input, modifier keys, paste behavior that does not corrupt commands, and long-lived process state.

What are the options for running TUI apps on phone?

There are four real options: run the TUI locally on Android, run it locally on iOS with a constrained shell, SSH to your own machine, or use a mobile cloud terminal. Browser IDEs can include terminal panels, but their primary UI is usually a desktop IDE or app-builder surface, which makes them weaker for TUI-heavy work on a narrow phone.

1. Local Android terminal: Termux

Termux is the best-known local Android path. It is excellent for many TUIs: tmux, vim, htop, git, Python scripts, Node tools, and package-manager work. The tradeoff is that everything runs on the phone in an Android-flavored ARM userland. That is fine for local tinkering and offline work. It is rougher for x86_64 Linux assumptions and long-running AI agent sessions.

2. Local iOS shells: iSH and a-Shell

iSH and a-Shell give iPhone users local terminal-like environments. They are useful for learning, scripts, and lightweight tools. They are not the smooth path for modern AI coding CLIs or heavy Linux workflows. iOS sandboxing, emulation overhead, and package compatibility all show up quickly once the TUI needs a real x86_64 Linux environment.

3. SSH client plus your own server

Blink Shell, Prompt, Termius, JuiceSSH, and Termux-as-SSH-client can all drive TUIs well if the remote machine is solid. This is the power-user path. Run tmux on the server, use mosh if available, and the phone becomes a remote terminal. The cost is operational: keys, machine uptime, OS patches, network access, and keeping the host awake.

4. Mobile cloud terminal: Cosyra

Cosyra is the managed version of the SSH path. You do not bring a server. The app connects to your Ubuntu 24.04 container, where tmux, vim, git, gh, Claude Code, Codex CLI, OpenCode, and Gemini CLI can run. The phone handles rendering and input; the container handles the process lifecycle.

How do you run tmux, vim, htop, and AI CLIs on Cosyra?

The commands are normal Ubuntu commands. The key difference is that they run in a container that persists between phone sessions. That means a short coffee-line session can start an agent, a train stop can review the diff, and a later desktop session can pick up the same repo.

Why do AI coding TUIs fit phones better than IDEs?

AI coding agents changed the mobile coding equation. Before agents, coding from a phone meant typing source code into a tiny editor. With agents, the phone workflow is prompt, wait, inspect, approve, and redirect. That maps to a terminal better than it maps to a desktop IDE compressed into mobile Safari.

A TUI agent takes the whole viewport, streams output line by line, asks permission in place, and leaves files in a real repo. It is closer to a chat plus shell than to manual editing. That is why we built Cosyra around the terminal primitive instead of a file-tree-first layout.

We tested this assumption on a Pixel 8 and an iPhone 14 in May 2026. tmux, vim, htop, lazygit, and Claude Code rendered cleanly in the alternate screen, redrew correctly after orientation changes, and survived two backgroundings each. Where the experience broke down was always the keyboard layer, not the TUI layer: glass keyboards do not give you ESC, CTRL, ALT, or arrow keys for free, which is why our toolbar exposes those keys and why we suggest a Bluetooth keyboard for long vim sessions even though most agent loops are fine without one. The TUIs themselves treat the container like any other Linux machine.

Which TUI-on-phone setup should you pick?

Pick by the constraint you cannot compromise on. If you need offline, pick a local terminal and accept compatibility limits. If you already run a secure, always-on server, use SSH and tmux. If you want the server included and the agents already installed, use a mobile cloud terminal.

• Pick Termux for local Android work, offline scripts, and package-manager tinkering.
• Pick Blink Shell or Termius if your server already exists and you want a polished SSH client.
• Pick Cosyra if you want TUI apps and AI coding CLIs on both iPhone and Android without managing infrastructure.
• Pick Replit or Codespaces if your main job is an app-builder or IDE workflow, not a terminal-first TUI workflow.

Frequently asked questions