A VS Code user gets GitHub Copilot ghost text in TypeScript but none in Markdown or in some repository files — which settings and policies explain it?
answer
- off by language, off by policy
- default map skips markdown
- status-bar icon struck through
- Snooze adds five minutes
- metered stops automatic requests
basics
~20 sCheck the switches in order: github.copilot.enable turns ghost text off for markdown, plaintext and scminput by default; a content exclusion blanks specific files and strikes through the status-bar icon; Snooze or a metered connection pauses automatic suggestions.
solid answer
~40 sStart with `github.copilot.enable`, the per-language map: VS Code's default is `{ "*": true, "plaintext": false, "markdown": false, "scminput": false }`, so Markdown has no ghost text until you add `"markdown": true`. Files missing suggestions inside one repository on a Business or Enterprise seat point to a **content exclusion** set by a repository admin or organisation owner: the Copilot status-bar icon shows a diagonal line, and its tooltip names the setting. If everything went quiet, look for **Snooze** (each click adds five minutes; **Cancel Snooze** ends it) or a **metered connection**, where VS Code starts no new automatic requests but **Trigger Inline Suggestion** still works. Thin or missing suggestions can also come from a **Suggestions matching public code** policy set to Block, which discards matches.
code
json · 8 lines{
"github.copilot.enable": {
"*": true,
"plaintext": false,
"markdown": true,
"scminput": false
}
}go deeper
Recall that ghost text can be off per language, and that Markdown and plain text are off in VS Code's default settings.
Explain each switch and its scope: the per-language map, content exclusion and its status-bar sign, Snooze, metered connections and the public-code filter.
Run the diagnosis by matching the scope of the silence to the scope of a switch, and know which switches belong to the developer and which to repository or organisation owners.
Decide which languages and paths a team turns off on purpose, and how exclusions and the public-code policy are explained so silence is not mistaken for an outage.
## Why the symptom splits by file When GitHub Copilot ghost text appears in some files but not others, the cause is almost never the model. VS Code and GitHub expose several independent **switches**, and each one has a different **scope**: a language, a file or path, a time window, or the network. Matching the scope of the silence to the scope of the switch finds the cause quickly. | Scope of the silence | Likely switch | Where it is set | |---|---|---| | Every file of one language | `github.copilot.enable` | VS Code settings | | Specific files or paths in a repository | **Content exclusion** | Repository, organisation or enterprise settings on GitHub | | Everything, for a while | **Snooze** | Copilot menu in the status bar | | Everything automatic, on this network | **Metered connection** | VS Code's view of your network | | Fewer or no suggestions, unevenly | **Suggestions matching public code** set to Block | Account or organisation policy | | Everything, always | Completions disabled, or `chat.disableAIFeatures` | Configure Inline Suggestions dialog, settings | ## The per-language map `github.copilot.enable` maps VS Code language identifiers to `true` or `false`; `*` covers every language not listed. VS Code's AI settings reference gives its **default**: - `"*": true` - `"plaintext": false` - `"markdown": false` - `"scminput": false` So a fresh install has **no ghost text in Markdown** — that is a default, not a fault. Add an entry to turn it on (see the example). The status-bar Copilot menu offers the same toggle for the **active editor's language**, so a colleague may have switched a language off with two clicks and forgotten. ## Content exclusion On **Copilot Business** or **Enterprise**, repository administrators, organisation owners and enterprise owners can exclude files from Copilot. For an excluded file: 1. Copilot gives **no inline suggestions** in it. 2. Its content does **not inform** suggestions in other files. 3. The Copilot **status-bar icon has a diagonal line** through it; hovering shows which settings applied the restriction. Exclusions are configured on GitHub by repository administrators, organisation owners or enterprise owners, so the fix, if one is warranted, lives with them rather than in your VS Code settings. ## Pauses that look like outages - **Snooze**: the Copilot status-bar menu's **Snooze** button pauses all inline suggestions, adding **five minutes** per click; **Cancel Snooze** — or the **Cancel Snooze Inline Suggestions** command — resumes them. - **Metered connections**: when VS Code treats the connection as metered, Copilot starts **no new automatic** ghost-text or next-edit requests; requests in flight finish. Run **Trigger Inline Suggestion** (default `Alt+\`, `Option+\` on macOS) to ask for one explicitly. This applies only to the built-in Copilot provider. ## Global switches and the public-code filter - The **Configure Inline Suggestions** entry in the title-bar Chat menu opens a dialog with **Enable Completions** and **Disable Completions**. - `chat.disableAIFeatures` (default `false`) disables built-in AI features, inline suggestions included. - GitHub checks each suggestion against public code. With the **Suggestions matching public code** policy set to **Block**, matches are discarded; GitHub's how-to warns this duplication detection can leave you with limited or no suggestions. ## Settings that look like silence Some settings do not turn suggestions off but can make them seem missing: - `editor.inlineSuggest.minShowDelay` — milliseconds to wait before showing an inline suggestion, default `0`. A large value copied from someone's settings makes ghost text appear late enough that a fast typist never sees it. - `editor.inlineSuggest.showToolbar` — default `"onHover"`; changing it hides or shows the toolbar, not the suggestion. - `github.copilot.nextEditSuggestions.enabled` — turns off **next edit suggestions** only; ghost text is governed by `github.copilot.enable`, so the two can disagree. ## A diagnosis order that works 1. Is the silence one **language**? Read `github.copilot.enable`. 2. Is it certain **files**? Look at the status-bar icon for the diagonal line. 3. Is it **everything**? Check Snooze, the metered state, the Enable/Disable Completions choice and `chat.disableAIFeatures`. 4. Are suggestions merely **sparse**? Ask which public-code policy applies to your account or organisation.
- You turned Markdown on in `github.copilot.enable`, but one docs folder still gets nothing and the status-bar icon is struck through. What now?That folder is under a Copilot content exclusion. Hover the icon to see which setting applied it — repository, organisation or enterprise. Exclusions are configured on GitHub, not in VS Code; if the exclusion is wrong, ask the repository administrator or organisation owner who configured it.
- On a train's metered Wi-Fi, ghost text stopped appearing. Is Copilot broken?No. When VS Code treats the connection as metered, Copilot starts no new automatic ghost-text or next edit suggestion requests, while requests already in progress finish. Run **Trigger Inline Suggestion** from the Command Palette, or its shortcut, to request one explicitly.
- Copilot ghost text is on for every language by default, Markdown included.
- A developer can lift a repository's Copilot content exclusion from their own VS Code settings.
- Snooze turns inline suggestions off until you re-enable them in settings.
- On a metered connection Copilot cannot produce any inline suggestions at all.
- Missing suggestions in some files mean the completions model needs changing.