write_file tool: parameter name mismatch between docs (absolutePath) and validation (paths array) causes 100% failure rate

[mesbahuddin]

Summary

Bug Report: write_file tool

Every call fails with:

Error: The "paths[1]" argument must be of type string. Received undefined

Attempted (all failed)

• {"absolutePath": "H:/f.c", "content": "x"}
• {"filePath": "H:/f.c", "content": "x"}
• Both parameters together
• Different drives, paths, content lengths

Impact

Completely unusable for an entire 4-hour session. All file creation had to use edit_file + echo workarounds.

Root Cause

The validation checks for a paths array parameter, but the documented API uses singular absolutePath. Internal validation and documented interface are out of sync.

Workaround

edit_file works fine. For new files: echo x > file in shell_command, then edit_file to overwrite.

Expected Behavior

.

Actual Behavior

.

Steps to reproduce the issue

.

Command Code Version

Microsoft Windows [Version 10.0.26200.8457]
(c) Microsoft Corporation. All rights reserved.

H:\ProgrammingWorkspaces\Programming_32Blit\32Blit_Workspace_C>

Operating System

Windows

Terminal/IDE

Unknown

Shell

cmd.exe

Additional context

No response