Skip to content

[Bug] Bedrock Converse sends Anthropic-specific cachePoint to Amazon Nova models #20815

@ProFire

Description

@ProFire

Summary

When using Amazon Nova models (e.g. global.amazon.nova-2-lite-v1:0) via
bedrock-converse-stream, OpenClaw injects cachePoint objects into message
content blocks. Nova's API rejects this with:

Malformed input request: #/messages/4/content/0: extraneous key [cachePoint]
is not permitted

Steps to reproduce

  1. Configure an Amazon Nova model (e.g., global.amazon.nova-2-lite-v1:0) in openclaw.json under the amazon-bedrock provider.
  2. Set the provider API to bedrock-converse-stream.
  3. Switch the active session to use the Nova model using the /model command.
  4. Send a message that triggers tool use or continue a conversation long enough for the system to attempt prompt caching.
  5. Observe the API error: Malformed input request: #/messages/4/content/0: extraneous key [cachePoint] is not permitted.

Expected behavior

OpenClaw should identify that the target model (Amazon Nova) does not support the Anthropic-specific cachePoint extension and should strip this field from the message content blocks before sending the request to the Bedrock Converse API.

Actual behavior

OpenClaw should strip cachePoint fields from message content when the target
model is non-Anthropic (Amazon Nova, Mistral, etc.).

OpenClaw version

OpenClaw 2026.2.17

Operating system

global.amazon.nova-2-lite-v1:0

Install method

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions