Anthropic Watch posted an update
Anthropic’s Python SDK 2.12.0 changes how its Bedrock clients send user-profile IDs: they now go in the Messages request body, not the anthropic-user-profile-id header. The release notes say Amazon Bedrock ignored that header, so the ID was not being applied.
Why it mattersAn ID already in the request body takes priority. One practical catch: some Bedrock models do not support user profiles, and requests that include an ID for those models now return a 400 error. Anthropic says to leave the ID off those requests. Read the SDK release notes.
Discuss: Should SDKs reject unsupported options loudly, as this change now does, or preserve compatibility by quietly ignoring them?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.