fix(ssh): let cold remote servers finish starting

[gbarros-dev]

Cold SSH environments can spend longer than 15 seconds downloading the T3 CLI and starting the server. The launcher then terminates npm before the server becomes ready, surfacing a misleading SIGTERM failure.

Give remote startup 60 seconds and the surrounding SSH launch command 90 seconds so the readiness window has enough headroom. A focused regression test covers a successful 75-second cold launch.

Fixes #2770.

Verification:

• vp test run packages/ssh/src
• vp run --filter @t3tools/ssh typecheck
• vp fmt --check packages/ssh/src/tunnel.ts packages/ssh/src/tunnel.test.ts

Generated with GPT-5.6 Sol using Codex in T3 Code.

---

Note

Low Risk
Timeout-only changes in SSH remote launch with a focused regression test; no auth or data-path changes.

Overview
Cold SSH launches were failing because the remote readiness window was only 15s while npm/T3 install and boot can take much longer, and the surrounding SSH session could still time out before the launch script finished.

This raises the embedded wait_ready budget to 60s (REMOTE_READY_TIMEOUT_MS) and sets an explicit 90s timeoutMs on the remote launch runSshCommand so the client waits longer than the on-host readiness loop. Tests assert the launch script uses wait_ready "60000" and add a regression where a 75s delayed SSH response still returns a valid remotePort.

^{Reviewed by Cursor Bugbot for commit 87a914b. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Increase SSH remote launch timeout to allow cold remote servers to finish starting

• Increases REMOTE_READY_TIMEOUT_MS from 15s to 60s and adds a new REMOTE_LAUNCH_TIMEOUT_MS constant of 90s in tunnel.ts.
• Passes REMOTE_LAUNCH_TIMEOUT_MS as the timeoutMs option to runSshCommand in launchOrReuseRemoteServer, overriding the shorter default SSH command timeout.
• Adds a test covering a 75-second delayed remote launch using TestClock to verify the extended timeout works end-to-end.

^{Macroscope summarized 87a914b.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 9e51b509-564d-495a-a55c-5533aaf1980f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved 87a914b

This is a simple timeout configuration fix that increases waiting time for cold remote servers to start (15s→60s ready timeout, adds 90s launch timeout). The change is low-risk, self-contained, and includes proper test coverage for the fix.

^{You can customize Macroscope's approvability policy. Learn more.}