-
Notifications
You must be signed in to change notification settings - Fork 39
Labels
Description
VS Code's default connection timeouts create a poor developer experience for Coder users.
Current Workflow Pain Points:
- Developers expect to return to their work seamlessly without losing state
- Instead, they must manually "Reload Window" every morning
- All unsaved changes and runtime state are lost during the forced reload
Technical Root Cause
VS Code used to have a hardcoded timeouts (3-hour ReconnectionGraceTime) that terminate server sessions when connections are lost for extended periods. This conflicts with Coder's cost-optimization model, where workspaces may be offline for 6+ hours overnight.
With the introduction the ReconnectionGraceTime setting, we can overwrite that value when establishing a connection to remote. If the value is already modified then we can possibly skip that.
Reactions are currently unavailable