T3 Remote Setup

Prepare $ARGUMENTS (an SSH host or alias) so the user can open Settings → Connections → Add environment → SSH in the T3 Code desktop app and connect once, with the right name, without reconnecting.

Principles

• The desktop app owns the server. Never start t3 serve yourself. A server you start is adopted as managed=external: the app will not restart or clean it up, and removing the environment leaves it running. The app downloads a server matching the client version to ~/.t3/runtime and launches it on first connect.
• Name before connect. The server reads its environment label only at startup. Set the name before the user adds the environment, so no restart or reconnect is needed.
• Leave no SSH connections behind. Run every remote command as one short-lived ssh call. Never use ssh -f, -L, -N, nohup through SSH, or ControlMaster. Never pipe a background SSH into another command. Pass -o ControlMaster=no -o ControlPath=none -o BatchMode=yes -o ConnectTimeout=15 on every call.
• Kill only by PID. Never use pkill, or pgrep | kill. Stop a process only by a PID you just read and showed the user, and only after the user agrees.
• Some SSH wrappers, such as Coder, print version-mismatch notices on stderr. Mention a notice once, then filter it out of later output.
• Talk to the user in their language.

Workflow

1. Resolve inputs

If $ARGUMENTS is empty, ask for the SSH host. Then use AskUserQuestion to ask, in one call: