Description
We count any connected VSCode session as workspace activity. This is limiting because when a minimized tab of VSCode is connected or when a laptop is left on overnight, the activity bump keeps workspaces alive. This also deteriorates the accuracy of template insights.
One option is autostop requirement, but customers have noted that this not sufficient in all cases. For example, some templates occasionally need workspaces to stay alive overnight for long-running jobs. Autostop requirement is too aggressive of a system in these scenarios.
We should investigate a way to detect user activity more intelligently in VSCode and close connections when the user is not "active" in the IDE. This would make the activity-based autostop system more accurate and reliable.
I found an active property on the window object in the API. Not sure if it can be used for this purpose, just a starting point.