Codeusse 2 brings tmux session persistence to every SSH connection. That changes what an ideal host looks like. A few deliberate choices on the server side can mean the difference between a session that survives a subway ride and one that drops the moment you lose signal.
Here is the short version of what to optimize, and why each piece matters.
1. Install tmux — it is now essential
Codeusse 2 expects tmux on the host. When it is available, the app creates and attaches to a dedicated codeusse-main session that lives on the server even when your phone disconnects. When it is not available, Codeusse falls back to a plain SSH session.
That fallback works, but it is flaky on mobile networks. A plain shell dies with the TCP connection. On a phone that switches between Wi-Fi and cellular, rides an elevator, or simply locks the screen, that means your working directory, running processes, and scrollback vanish. tmux keeps all of that alive server-side, so reconnecting is instant and lossless.
Most Linux distributions and BSDs ship tmux in their base repositories. macOS users can install it through Homebrew:
brew install tmuxFor other systems, see the full tmux installation guide.
2. Prefer SSH key authentication
Private-key authentication is the recommended default for any host you reach over the internet or an untrusted network. It eliminates password prompts, resists brute-force attacks, and pairs cleanly with SSH agents.
You do not need an elaborate setup. A standard Ed25519 key is enough:
ssh-keygen -t ed25519 -C "codeusse"Copy the public key to your host with:
ssh-copy-id -i ~/.ssh/id_ed25519.pub user@hostThen store the private key in Codeusse and connect without typing a password.
When password auth is fine
Password authentication is perfectly acceptable when both of these are true:
- You connect only over a local network (e.g., home Wi-Fi, a lab LAN).
- Or you tunnel through a trusted VPN you control.
In those cases the attack surface is small, and the convenience of skipping key setup may outweigh the risk. Just remember that passwords sent over SSH are still encrypted in transit; the main concern is brute-force exposure on internet-facing hosts.
3. Summary checklist
| Concern | Recommendation |
|---|---|
| Session survival | Install tmux so Codeusse can persist codeusse-main |
| Reconnection quality | Avoid plain SSH fallback on mobile networks |
| Authentication | Use private keys for internet-facing hosts |
| Trusted local/VPN | Password auth is fine if the network is controlled |
Take ten minutes to install tmux and copy an SSH key to your host, and Codeusse 2 becomes meaningfully more reliable — especially when you are coding on the move.
Have questions about tuning your host? Drop by our Reddit community — we are happy to help.