From 7ac5412c97840e50ce4946d0a608f90c060f93fc Mon Sep 17 00:00:00 2001 From: catlog22 Date: Thu, 16 Oct 2025 10:39:40 +0800 Subject: [PATCH] docs: update Windows path format guidelines for MCP and Bash compatibility MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Clarified path format requirements: - MCP tools require double backslash format (D:\path) - Bash commands support forward slash (D:/path) or POSIX (/d/path) - Added quick reference for common conversions 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- CLAUDE.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index e9481241..2a98f344 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -72,9 +72,11 @@ For all CLI tool usage, command syntax, and integration guidelines: ## Platform-Specific Guidelines -### Windows Path Conversion for Bash Commands -- **Windows paths** must convert to Git Bash format: `C:\path` → `/c/path`, `D:\path` → `/d/path`, `\` → `/` -- **Relative paths** (starting with `.` or `..`) require no conversion +### Windows Path Format Guidelines +- **MCP Tools**: Use double backslash `D:\\path\\file.txt` (MCP doesn't support POSIX `/d/path`) +- **Bash Commands**: Use forward slash `D:/path/file.txt` or POSIX `/d/path/file.txt` +- **Relative Paths**: No conversion needed `./src`, `../config` +- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users` #### **Content Uniqueness Rules**