Remote-host setup check for Git, selected providers, and service restarts

[Pranav-Bobde]

I followed the T3 Connect path on a fresh Ubuntu 26.04.1 machine, then tried to create a remote project from the Mac desktop app (T3 Code 0.0.42). I eventually got an OpenCode thread working, but the setup errors didn't tell me what to fix next.

What happened on this host:

• A new project surfaced Claude Agent CLI (claude) was not found on PATH while I was trying to use OpenCode. I cannot yet tell whether that came from provider selection, settings scope, or stale state; the UI did not make the selected provider clear.
• After I installed Claude and Codex into ~/.local/bin, command -v found both in the interactive shell, but T3 still said Not found. The background service had started before that directory and those binaries existed. Restarting t3code.service made T3 detect both versions. This is a concrete instance of the service PATH/discovery issue tracked in [Bug]: systemd user unit from t3 service install sets no PATH, so providers in ~/.local/bin are invisible to the service #4913; the startup timing is the likely explanation, not a proven diagnosis of T3's in-process PATH.
• Git was missing on the Ubuntu host, and remote project checks failed until Git was installed. I had to discover that requirement during project setup.
• After detection was fixed, T3 marked Claude Authenticated while claude auth status on the host returned {"loggedIn":false,"authMethod":"none"}. That is already tracked in [Bug]: Claude Settings reports authenticated while the launched CLI is logged out #7690.
• OpenCode 2.0.18 timed out during provider inventory. OpenCode 1.18.29 worked after I gave it a separate XDG_DATA_HOME from the v2 installation. The v2 inventory failure is already tracked in OpenCode 2.0.3 provider inventory times out in T3 Code Nightly #11790.

Could the first remote connection / first project flow show a single host setup check for the provider the user is actually trying to use?

1. Check Git and the selected/enabled provider CLI on the remote host. Offer a user-confirmed install when supported, or give the exact install/login command for that host.
2. Show the binary path, detected version, auth result, and compatibility result separately. Name the provider responsible for each error.
3. If a CLI is found in the host's login shell but the running service cannot find it, say that the service may need a restart and show t3 service restart. An in-app restart could be offered after warning that active turns/terminals will be interrupted.

I found #226, which covered general dependency probing and install hints and is closed as completed. The current welcome wizard offers inline install/login for Claude and Codex; this request is specifically about a newly connected remote Linux host, Git, other selected providers such as OpenCode, and the service's post-install state.