Copilot edit predictions broken in Zed 0.219.4 - does v0.220 fix it?
After updating Zed to v0.219.4+stable on macOS 26.2 (aarch64), GitHub Copilot inline edit predictions became unreliable and most of the time do not show up at all, even though the log shows the Copilot language server starting and the client authenticating successfully. Is this a known regression and what is the fix?
Originally asked on GitHub: https://github.com/zed-industries/zed/issues/46880
4 answers
Reported as fixed: the issue was closed as completed. On 2026-01-15 a Zed maintainer said the problem should be fixed in v0.220, and on 2026-02-08 a commenter said it seemed fixed now and closed the issue. No one in the thread confirmed the fix by upgrading and retesting, so treat the upgrade as the likely resolution rather than a verified one.
The reporter's log shows the Copilot language server started normally (Node 25.2.1 satisfied Copilot's requirement of >= 20.8.0) and the client authenticated, so this is not an auth or setup failure. The root cause is not confirmed; the reporter speculated about the Next Edit Suggestion implementation from PR #44486, but that is only a guess. Other users agreed edit predictions were unusable in Go and JavaScript before the fix.
The only resolution path stated in the thread is to update Zed to v0.220 or later and retry inline edit predictions. No settings changes, config edits, or CLI flags were mentioned.
If predictions still do not appear after upgrading, confirm Zed is really on v0.220+ and check Zed.log for an 'lsp' line that starts copilot-language-server; that check is general advice, not a workaround tested in this thread.
Did this work for you?What a GitHub user tried on GitHub (Didn't work)
Installed Zed v0.219.4+stable on macOS 26.2 (aarch64) and tried to trigger inline edit predictions; predictions were unreliable or most of the time did not appear. The log showed the Copilot language server starting and the client authenticating successfully.
Source: https://github.com/zed-industries/zed/issues/46880 (opens external site)
Did this work for you?What @osiewicz tried on GitHub (Outcome unclear)
A Zed maintainer stated the issue should be fixed in v0.220, implying that upgrading to that version was the remedy; no one in the thread reported actually testing that version.
Source: https://github.com/zed-industries/zed/issues/46880#issuecomment-3754723668 (opens external site)
Did this work for you?What @dnlsndr tried on GitHub (Outcome unclear)
A commenter said the problem seemed fixed now and closed the issue as completed, without describing any reproduction, version, or confirmation steps.
Source: https://github.com/zed-industries/zed/issues/46880#issuecomment-3868548229 (opens external site)
Did this work for you?