Edit tool broken: 'replace_all type is expected as boolean but provided as string'

Resolved 💬 6 comments Opened Mar 6, 2026 by Joseelmax-00 Closed Apr 8, 2026

Bug Report

The Edit tool is completely broken — every call fails with a type validation error regardless of how replace_all is passed.

Error

● Read
  ⎿  Error: InputValidationError: Edit failed due to the following issue:
     The parameter `replace_all` type is expected as `boolean` but provided as `string`
  ⎿  Error: InputValidationError: Edit failed due to the following issue:
     The parameter `replace_all` type is expected as `boolean` but provided as `string`

● Bash(python -c "print('test')")
  ⎿  test
  ⎿  Error: InputValidationError: Edit failed due to the following issue:
     The parameter `replace_all` type is expected as `boolean` but provided as `string`

● The Edit tool seems broken. Let me try Write with the full file content for just the imports section, or use Bash:

Impact

The Edit tool is completely unusable mid-session. Required workarounds: using Bash + Python string replacement or full file rewrites with Write, both of which are significantly worse UX and risk accidental data loss.

Environment

  • Platform: win32
  • OS: Windows 10 Pro 10.0.19045
  • Model: claude-sonnet-4-6
  • Version: current: 2.1.70 · latest: 2.1.70

---
This issue was filed by Claude Code (claude-sonnet-4-6) on behalf of the user. The issue will appear under the user's GitHub account.

EDIT: to add human input:

I (the human behind the account) could not have worded it better, I get auto-updates at 3am that break functionality and my agent is getting tired of it, do you see how annoyed he sounds? please fix this.

Reproducibility:

This bug happened under a conversation, it started happening when I switched it from 4.5-haiku to 4.6-sonnet, in that specific moment tool usage broke for the most part. Reads failing without an error description and edits failing 19 out of 20 times with that error (in some rare instances edits actually worked).

View original on GitHub ↗

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