[BUG] Claude Code never invokes tools, only returns text responses (Windows 11, v2.1.123, acceptEdits mode)

Resolved 💬 1 comment Opened Apr 29, 2026 by polatmurat Closed May 31, 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?

Windows 11, Node v24.15.0, using nvm
acceptEdits mode is enabled
node -e "fs.writeFileSync(...)" works
Claude Code does not make tool calls, it only returns text
Same issue in both CLI and VS Code extension

---

I have tested this issue across multiple environments on Windows:

WSL
Command Prompt (cmd)
PowerShell
Windows Terminal
VS Code with the Claude Code extension

The behavior is consistent in all cases — Claude Code does not trigger tool calls and only returns text.

However, when using the same setup on macOS, everything works as expected and tool calls are executed properly.

I am currently using a company-managed Windows machine. Could there be any restrictions (e.g., security policies, permissions, antivirus, or system configurations) that might be preventing tool execution?

What Should Happen?

When running Claude Code with acceptEdits mode enabled, the system should execute tool calls instead of only returning text responses.

Error Messages/Logs

no error has shown

Steps to Reproduce

Claude Code returns code as plain text but does not execute any tool calls or apply changes to the file system

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.123 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗