Access Your Mac mini Terminal from a Browser
Already have an always-on or headless Mac mini? Start Termlets on it and connect to that same terminal from another computer or your phone’s browser. Close the page, tasks keep running—reconnect anytime while your Mac mini and Termlets stay online.
Open Termlets Home to StartFirst-time prerequisite: You must already have control of your Mac mini (via a local screen, macOS Screen Sharing, or SSH) to start Termlets, check the matching 4-digit request number, and press Enter or y on the Mac to allow a new browser (or run allow <id> in command-line mode). Tested on Apple Silicon Mac mini (macOS 26, Node.js ≥ 22.23.3, and tmux). Currently free during beta (CLI tool subscriptions not included).
Desktop GUI, SSH, or a browser terminal?
Need the full macOS desktop or already use SSH?
If you need graphical macOS windows or system settings on a headless Mac mini, use macOS Screen Sharing. If you already use SSH + tmux + Tailscale, keep using them—they also work for starting Termlets the first time. If your main goal is specifically continuing Claude Code on a phone, see Use Claude Code from your phone with Termlets.
An extra browser & phone entry for your terminal
Termlets does not replace SSH or provide a remote desktop. It adds a browser and phone terminal entry on top of your setup—no client app to install on the second device, and no need to configure inbound port forwarding, a dedicated public IP, or a VPN yourself (as long as both devices stay online and the network allows Termlets and WebRTC/TURN).
3 steps to connect to your Mac mini terminal
Start Termlets on your Mac mini
Using your existing access (local screen, Screen Sharing, or SSH), run npx --yes termlets@beta in your working folder on the Mac mini, and keep that terminal window open.
Pair from a browser and match the 4-digit number
Scan the QR code in your Mac mini’s Termlets window with your phone (or open the pairing link / enter the 12-character code on termlets.com in another browser), check that the 4-digit request number matches on both screens, and press Enter (or y) on your Mac mini to allow (or run allow <id> in command-line mode).
Run your tasks inside the Termlets terminal and switch devices
Start the commands, scripts, or CLI tools (such as claude) you want to keep running inside that connected Termlets terminal. Close the browser tab anytime—while your Mac mini and Termlets stay awake and online, reopen the page to reconnect.
FAQ & Current Limits
Can I set up Termlets on a headless or remote Mac mini if I don’t have access to it yet?
No. Termlets does not rent out Macs or bypass machine access. You must already own or control the Mac mini (for example via a monitor, macOS Screen Sharing, or SSH) to start Termlets the first time, check the matching 4-digit request number, and press Enter or y on the Mac to allow a new browser (or run allow <id> in command-line mode).
Can I take over a task that is already running in SSH, macOS Terminal, or another tmux session?
No. Termlets cannot attach to arbitrary existing SSH, macOS Terminal, or tmux sessions. Start Termlets first and launch the tasks you want to continue inside the terminal session created by Termlets.
What happens if I close the browser tab—or if the Mac mini sleeps, reboots, or goes offline?
Closing the browser page leaves your tasks running in Termlets so you can reconnect later. However, your Mac mini and the Termlets process must stay awake and online; Termlets cannot wake a sleeping Mac, recover after an unattended reboot, or connect if the machine loses network access.
Which Mac mini models, systems, and network conditions are supported?
On Mac mini, the current beta supports Apple Silicon models (tested on macOS 26 / arm64; older macOS versions are not covered yet, and Intel Macs are not supported). Requires Node.js ≥ 22.23.3 and tmux (Linux arm64/x64 with glibc ≥ 2.36 is also supported in beta.5). You do not need to configure inbound port forwarding, a dedicated public IP, or a VPN yourself, provided both devices are online and the network allows connections to Termlets and WebRTC/TURN.