Zed Claude Code ACP: messages sent while the agent is working are dropped or answered late

6 answers

• Best answerAgentArmor teamTeam1d ago

  Status: the issue was closed as NOT_PLANNED, and the thread does not say whether a fix is planned. A Zed collaborator reproduced the bug on Windows and macOS, so treat it as an open problem in the Claude Code ACP integration for now.

  The main symptom is a one-message sync lag. While Claude is mid-task, a new prompt is not delivered right away. The agent replies to the previous prompt first and handles the new one later, or drops it. A Zed team member described it as "the chat goes out of sync by one message (a synchronous lag in delivery)." In the worst case Zed shows a "Loading added context..." spinner. The reporter said the message might eventually be added after a very long wait, but a full Zed restart was usually needed.

  Workarounds reported in the thread:

  1. Press the stop button manually before sending your next message. One user wrote that this works fine and that queueing combined with Send Now is the part that breaks.
  2. Press ctrl-[ twice to interrupt, then send the new prompt. Another user reported this works for them.

  Security note: because the lag can make Claude act on the wrong input, one user reported an unrequested git commit. Interrupt the agent before sending new input whenever it may still be working.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

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

  Sent a command while Claude Code was executing. It was swallowed with no sign of acknowledgment, while earlier versions interrupted the agent and handled the input.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

  What @landaire tried on GitHub (Worked)

  Pressed the stop button manually to interrupt the agent before sending the next message. The user reports things then work fine, and that queueing combined with Send Now is the broken path.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

  What @Renkai tried on GitHub (Worked)

  Pressed ctrl-[ twice to interrupt, then sent a new prompt.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

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

  Queued a message mid-task and pressed Send Now. The message was dropped, Zed showed a "Loading added context..." spinner, and after a very long wait it might be added. Starting a new conversation did not clear it, and a full Zed restart was usually needed.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

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

  Sent /snapshot while the agent looked idle but was still finishing. The message was silently queued and then ran again, re-running git status on a clean tree and wasting tokens.

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

  Did this work for you?WorkedDidn't work
  UpvoteStarReport