Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Oct 12, 2026

Add Native Prompt Caching Support for Anthropic Claude on AWS Bedrock in Watson Orchestrate Agent Runtime

Watson Orchestrate's agent runtime does not inject the cache_control: {"type": "ephemeral"} metadata on static prompt segments when calling Anthropic Claude on AWS Bedrock, so Bedrock prompt caching is never activated.

Why it's useful: Every agent turn recomputes the full static context (system instructions + skill catalog), wasting Bedrock compute tokens and adding latency — even though the downstream gateway already supports caching.

Who benefits: Enterprise customers running high-volume agent workloads on Bedrock/Anthropic models who want lower token costs and faster response times.

How it should work: The agent runtime should automatically attach cache_control breakpoints to static prompt segments (base instructions, tool/skill catalogs) at the point of LLM dispatch when routing to Bedrock/Anthropic models — requiring no configuration from the end user.

Idea priority Medium