Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Code server disconnects after browser inactivity for a while

Open
#7,016 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
devtools, web-dev

Research direction

Start by reproducing the disconnect in code-server v4.16.1 on a SageMaker notebook with Chrome or Firefox after roughly 15 minutes of inactivity. Inspect the connection behavior and collect logs during the failure; done means the VS Code client and terminal remain responsive without requiring a browser refresh.

Written by the indexing model from the issue text.

Description

bug triage
Is there an existing issue for this?
  • I have searched the existing issues
OS/Web Information
  • Web Browser: Chrome, Firefox
  • Local OS: macOS, Windows
  • Remote OS: Amazon linux 2 (Sagemaker)
  • Remote Architecture: x86_64 GNU/Linux
  • code-server --version: code-server: v4.16.1, Code: 1.80.2
Steps to Reproduce
  1. launch code server on Sagemaker notebook instances
  2. Connect from local machine using Chrome, or Firefox
  3. When the go computer is idle (e.g. in screen saver mode) for a while (the duration is not consistent, but 15min should do), or when the browser is out of focus for a long time, the vscode client page gets disconnected: the file system is no longer responsive (we have a blue clock icon and a horizontal line that scrolls continuously, see screeshot); and the terminal no longer respond also
  4. Refreshing the browser page brings the connection back to normal
Expected

The vscode code client should not be disconnected when the computer has access to internet

Actual

Vscode client page gets disconneted when computer is idle or when browser is out of focus for a while

Logs

No response

Screenshot/Video

vscode-disconnection

Does this bug reproduce in native VS Code?

I did not test native VS Code

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?
  • I am using a secure context.
Notes

No response

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.