Codex Relay vs MuxPad

Codex Relay brings your Codex workflow to your phone. Connect to your local Codex Relay server and keep track of active threads, responses, approvals, and workspace activity without staying at your desk. Send follow-up prompts, review assistant output, attach images for context, and respond when Codex needs input before it can continue. Built for developers who use Codex as part of real work, Codex Relay keeps the mobile experience focused, fast, and close to the terminal workflow. Key features: - Follow Codex conversations from your phone - Send prompts and follow-up instructions - Respond to approval and input requests - Attach images as context - Review workspace and thread activity - Manage connected relay server state - Check usage - Designed for local developer workflows Codex Relay requires a running Codex Relay server on your computer. Start the server with `npx codex-relay@latest`, then connect your device over your local network. GitHub: https://github.com/gronxb/codex-relay Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/

MuxPad is a native tmux terminal built from the ground up for iPad. Unlike ordinary SSH apps that draw a single terminal screen, MuxPad runs tmux control mode (tmux -CC) over SSH and maps tmux sessions, windows, and panes directly onto a native iPad interface. NATIVE TMUX PANES & WINDOWS Windows become tabs and splits become real split views. Every pane has native scrollback, selection, and copy, with flow control that stays smooth under heavy output. FULL HARDWARE KEYBOARD CONTROL Drive tmux from an external keyboard exactly like the desktop. Control characters, Option as Meta, arrow and function keys, Home/End/Page Up/Down, the tmux prefix (Ctrl-b), and vi/emacs copy-mode keys are all sent as the correct bytes. Fine-tune with Option as Meta and Caps Lock as Ctrl/Esc. On the software keyboard, a horizontally scrolling accessory bar gives you Esc, Ctrl, arrows, the prefix, and a dismiss key. DUAL-PANE SFTP FILE MANAGER Put a local folder or any remote host in each of the two panes and move files by drag and drop. Transfer local-to-remote and remote-to-remote (relayed through your device). Long-press to multi-select and copy or move files in bulk. A transfer queue handles progress, resume, and conflicts. TMUX-NATIVE SCROLLING Two-finger and trackpad scrolling is forwarded to tmux as mouse-wheel input, so scrolling drives tmux copy-mode just like on the desktop (requires tmux mouse mode). SESSION PERSISTENCE & CROSS-DEVICE RECONNECT tmux sessions live on the server. Quit the app completely or switch devices and your session is still there. Reconnect manually or automatically with no loss, and pick up an iPad session on your iPhone. iCLOUD SYNC Hosts, reusable users, mux sessions, and groups all sync through your private iCloud (SwiftData + CloudKit) — on change and on launch. Credentials never touch CloudKit: passwords and keys stay in the Keychain (and iCloud Keychain, end-to-end encrypted), and only a reference is synced. Protect access with Face ID / Touch ID. LIVE ACTIVITY See your connected sessions on the Lock Screen and in the Dynamic Island. Tap a session to deep-link straight back into the app. One unified activity that ends automatically when you close the app. ENGLISH & KOREAN The interface is in English and switches to Korean automatically on Korean devices. ALSO INCLUDED - Host chaining (ProxyJump) through a jump host into private networks - ed25519 / RSA key and password authentication, known_hosts fingerprint verification (MITM warning) - Preset and custom themes, monospaced and Nerd Font support - Sidebar host management: inline rename, drag to reorder, groups IMPORTANT — YOUR SERVER NEEDS TMUX MuxPad is built on tmux control mode. The remote server you connect to must have tmux installed (detected automatically on connect); if it is not, the connection is blocked and installation guidance is shown. There is no local shell emulation. MuxPad does not collect your data. It has no ads and no analytics or tracking SDKs. Your server credentials and activity are never sent to the developer.