claude-code - 💡(How to fix) Fix [Bug] Claude Code consumes excessive tokens for local filesystem operations available via Google Drive sync [1 comments, 2 participants]

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/casa/.local/share/claude/versions/2.1.92 (expected in multi-process scenarios)\n at im_ (/$bunfs/root/src/entrypoints/cli.js:1884:2153)\n at An6 (/$bunfs/root/src/entrypoints/cli.js:1884:1233)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-07T15:43:22.447Z"},{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:537:2729)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-07T15:44:41.199Z"},{"error":"Error: File does not exist. Note: your current working directory is /Users/casa.\n at call (/$bunfs/root/src/entrypoints/cli.js:4303:7610)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-07T15:45:31.876Z"},{"error":"Error: Failed to fetch version from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/latest: ECONNREFUSED\n at Py1 (/$bunfs/root/src/entrypoints/cli.js:1882:15046)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-07T16:29:29.390Z"},{"error":"Error: Failed to fetch version from https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/latest: ECONNREFUSED\n at Py1 (/$bunfs/root/src/entrypoints/cli.js:1882:15046)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-07T16:29:29.390Z"},{"error":"Error: 1P event logging: 3 events failed to export (code=ECONNREFUSED, ECONNREFUSED)\n at queueFailedEvents (/$bunfs/root/src/entrypoints/cli.js:422:2574)\n at async doExport (/$bunfs/root/src/entrypoints/cli.js…

TL;DR

The issue can be mitigated by optimizing the approach to creating folders on Google Drive, prioritizing local creation and verifying access before using APIs.

Guidance

1. Verify local access: Before using Google Drive APIs, check if the agent can create folders locally to avoid unnecessary API calls.
2. Detect tool bugs quickly: Implement a mechanism to detect bugs in tools like gws drive files create and gdrive-upload to prevent repeated attempts and wasted tokens.
3. Prioritize simple solutions: Favor the most straightforward approach, such as using mkdir for local folder creation, to reduce token consumption.
4. Check OAuth token expiration: Ensure that OAuth tokens used by gdrive-upload are valid and handle expiration by refreshing or renewing them as needed.

Example

No specific code example can be provided without modifying the existing implementation, but the approach should involve checking local access and handling potential errors in tool interactions.

Notes

The provided information suggests issues with the current implementation, including inefficient use of APIs and failure to detect bugs promptly. Addressing these concerns should improve performance and reduce token consumption.

Recommendation

Apply workaround: Optimize the folder creation process by prioritizing local creation and improving error handling for tool interactions to reduce token consumption and improve efficiency. This approach addresses the immediate issues without requiring a version upgrade or significant changes to the existing infrastructure.