Diagnostics & Recovery

Troubleshooting Center

Verify the editor, Node.js runtime, extensions, language servers, and workspace one signal at a time.

This page is the executable diagnostic tree. For background explanations and configuration guidance, see the FAQ.

GitHub Issue Tracker

Core Diagnostic Commands

:CocInfo

Show version and log information for a bug report.

:CocOpenLog

Open coc.nvim’s log file.

:CocCommand workspace.showOutput

Open an extension or language-server output channel.

:CocRestart

Restart the coc.nvim service.

Common Symptoms

Resolution Guide

coc.nvim service does not start after installation

30-Second Quick Verification

Neovim users can run `:checkhealth`; in either editor check `:version`, `:echo exepath("node")`, and `:!node --version`.

Probable Cause

The editor or Node.js executable seen by Vim may be older than the current requirements: Vim 9.0.0438+, Neovim 0.8.0+, and Node.js 22.15.0+.

Step-by-step Solution

1Upgrade Vim, Neovim, or Node.js when the reported version is below the documented requirement.
2If the shell has a newer Node.js, make sure Vim inherits that PATH or set `g:coc_node_path` to the intended executable.
3Restart the editor, run `:CocInfo`, and inspect `:messages` if initialization still fails.

Commands to Test

Still stuck?

Pre-formatted GitHub Issue Template

issue-report.md

1	### [Runtime] coc.nvim service does not start
2
3	### Environment (fill in from your editor; do not guess)
4	- Editor: Vim or Neovim and version: [fill in]
5	- coc.nvim version/branch/commit from :CocInfo: [fill in]
6	- Node.js version and executable path from :CocInfo or :!node --version: [fill in]
7	- Extension and/or language server name, version, and command: [fill in if applicable]
8
9	### Problem
10	coc.nvim service does not start after installation
11
12	### Minimal reproduction (smallest file, filetype, config, and exact steps)
13	[fill in; write "Not collected" if unavailable]
14
15	### Diagnostics (paste only the relevant output)
16	- Output of :CocInfo:
17	[paste here]
18	- Relevant :CocOpenLog, :CocPrintErrors, or workspace.showOutput output:
19	[paste here]
20
21	### Additional details for this symptom
22	## Output of `:version`
23
24	## Output of `:!node --version` and `:echo exepath("node")`
25
26	## Output of `:CocInfo`, `:messages`, or Neovim `:checkhealth`
27
28
29	### Redaction checklist before posting
30	- [ ] Replace home, workspace, and project paths plus usernames with <PATH> (for example /Users/<USER>/project or C:\Users\<USER>\project).
31	- [ ] Replace tokens, API keys, passwords, cookies, private keys, and Authorization headers with <REDACTED>.
32	- [ ] Remove private proxy or registry credentials and private hostnames/IP addresses; keep only the relevant public error or setting name.
33	- [ ] Review language-server commands, arguments, and environment variables for --token, --api-key, --password, URLs, and paths before posting.
34	- [ ] Share a minimal reproduction and small config excerpt only; do not paste project source code, a whole private repository, or unrelated log history.