Terminal becomes unusable after prolonged session

[stirby]

An enterprise customer has reported that a long-running VSCode session connected via our extension leads to a slow and unfavorable experience in the integrated terminal. After about 24 hours, the terminal is unusable, seemingly due to networking degradation. This customer compared the native Remote SSH extension from VSCode and found no issues, confirming this problem is on our end.

In the degraded terminal, keystrokes take seconds to register, revert, and drop. It is likely a networking issue.

This is a top priority, impacting many enterprise users.

For the Coder team: see the internal issue for a recording of the behavior.