[BUG] File path autocomplete displays Chinese characters as octal escape sequences in v2.0.73

Workaround Found: Configure Git to Display UTF-8 Characters

I encountered the same issue with Chinese characters displaying as octal sequences in the @ autocomplete. I found a workaround that fixes the display issue:

git config --global core.quotePath false

Why this works:

Claude Code's @ file autocomplete appears to rely on Git commands (like git ls-files or git status) to list files. By default, Git escapes non-ASCII characters in file paths. Setting core.quotePath to false tells Git to output raw UTF-8 characters instead of octal escape sequences.

Before:

\345\256\236\347\224\250 Claude Code Skills \346\216\250\350\215\220\346\270\205\345\215\225.md

After:

實用 Claude Code Skills 推薦清單.md

Additional recommendation:

If you're still seeing issues, ensure your shell locale is set to UTF-8:

# Add to ~/.zshrc or ~/.bashrc
export LANG=zh_TW.UTF-8  # For Traditional Chinese
export LC_ALL=zh_TW.UTF-8

Then restart your terminal or run source ~/.zshrc.

---

找到臨時解決方案：配置 Git 顯示 UTF-8 字符

我遇到了同樣的問題，中文字符在 @ 自動補全中顯示為八進制序列。我找到了一個可以修復顯示問題的臨時方案：

git config --global core.quotePath false

為什麼這個方案有效：

Claude Code 的 @ 文件自動補全似乎依賴 Git 命令（如 git ls-files 或 git status）來列出文件。默認情況下，Git 會轉義文件路徑中的非 ASCII 字符。將 core.quotePath 設置為 false 可以讓 Git 輸出原始的 UTF-8 字符，而不是八進制轉義序列。

修改前：

\345\256\236\347\224\250 Claude Code Skills \346\216\250\350\215\220\346\270\205\345\215\225.md

修改後：

實用 Claude Code Skills 推薦清單.md

額外建議：

如果仍然有問題，請確保您的 shell locale 設置為 UTF-8：

# 添加到 ~/.zshrc 或 ~/.bashrc
export LANG=zh_TW.UTF-8  # 繁體中文
export LC_ALL=zh_TW.UTF-8

然後重啟終端或運行 source ~/.zshrc。

---

This is a workaround, not a fix for the underlying TUI bug, but it makes Claude Code usable with Chinese filenames again.

Tested on:

• macOS 14.6 (Darwin 24.6.0)
• Claude Code 2.0.74
• Both Simplified Chinese (zh_CN) and Traditional Chinese (zh_TW) filenames

感謝大大，這問題解決了！

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.