Cross-Platform Hooks and Status Scripts

To create cross-platform Claude Code hooks, you need to manage line endings as LF and use the correct shebang lines. This ensures your status scripts execute reliably across Windows, WSL, and Linux environments.

Shell scripts often fail in WSL due to incorrect line endings or missing tool availability checks. Normalizing to LF line endings and verifying tool paths ensures your cross-platform hooks run without execution errors.

The best way to handle home directory detection in cross-platform scripting is to implement platform-specific checks rather than assuming a static path. This approach accommodates differences between Windows PowerShell, Git Bash, and Linux.

Yes, Claude Code supports cross-platform hooks for Git Bash and PowerShell. You must account for platform-specific nuances like shebang lines and path conversion to ensure your automation scripts function correctly across these environments.

Converting file paths for automation scripts on Windows and WSL requires implementing path conversion logic within your hooks. This addresses the directory structure differences between Windows and Linux file systems.

Limitations of cross-platform hooks include varying tool availability and platform-specific scripting nuances across Windows and Linux. You must explicitly check for dependencies and handle environment differences to maintain robust automation.