VS Code Remote - Tunnels idle timeout question

What is the idle timeout for VS Code Remote - Tunnels server?

0 reputation · 26 Mar 2024, 14:23 UTC

82K views0

Goal

Determine the idle timeout that causes the VS Code Remote - Tunnels server to shut down when a tunnel is inactive, so that low‑traffic development workloads can rely on predictable server availability without incurring unnecessary compute costs.

Uncertainty

The extension’s documentation does not specify the timeout value, and no user‑exposed setting exists in the Settings UI. Reported observations vary, leaving the exact duration and any possible configuration method unclear.

What is the default idle timeout for the Remote - Tunnels server? Can the timeout be adjusted through a setting, environment variable, or command‑line flag?

2,039 following

Keep exploring this topic

Limiting VS Code Notification Noise Without Losing Critical Alerts

How to reduce VS Code notification noise while keeping critical alerts visible and addressing the lack of a snooze feature.

VS Code Local files.associations Setting Not Propagated to Remote‑SSH Host

Investigates why a custom files.associations setting works locally but fails when the same VS Code workspace is accessed via Remote‑SSH in a production environment.

Always-On repl idle timeout behavior for idle TCP connections

Exploring whether Replit’s Always-On idle timeout treats idle open TCP connections as activity or as no network activity, impacting persistent socket‑based apps.

Idle Connection Timeout vs. Proxy Multiplexing: Trade‑off for Mitigating Memcached Connection Pool Exhaustion

Choosing between client‑side idle timeout and a multiplexing proxy to mitigate memcached connection pool exhaustion under bursty traffic while balancing latency.

What is the idle timeout for VS Code Remote - Tunnels server?

Goal

Uncertainty

0 answers

Your perspective belongs here.

0 question comments