[Bug] Bash tool execution failing or non-functional

Found 3 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/15801
2. https://github.com/anthropics/claude-code/issues/17961
3. https://github.com/anthropics/claude-code/issues/17664

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

This started happening with the recent 2.1.53 update.

working around this locally

Manually rolling back to 2.1.52 with:

& ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 2.1.52

And disabling auto-update in ~/.claude/settings.json with:

"env": {
	"DISABLE_AUTOUPDATER": "1"
},

Same issue here. Windows 11 Home 10.0.26200, Claude Code 2.1.53. Every Bash tool call fails with EINVAL: invalid argument, open on temp file in AppData\Local\Temp\claude\. Write tool works fine to the same directory. Rolling back to 2.1.52 per the workaround.

I wonder if Anthropic releases its tools just like "huyak, huyak i v prodakshen"? Do they even test them themselves, or is it just pure vibe coding?! @bcherny
Updating is scary now; you never know what might break next?!

https://dev.to/kolkov/from-vibe-coding-to-agentic-engineering-what-karpathy-got-right-and-whats-missing-62e - Maybe it's worth learning how to work with a coding agent?!!

+1 same here - suddenly.

Bug Description

All Bash tool calls fail with EINVAL: invalid argument when Claude Code tries
to open the task output file. This makes it impossible to run any shell command
from within a Claude Code session.

## Environment

• OS: Windows 11 Pro 10.0.26200
• Claude Code version: 2.1.53
• Shell: Reproduced in Git Bash, CMD, and PowerShell (all fail identically)

## Error

Every Bash tool call — including trivial ones like claude --version — fails with:

EINVAL: invalid argument, open 'C:\Users<user>\AppData\Local\Temp\claude\D--Claude-Bn\tasks<random-id>.output'

## Steps to Reproduce

1. Run any Claude Code session on Windows
2. Attempt any Bash tool call (e.g. ls, pwd, claude --version)
3. Error fires immediately — command never executes

## What I Tried

• Deleted entire AppData\Local\Temp\claude\ directory → Claude Code recreates it, same error
• Restarted PC → same error
• Uninstalled and reinstalled Claude Code → same error
• Tested all three shells (Git Bash, CMD, PowerShell) → same error in all

## Key Diagnostic Finding

The temp directory exists with correct permissions (gf\mn:(I)(OI)(CI)(F)).
Node.js can write to the exact same path manually:

```powershell
node -e "const fs = require('fs');
fs.writeFileSync('C:\\Users\\<user>\\AppData\\Local\\Temp\\claude\\D--Claude-B\\tasks\\test.output', 'test');
console.log('OK');"
# Output: OK

This confirms it is not a permissions issue — Node.js itself can create .output
files at that path. The failure is specific to how Claude Code internally opens the
file (likely fs.open() with flags that are invalid on Windows).

Trigger

The issue started after a Claude Code session crashed mid-command (possibly after auto update?). It has persisted
through reinstalls and reboots, suggesting the bug is in the Claude Code binary's
file-open logic, not environmental state.

Expected Behavior

Bash tool calls should execute successfully as they did before the crash.
```

This started happening with the recent 2.1.53 update. working around this locally Manually rolling back to 2.1.52 with: & ([scriptblock]::Create((irm https://claude.ai/install.ps1))) 2.1.52 And disabling auto-update in ~/.claude/settings.json with: "env": { "DISABLE_AUTOUPDATER": "1" },

This was the fix for me. It definitly was the 2.1.53 update

Seriously, they should build a robust testing system!

@WangShiSoftware When multiple versions of a program are released a day, it always means something's wrong with the development company! It might be a alpha version, but this is already in production and costs a pretty penny annually!

@shawnm-anthropic Maybe the Anthropic company is changing something in its work or what?

Another work-around that may work long term:

Use /config then set Auto-update channel to stable

You may need to install an earlier version.

@shawnm-anthropic Fixed in 2.1.55.
But despite this, something needs to be done about testing before release. This is simply very unprofessional on your part!

An hour of my day gone. Crazy that Auto-update channel isn't set to stable by default.

@DingoDavid The whole problem is that Anthropic themselves don't know what's stable and what's not... It's a complete lottery! Whatever their agent wakes up on, that's what it'll be like!
For example, they fix the problem with task loss, but then it reappears in full force, leaving the agent motionless for several minutes until some timeout kicks in. So, I often have to ESC and restart from the same spot, and it immediately starts working as if nothing had happened!

Hi, thanks for reporting. We just released v2.1.55 which should fix this.

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.