What this error means
Extra 'caller' Field in Request Breaks computer-use Between v0.74.1 and v0.75.0 is a Anthropic API failure pattern reported for developers trying to fix anthropic sdk computer-use feature broken after upgrading to v0.75.0. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.
Why this happens
Closed issue (11 comments) on official Anthropic SDK repo. Extra 'caller' field in API requests broke computer-use functionality between SDK v0.74.1 and v0.75.0. Breaking change affects production agents.
Common causes
- Computer-use is a premium Anthropic API feature; breaking changes between SDK versions block automated desktop agents and RPA workflows
- Closed issue (11 comments) on official Anthropic SDK repo. Extra 'caller' field in API requests broke computer-use functionality between SDK v0.74.1 and v0.75.0. Breaking change affects production agents.
Quick fixes
- Confirm the exact error signature matches
Extra 'caller' Field in Request Breaks computer-use Between v0.74.1 and v0.75.0. - Check the Anthropic API account, local tool state, and provider configuration involved in the failing workflow.
- Compare the failing environment with a known working setup, then change one configuration value at a time.
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.