What this error means

wrangler upload rejected with code 10375 'Durable Object bindings cannot be used with edge preview' after removal of wrangler dev --remote on 2026-05-18 is a Cloudflare failure pattern reported for developers trying to fix code 10375 error preventing cloudflare worker deployments that combine durable objects with remote bindings (kv/d1/r2/ai). Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #13956 (cloudflare/workers-sdk), opened 2026-05-18T17:00:43Z. Directly caused by official changelog change removing wrangler dev --remote. Affects production workers with hybrid DO+remote setups. Mapping: Cloudflare Workers error → Cloudflare.

Common causes

  • GitHub Issue #13956 (cloudflare/workers-sdk), opened 2026-05-18T17:00:43Z. Directly caused by official changelog change removing wrangler dev --remote. Affects production workers with hybrid DO+remote setups. Mapping: Cloudflare Workers error → Cloudflare.

Quick fixes

  1. Confirm the exact error signature matches wrangler upload rejected with code 10375 'Durable Object bindings cannot be used with edge preview' after removal of wrangler dev --remote on 2026-05-18.
  2. Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
  3. Check the build output, project root, and deployment platform configuration before redeploying.

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

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. 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.