Claude Code cannot be used in a Windows environment

[kevintsai1202]

App Version

3.23.7

API Provider

Anthropic

Model Used

Claude 4 Sonnet

Roo Code Task Links (Optional)

Currently, Claude Code supports the Windows environment, but an error occurs when using Roo Code set as the provider

🔁 Steps to Reproduce

1. Set Claude Code as the Provider
2. Use the Claude 4 Sonnet model
3. Input the question

💥 Outcome Summary

Command failed with ENAMETOOLONG: claude -p --system-prompt

📄 Relevant Logs or Errors (Optional)

[dosubot]

This error is almost certainly caused by Windows' strict command length limits, which are much lower than on Linux or macOS. Roo Code builds the system prompt dynamically, and if you have a large custom system prompt (for example, in a .roo/system-prompt-{mode-slug} file) or extensive custom instructions, the resulting command can easily exceed Windows' maximum allowed length for a shell command, triggering ENAMETOOLONG. This isn't directly addressed in the official docs, but the way Roo Code constructs prompts and passes them to the provider makes this a likely culprit docs.

Try removing or shortening any custom system prompt overrides and minimizing custom instructions. Test with the default system prompt (by deleting or renaming any .roo/system-prompt-* files) to see if the error goes away. If you can, share the full command or prompt being passed—this will help confirm if length is the issue.

There’s no documented workaround for this in Roo Code, so keeping prompts concise is the best way to avoid hitting this Windows limitation.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[roomote]

PR #5632 has been created to address this issue: #5632

[daniel-lxs]

Closing as duplicate #5042

[roo-code-preview]

I investigated this issue and found that the Windows ENAMETOOLONG error has already been resolved in the current codebase. The fix is implemented in src/integrations/claude-code/run.ts where:

1. Windows is detected using os.platform() === "win32"
2. For Windows: both system prompt and messages are sent via stdin to avoid the 8191 character command line limit
3. For other platforms: system prompt is sent via command line args and messages via stdin

The implementation correctly addresses the root cause mentioned in the original issue. While PR #5632 was closed due to conflicts, the fix appears to have been integrated through other means.

If you are still experiencing this issue with the latest version, please let me know and I can investigate further.