claude-code - 💡(How to fix) Fix [BUG] Cygwin: CWD temp file path missing /cygdrive prefix [1 comments, 2 participants]

On Cygwin (Windows), the Claude Code shell integration layer writes a CWD-tracking temp file using the Windows-mapped path (e.g., /c/cygwin64/tmp/claude-xxxx-cwd) instead of the Cygwin-translated path (/cygdrive/c/cygwin64/tmp/claude-xxxx-cwd). Bash then fails to read the file and produces an error after every single Bash tool invocation: The Cygwin-translated path (/cygdrive/c/cygwin64/tmp/claude-xxxx-cwd) should be used and the error should not occur.

Error Messages/Logs

The error reported is:

TL;DR

The issue can be resolved by modifying the Claude Code shell integration layer to use the Cygwin-translated path instead of the Windows-mapped path for the CWD-tracking temp file.

Guidance

• Investigate the Claude Code shell integration layer to identify where the Windows-mapped path is being used and modify it to use the Cygwin-translated path.
• Verify that the Cygwin-translated path is correctly formatted as /cygdrive/c/cygwin64/tmp/claude-xxxx-cwd instead of /c/cygwin64/tmp/claude-xxxx-cwd.
• Test the modified Claude Code shell integration layer to ensure that the error no longer occurs after Bash tool invocations.
• Consider using Cygwin's cygpath command to convert Windows paths to Cygwin paths, if available.

Example

No code snippet is provided as the issue does not contain sufficient information about the implementation details of the Claude Code shell integration layer.

Notes

The solution assumes that the issue is caused by the incorrect path being used by the Claude Code shell integration layer. If the issue persists after modifying the path, further investigation may be necessary to identify the root cause.

Recommendation

Apply workaround: Modify the Claude Code shell integration layer to use the Cygwin-translated path, as this is the most likely cause of the issue and a workaround can be implemented without requiring an upgrade to a fixed version.