Why VS Code GitHub Copilot Stops Auto-Completing After 10 Minutes

Official documentation checked October 14, 2026.

If Copilot stops offering ghost text after about ten minutes, record the pattern rather than assuming a built-in idle cutoff. The current documentation cited here does not establish a universal, hardcoded ten-minute Copilot timeout across plans. A deliberate snooze, disabled language, connection problem, account message, or host environment stopping can require different action.

A Ten-Minute Pattern Is a Symptom to Measure

VS Code provides a deliberate Snooze control. Each click increases the snooze period by five minutes, and Cancel Snooze resumes inline suggestions. This documented control can account for a ten-minute pause if it was selected twice. It does not establish a separate idle timer triggered by the absence of typing. See inline suggestions and snooze.

Automatic requests can also be suppressed when VS Code treats the connection as metered. An explicit Trigger Inline Suggestion request is still supported in that state. Check this distinction before changing network settings; an organization may have a reason for its configuration.

Rate or usage messages need their own interpretation. GitHub documents service rate limiting separately from plan allowances. A failed request at a repeatable time does not identify either condition without its message. There is no reason to infer a plan-specific icon or promise immediate recovery. See Copilot rate and authentication troubleshooting.

How to Restore Suggestions and Test the Pattern

1. Save and capture the starting state. Note the current time, VS Code and Copilot versions, active profile, language, and whether the editor is local or connected remotely. Preserve the function you are editing.
2. Read the Copilot Status Bar menu. Check for a snooze, disabled inline suggestions, sign-in request, or other message. Cancel an unintended snooze, or enable suggestions for the intended language if you disabled them accidentally. Retain other language restrictions.
3. Make one explicit request. In a small non-sensitive source file, place the cursor after a clear comment and run Trigger Inline Suggestion. If this works while typing produces no automatic requests, investigate the automatic-suggestion controls and metered-connection state. Do not treat opening the additional-suggestions pane as a guaranteed session reset.
4. Record the later failure. If the problem returns, write down the exact time and whether you were actively editing, idle, or waking the computer. Check whether the editor and, for a remote session, its terminal and connection still work. Repeat only enough to establish a reproducible pattern.
5. Inspect the matching diagnostic entry. Open View > Output and select the relevant Copilot channel. Look around the failed request’s timestamp, rather than using an assumed “Show Logs” command. See Copilot log collection.
6. Reload once if needed. Save files before Developer: Reload Window and then repeat the same test. Avoid replacing the github.copilot.enable map with a boolean: it is a language map, and an indiscriminate replacement can remove deliberate restrictions.

If Copilot Still Stops After You Resume

An authentication error appears: confirm the intended account has Copilot access. GitHub documents signing out through Accounts, reloading, and signing back in for an actual authentication problem. This is more targeted than deleting stored credentials. Follow the official sequence.

A network failure appears: use GitHub Copilot: Chat Diagnostics when available to identify failed connectivity checks, and compare them with the timestamped Output messages. A successful report covers only its tested connections. Follow your administrator’s proxy/firewall guidance instead of bypassing certificate verification or repeatedly forcing requests. See VS Code AI diagnostics.

The remote editor stops responding: check the host environment separately. For Codespaces, idle timeout stops the codespace and is a different lifecycle rule from a Copilot snooze. Reconnect to the intended existing codespace and inspect its state and cost settings before changing a timeout. See Codespaces lifecycle.

Snooze, Disabled Suggestions, and Connection Failures

A keystroke simulator is not a documented remedy for an assumed Copilot timer. Keep a redacted reproduction with versions and timestamps instead. If the pattern remains unexplained, that evidence lets support investigate a client or network problem without masking it with a keepalive.