What this error means
Error: File does not exist. Note: your current working directory is /Users/edgar/Desktop/admin-app-ios at call (/$bunfs/root/src/entrypoints/cli.js:4299:9752) is a Claude Code failure pattern reported for developers trying to claude code automatically consumes 15% of user's 5-hour quota on session startup without any user input; repeated filedoesnotexist errors suggest background process or config scanning bug wasting paid api tokens. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
GitHub issue #61084 on anthropics/claude-code opened May 21, 2026 by edgar5055. Labeled area:cost and platform:macos. Three identical errors logged within ~40 seconds showing the CLI repeatedly trying to access a non-existent file. This directly impacts paid users who get charged per token used. Category: AI Coding Tools since it's a Claude Code bug that wastes subscription credits.
Common causes
- GitHub issue #61084 on anthropics/claude-code opened May 21, 2026 by edgar5055. Labeled area:cost and platform:macos. Three identical errors logged within ~40 seconds showing the CLI repeatedly trying to access a non-existent file. This directly impacts paid users who get charged per token used. Category: AI Coding Tools since it's a Claude Code bug that wastes subscription credits.
Quick fixes
- Confirm the exact error signature matches
Error: File does not exist. Note: your current working directory is /Users/edgar/Desktop/admin-app-ios at call (/$bunfs/root/src/entrypoints/cli.js:4299:9752). - Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
- Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Platform/tool-specific checks
- Verify the command, editor, extension, or API client that produced the error.
- Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
- Avoid deleting credentials, local model data, or project settings until the failing scope is clear.
Step-by-step troubleshooting
- Capture the exact error message and the command, editor action, or request that triggered it.
- Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
- Review the source evidence below and compare it with your environment.
- Apply one change at a time and rerun the smallest failing action.
- Keep the working fix documented for the team or deployment environment.
How to prevent it
- Keep provider/tool configuration documented.
- Record non-secret diagnostics such as tool version, provider name, model name, and command path.
- Add a lightweight check before CI or production workflows depend on the tool.