[BUG] CloudSync file access mismatch—Claude Code sees stale cached content while terminal sees current file

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Description:

• Files in Google Drive CloudSync directories show as empty (0 bytes) when accessed via Claude Code's Read/Bash tools
• Same files have full content when opened directly via nvim or terminal commands
• Affects skill files in .claude/skills/ on Google Drive mounts
• stat shows 0 byte size, but file is not actually empty
• Issue persists even when files are synced in Google Drive web interface

Steps to reproduce:

1. Create/edit file in Google Drive CloudSync mount
2. Try to read via Claude Code Read tool → shows empty/fails
3. Open same file in terminal editor → content visible

This blocks local skill development on Google Drive.

What Should Happen?

Claude Code Read/Bash tools should access the same file content that the terminal sees—reading the actual current
file from CloudSync, not a stale cached version.

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce:

1. Store a file in Google Drive CloudSync mount (e.g., ~/Library/CloudStorage/GoogleDrive-*.../file.md)
2. Edit file content in terminal (nvim, echo, etc.)
3. Try to read with Claude Code Read tool on the same path → returns empty/error
4. Open file in terminal with cat or nvim → shows correct current content
5. Run stat on the file → shows 0 bytes size (incorrect)

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.114

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_