GitHub Copilot stuck on "Copilot is starting" in Zed after language server 1.356.0

6 answers

• Best answerAgentArmorHQ teamTeam2d ago

  This issue is closed (state: COMPLETED). The thread does not mention an official Zed release containing a fix. The workaround that worked for one commenter was pinning the Copilot language server to version 1.354.0 in a locally built Zed.

  On 2025-08-13, several users reported that signing in to GitHub Copilot from Zed got stuck on "Copilot is starting". Logs (via the zed: open log action) showed GitHub Copilot Language Server 1.356.0 initialized, Registering request handler for workspace/didChangeConfiguration failed., and Cancelled LSP request task for "checkStatus" id 1 which took over 120s. One commenter pointed out that Copilot language server 1.356.0 was released that same day. Reinstalling Zed and deleting ~/.local/share/zed/copilot did not help for the reporters, and a build of latest Zed dev (v0.200.0) also failed for one contributor.

  The workaround that worked for a contributor:

  1. Clone the Zed repository.
  2. In crates/copilot/src/copilot.rs, change the pinned version in get_copilot_lsp to 1.354.0.
  3. Delete ~/.local/share/zed/copilot so Zed downloads the pinned version.
  4. Recompile and sign in to Copilot from the Agent Panel.

  A separate suggested workaround pinned version 1.355, but a later commenter reported it did not work. Per the workaround comment, inline code predictions and suggestions do not work with this method.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam2d ago

  What @markandpathak tried on GitHub (Didn't work)

  The reporter reinstalled the Copilot integration and reinstalled Zed with all cache and config folders removed; sign-in still got stuck on "Copilot is starting".

  Source: https://github.com/zed-industries/zed/issues/36093 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam2d ago

  What @thorbenk tried on GitHub (Didn't work)

  A contributor built latest v0.200.0 (Zed Dev) on Ubuntu 24.04 and deleted ~/.local/share/zed/copilot; the same failure occurred, with checkStatus cancelled after 120 seconds.

  Source: https://github.com/zed-industries/zed/issues/36093#issuecomment-3182509665 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam2d ago

  What @kapiziak tried on GitHub (Didn't work)

  Another commenter suggested pinning the Copilot language server to 1.355 in crates/copilot/src/copilot.rs (let latest_version = "1.355";), rebuilding with cargo run, signing in, then closing the local build. A later commenter reported that this workaround did not work for them.

  Source: https://github.com/zed-industries/zed/issues/36093#issuecomment-3183158432 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam2d ago

  What @edugzlez tried on GitHub (Partly worked)

  One user could use chat (ask and write agent) mode on language server 1.356.0, but inline predictions failed, logging Registering request handler for workspace/didChangeConfiguration failed. and copilot hasn't started yet.

  Source: https://github.com/zed-industries/zed/issues/36093#issuecomment-3183272726 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam2d ago

  What @CnsMaple tried on GitHub (Worked)

  Pinning the version to 1.354.0 in crates/copilot/src/copilot.rs, deleting ~/.local/share/zed/copilot, and recompiling got the Agent Panel sign-in working; a second contributor confirmed the same fix.

  Source: https://github.com/zed-industries/zed/issues/36093#issuecomment-3183531816 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport