How to configure GitHub Copilot inline suggestions and keyboard shortcuts
GitHub Copilot installed in VS Code
What this does
GitHub Copilot's inline suggestions appear automatically as code is typed. Customizing these settings controls trigger behavior, completion depth, and which languages are enabled. Keyboard shortcuts allow accepting, dismissing, and cycling through suggestions without removing hands from the keyboard. Configuring both streamlines the editing workflow and reduces friction during AI-assisted coding.
Steps
- Open VS Code Settings: use File → Preferences → Settings or press
Ctrl+,. - Type "copilot" in the search bar to filter Copilot-related options.
- Under Extensions → Copilot, toggle "Enable Inline Suggestions" to the desired state.
- Locate the Completion: Trigger setting and adjust
inlineSuggest.enableif needed for fine-grained control. - Open the Keyboard Shortcuts editor via File → Preferences → Keyboard Shortcuts or
Ctrl+K Ctrl+S. - Search for "copilot" to list all Copilot-bound commands such as Accept Inline Suggestion, Reject Inline Suggestion, and Show Copilot Chat.
- Click the pencil icon next to any command and assign a keybinding by pressing the desired key combination.
- Test a binding by opening a code file, triggering a suggestion, and pressing the assigned accept shortcut to insert the completion.
Verification
code --get-keybindings | grep -i copilot
Expected output: one or more lines showing "acceptInlineSuggestion" and "rejectInlineSuggestion" with their current keybindings.
Common failures
- Suggestions not appearing: Ensure
github.copilot.enableis set totruein the workspace or user settings JSON. - Keybinding conflict: VS Code warns when a shortcut is already assigned; resolve by choosing a different binding or removing the conflicting one.
- Language-specific suppression: Check that the current file's language ID is not listed under
copilot.statusBar.backgroundorinlineSuggest.languagesexclusions.
Operator checkpoint
Before treating this as solved, write down the local runtime, model or package version, hardware/backend if relevant, and the verification output. This keeps the guide useful as a Will-It-Run style decision instead of a one-off command transcript.