[BUG] Claude VS Code extension doesn't respond if setting claudeProcessWrapper
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 VS Code extension v2, the claudeCode.claudeProcessWrapper option doesn't work for me with the default non-terminal mode.
For instance, even when setting claudeCode.claudeProcessWrapper to a direct path of non-wrapped Claude binary, /Users/nekketsuuu/.volta/bin/claude, Claude keeps showing waiting messages like "Marinating..." after sending a question.
It may be interesting that, after closing the extension pane and re-opening the pane, it has a record for successful response in its "Past Conversations" history. So the extension seems to have an issue around displaying its response, I guess.
What Should Happen?
The response will be shown as usual.
Error Messages/Logs
I can't find any logs about this. I'd appreciate if anyone suggests how to show internal logs of the VS Code extension.
Steps to Reproduce
- Install Claude Code VS Code extension v2.
- Set up like below:
``
"claudeCode.claudeProcessWrapper": "/Users/nekketsuuu/.volta/bin/claude",
"claudeCode.environmentVariables": [
{
"name": "CLAUDE_CODE_USE_BEDROCK",
"value": "1"
}
],
"claudeCode.useTerminal": false
Actually I'd like to choose my wrapper command for claudeProcessWrapper, but I found that this issue still happens when I set it to the plain claude command.
- Open the Claude Code VS Code extension pane.
- Ask something.
- It will only show several waiting messages.
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
N/A
Claude Code Version
2.0.28 (Claude Code)
Platform
AWS Bedrock
Operating System
macOS
Terminal/Shell
Other
Additional Information
VS Code extension: anthropic.claude-code 2.0.28
Related issue: https://github.com/anthropics/claude-code/issues/10491
7 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I found that this was caused by my misconfiguration of claudeProcessWrapper.
First, I found that the extension logs can be seen by: Command + Shift + P -> "Developer: Open Extension Logs Folder" -> "Anthropic.claude-code/Claude VSCode.log". It has a log for the exact command which is launched by the extension, and it turned out that claudeProcessWrapper is used as a prefix for
claude, likewrapper-command claude --any-other-options. The actual command is like below:So, after I modified
claudeCode.claudeProcessWrapperto follow this rule, the extension started to work properly.@nekketsuuu Looks like behaviour is not consistent between platforms. On Windows I get
It looks like a different problem from mine. The error message shows that a binary specified by claudeCode.claudeProcessWrapper is not an executable. For instance, I needed to specify the absolute path to the wrapper.
If your problem isn't resolved, I recommend to open a new issue.
I'm seeing similar behaviour, but on Linux. I'm running Claude Code on an Ubuntu server and using the VS Code extension on my desktop. It worked at first, but now the Claude panel in VS Code just sits on “marinating…” / waiting after I send a prompt and never shows a reply, even though it sometimes appears in the history after I close/reopen the panel. At the same time, if I use Claude Code in the integrated VS Code terminal instead, the terminal output starts visually glitching (flickering / rapid redraw). No clear error logs.
That bug is different from this issue's one according to the behavior. I recommend to search other issues or open a new issue.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.