[BUG] VS Code Extension Error: "Received message_stop without a current message"

Resolved 💬 5 comments Opened Mar 30, 2026 by siddhjagani Closed Jun 13, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When using Claude Code via the VS Code extension, it throws the error:

"Received message_stop without a current message"

This happens during normal execution (e.g., asking it to review a codebase and perform a QA test). The same workflow works perfectly in the CLI.

What Should Happen?

The VS Code extension should:

Maintain correct message lifecycle (start → stream → stop)
Execute tasks identically to the CLI
Handle LSP/tool calls without validation errors

Additionally, can add in system prompt:
DO not include message_stop at the mid of the session.

Error Messages/Logs

Received message_stop without a current message

Steps to Reproduce

  1. 1. Open VS Code with Claude Code extension installed
  2. Open any project
  3. Run prompt: "Review this codebase" or ANY

Observe:

  • Partial response starts
  • Then error appears: message_stop without a current message

<img width="464" height="482" alt="Image" src="https://github.com/user-attachments/assets/edaa12e6-4d98-4a67-8312-b9b16f5c1379" />

Claude Model

Other

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.86

Claude Code Version

2.1.87 (Claude Code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗